The admin panel for your Supabase app.

See and edit the users and tables of your Supabase app in its own words, plus money, AI costs and pg_cron jobs. Set up by your coding agent.

Set up everydeck for this app, including the read-only connection that lets everydeck read the data I approve, restart the local servers of this app when needed, and open a pull request, or commit locally if the repository has no remote.
claude mcp add --transport http everydeck https://app.everydeck.ai/mcp
Connect your appRead the docs

Supabase is a tested stack: Postgres with Supabase Auth, pg_cron and Edge Functions.

A guest's page in a Supabase app. Drawn from everydeck's own code with example data (Tourbird, a tour booking app), not a screenshot.

Last verified:

everydeck gives a Supabase app its own backend: see and edit your tables as pages in your app's own words and the people who sign up through Supabase Auth, plus money and AI costs and your pg_cron schedules. Your coding agent sets it up in one sentence, and Supabase is a tested stack.

What you see for a Supabase app

AreaWhat everydeck shows
Your dataOne page per kind of thing your agent found in your tables (tours, bookings, orders), with history; change a value where it stands, and the edit goes through your app
PeopleEveryone in your app with how they sign in, what they did and what they paid
Money and AI costsRevenue, paying customers and failed payments, only from payments everydeck saw, plus what AI costs you per flow and model
JobsEvery pg_cron schedule with its last 30 days; a run that does not check in opens a case
ErrorsCases in plain words with your code first and a fix prompt for your agent

What you can do

Send a password link, suspend access, delete a person's data, and export it for a GDPR request. Each of these uses an action your app itself offers, is your click, and lands in the Protocol with who and why.

pg_cron schedules

everydeck finds cron.schedule(…) in your migrations. A schedule written in SQL reports through the outbox, in the same transaction, with no key in SQL:

select everydeck_outbox.run_job('nightly_import', $job$ select import_availability() $job$);

If the command fails, its writes roll back and the run reports error. If no run arrives by its due time plus 2 minutes, a case opens.

Schedules of a Supabase app, one of them quiet. Drawn from everydeck's own code with example data (Tourbird, a tour booking app), not a screenshot.

How it is set up

Your coding agent does the setup after one sentence (Set up with Claude Code). It writes the app map from your code and schema, and the read bridge as a Supabase Edge Function. When you connect your Supabase project to everydeck, everydeck brings its own parts into it (outbox, schedule, relay, read bridge), each with a preview and your Approve.

The read bridge reads only what you approved, in a read-only transaction, so your database refuses writes. Email, phone and IP columns are not read by default.

Limits

  • The read bridge makes at most 600 requests per hour, about 2.6 MB. One query may run 20 seconds in your database.
  • everydeck derives at most 200 kinds of things and 100 fields per kind from your schema.
  • The extensions pg_cron and pg_net stay when you remove everydeck, because your app may use them.
  • Every limit: Limits.

Next