Supabase + Orcabase

Your Supabase data, in plain answers.

Built your app on Supabase? Connect its Postgres database and ask about signups, activity and revenue in plain words. Orcabase reads it live through a read-only login, so there’s nothing to sync and nothing to break.

  • Live connection
  • Always current
  • Read-only login
AgentSupabase connected

How many people signed up this week, and how many came back?

Reading your Supabase data…

1,284 signups this week. 43% came back within 3 days.

  • Signups are up 18% on last week.
  • People who created a project on day one came back twice as often.
  • Tuesday’s spike follows the newsletter going out.

Signups by day

M262TWTFSS
How I got this· 4 steps
  1. Looked at your users and projects
  2. Counted signups by day
  3. Checked who returned within 3 days
  4. Compared first-day projects with none

Example answer. Numbers are illustrative.

In plain words

Can I build dashboards on my Supabase data?

Yes. Every Supabase project is a Postgres database, and Orcabase connects to it like any other: through a login you create that can read but never change anything. Then you ask questions in plain words, and the agent answers with the number, a chart and how it got there.

Your app keeps talking to Supabase as usual. Orcabase reads the same data, live, so a dashboard of signups or orders is always current.

Ask in plain words

What you can ask about your Supabase data

The agent answers with the number, a chart and the steps it took. Keep the good answers on a dashboard.

  • How many people signed up each day this month?

  • Which users haven’t signed in for 30 days?

  • How many new users create something on their first day?

  • Which plan do teams upgrade to first?

  • What does a typical week-one user do?

  • Which accounts grew fastest this quarter?

  • How many users are active every day, every week?

  • Show me paying teams by the month they signed up.

What Orcabase can read

Everything in Supabase, read where it lives.

Stays in your database. Orcabase keeps only the latest result of each saved chart, so dashboards open fast.

01

Your app’s tables

Projects, orders, teams: everything your app keeps in its Supabase database, read live.
02

Sign-ups and sign-ins

The user records Supabase keeps for you, when Orcabase’s login is allowed to read them.
03

Anything you add later

New tables are readable as soon as your app creates them, with the recommended login.
04

Only what you share

Grant Orcabase’s login part of the database if some of it should stay out of sight.

Numbers worth defining

Define them once. Every answer agrees.

Tell Orcabase what each number means, certify it, and your dashboards, the agent and your whole team use the same one. The agent can draft these from your Supabase data.

How metrics work

  • Signups

    New user accounts, counted on the day they were created.

  • Activation rate

    Share of new users who do your key action, like creating a project, in their first week.

  • Weekly active users

    Users who did anything meaningful in the last 7 days.

  • Paying accounts

    Accounts on a paid plan at the end of each day.

Dashboards to start with

Your Supabase numbers at a glance.

Ask the agent to build one of these, or pin charts yourself. Share any dashboard with a link.

Growth

4 charts
  • Signups by day
  • Activation rate by week
  • Weekly active users
  • Paying accounts

Onboarding

3 charts
  • First-day actions
  • Time to first project
  • Week-one retention by signup week

About dashboards

How to connect

Connect Supabase, step by step.

  1. 1

    Copy the session pooler details

    In Supabase, click Connect and choose Session pooler. It works over IPv4; the direct connection needs Supabase’s IPv4 add-on for that.

  2. 2

    Create a read-only login

    In Supabase’s SQL editor, create a login for Orcabase that can read and never change anything. The PostgreSQL guide has the lines.

  3. 3

    Add it to Orcabase

    Go to Data Sources → New data source and pick PostgreSQL. Use the pooler’s host and port, the postgres database, and your login as orcabase_readonly.your-project-ref, the form the pooler expects.

  4. 4

    Test, then ask

    Click Test connection, then open the agent and ask about this week’s signups.

What you’ll need

  • Access to your Supabase project’s dashboard, to copy the connection details.
  • A read-only login for Orcabase, created in Supabase’s SQL editor.
At a glance
How it connects
Live connection
How fresh
Live. Every answer reads your data as it is right now.
Where your data lives
Stays in your database. Orcabase keeps only the latest result of each saved chart, so dashboards open fast.
Who can set it up
Anyone in your organization.
Your login
A read-only login you create for Orcabase. Its password is encrypted and never shown again.
Cost
Included on every plan.
Connect PostgreSQLStep-by-step, in the docs.

Questions

About Supabase and Orcabase

More in the docs: Connect PostgreSQL

Why do some of my tables look empty in Orcabase?
Row level security. Supabase tables often have it turned on, and it hides rows from any login without a matching policy, Orcabase’s read-only one included. Add a policy that lets Orcabase’s login read those tables, or connect with a login that bypasses row level security.
Should I use the direct connection or the pooler?
The session pooler. Supabase’s direct connection only works over IPv6 unless you’ve bought its IPv4 add-on, while the session pooler works everywhere.
Will Orcabase slow down my app?
Questions only read, each stops after 30 seconds, and dashboards reuse each chart’s last result instead of asking again. For a busy production database, give Orcabase’s login its own time limit too.
Does Orcabase copy my Supabase data?
No. Every question reads it where it lives. Orcabase keeps only the latest result of each saved chart, up to 5,000 rows, so dashboards open quickly.

Your Supabase data already has the answers.

Connect it, ask your first question, and pin the answers you want to see every week.