Get started for free

Supabase, queried in plain words.

Ask how many users signed up this week, what a table looks like and whether the project is healthy, and Cedric proposes the SQL, the update or the deploy before he runs anything that changes data.

Get started for free

100K credits ($50) on sign up. No card needed.

  • The question is usually in the database already; what is missing is someone free to write the query.
  • Ask in plain words: rows matching a condition, the columns on a table, the migrations applied, the project's status and region.
  • Cedric runs SQL to read, and proposes the insert, update or delete before running it, with the statement shown in full.
  • End-user accounts, storage buckets, serverless functions and project settings such as auth and secrets are managed from the same thread.
  • Deleting a project, dropping a table or removing a user is irreversible, so each one is confirmed first, and plan-based rate and resource limits apply.

What can a Supabase AI agent do?

A Supabase AI agent turns a question into a query and runs it. Cedric runs SQL queries against a project's database to read records, and he inspects the database structure first, tables, columns, extensions and migrations, so the query fits the schema rather than a guess at it. He lists organizations and projects and checks a project's status, region and settings, which covers "is production paused" and "which region is staging in". That is the shape of an AI data analyst for a team whose data lives in one project.

Writes to data are proposed with the statement shown. Cedric can insert, update or delete records through SQL, and he can manage end-user accounts: listing users, creating them, updating details and deleting them. He uploads, downloads, lists, moves and removes files in storage buckets and creates or configures buckets. Each of those is a change to live data, so Cedric shows exactly what will run and waits for your yes; a read never needs one.

The project itself is manageable too. Cedric deploys, updates, lists and removes serverless functions attached to a project, manages configuration such as authentication settings, secrets, custom domains and preview branches, and creates new projects or pauses, restores and deletes existing ones. Deleting a project or dropping a table cannot be undone, which is why those are confirmed every time, and heavy query or API usage can hit the plan's rate and resource limits.

The growth question

One query written, one number, one cleanup proposed.

#productCedric is in this channel

Yusuf Demir9:14 AM

@Cedric how many users signed up in the last 7 days on production, and how many of those never created a workspace? Then delete the test accounts ending in @example.test.

CedricAPP9:15 AM

Production (eu-central-1, healthy). Last 7 days: 312 sign-ups in auth.users; 87 of them (28%) have no row in public.workspaces. Query used: a left join of auth.users on workspaces.owner_id filtered on created_at >= now() - interval '7 days'. Test accounts: 14 users match email like '%@example.test', all created by the QA run on 29 August, none owning a workspace. Proposed: delete those 14 users. This cannot be undone.

Delete the 14 test users from production?

Queried

SQL written from a plain question and run against the project, with the schema, tables and columns inspected first.

Changed

An insert, update or delete, a user created or removed, a file moved in a bucket, a function deployed: shown in full, run on your yes.

Checked

Project status, region and settings, applied migrations, and configuration such as auth settings, secrets and custom domains.

Connect Supabase with your own key

No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.

  1. 01

    Install Cedric where your team talks

    One click. He joins your Slack like any other member, and everyone shares the same Cedric.

  2. 02

    Connect Supabase from the dashboard

    Open the Integrations page, pick Supabase and paste the project URL and a service key from Supabase's API settings. You can revoke the connection in one click at any time.

    Pick Read-only when you connect if you only want him reading. You can switch it later.

  3. 03

    Ask in plain words

    Back in the channel, try it: "how many users signed up this week?" You describe the outcome; Cedric picks the Supabase actions the ask needs. There is nothing to configure.

    Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.

  4. 04

    Let it become routine

    Schedule the recurring version of the ask, and let Cedric fold Supabase into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.

Better in company

The numbers in Supabase are the numbers behind the charts in PostHog; when the two disagree, ask Cedric to query the table and read the event count side by side, then name the gap. The result can go into a Google Sheets tab for the week.

A schema change starts as a pull request in GitHub and ends as a migration in Supabase. Ask Cedric whether the migration from last week's PR has been applied on production and staging, and he reads the migration list on both projects and says which one is behind, with the follow-up filed in Linear on your yes.

Worth knowing

Supabase comes from Cedric's catalog of 3,200+ apps. He works from what the Supabase connection can read and do, the same list its card shows in your dashboard.

Deletes cannot be undone. Deleting a project, dropping a table or removing a user is irreversible in Supabase, so Cedric shows the exact statement or the exact list and asks every time.

Plan-based limits apply. Heavy query or API usage can hit the rate and resource limits of the project's plan, so a very large read is paged or narrowed rather than run in one go.

The Supabase connection sets the scope. Cedric sees what it grants. Access is logged, and you can revoke it from the dashboard at any time.

Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a person to approve.

FAQ

Yes. Supabase is one of the 3,200+ apps in Cedric's catalog. Connect it once from the dashboard, with the project URL and a service key from Supabase's API settings, and ask in plain words. Cedric picks the actions an ask needs from what the connection can read and do, with no fields to map.

He can run SQL queries against the project's database to read, insert, update or delete records. Reads run when asked; anything that changes data is shown as the full statement and waits for your yes. He inspects tables and columns first so the query matches the real schema.

He reads each project's status and region from Supabase, so you can ask which project a query ran on, and any write, deploy or setting change is proposed with the project named before it runs. Pausing, restoring or deleting a project is confirmed the same way.

Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.

Yes, and it starts that way: a key connection is read-only until you turn writes on. Even with writes on, anything that changes or sends waits for an approval.

Every workspace starts with 100,000 free credits (worth $50) on sign-up, no card. Plans start at $19 a month for the whole team, no seats. Each task uses credits in proportion to the work. See pricing.

Works well with Supabase

All integrations

Connect Supabase in a minute.

Ask how many users signed up this week, then see the query he wrote to answer.

Get started for free

100K credits ($50) on sign up. No card needed.