How does Rig connect to Supabase?

With standard Postgres connection details: host, port, database, username, password and schema. Supabase is Postgres, so it connects the way any Postgres database does.

Does this affect my production database?

Rig reads from it on a schedule and writes nothing. Moving analysis into the warehouse is what keeps heavy queries away from the database serving your application.

Can I sync only some tables?

You choose the schema, and Rig ingests the tables in it. If you want to narrow further, tell us which tables matter and we will scope the source.

Is this the same as connecting Postgres?

Mechanically yes, and Rig lists both because people look for the product they use rather than the engine underneath it.

Warehouses & databases Supported

Supabase integration for Rig

The easiest way to query Supabase in Claude and other AI tools

Supabase is a hosted Postgres platform with authentication, storage and realtime APIs, widely used as the primary application database for a product.

Try Rig Book a demo

What Rig sees in Supabase

Once connected, Rig models these objects so questions resolve to the right tables and joins:

All tables in the selected schema
Application records
User tables
Relational structure

How Supabase connects to Rig

Give Rig standard Postgres connection details for your Supabase database and the schema you want. Rig replicates those tables into your analytics warehouse, so heavy analytical queries run there rather than against the database serving your product.

Analyse product data without touching production

Running analytics against the database your application depends on is how dashboards cause outages. Rig replicates Supabase into the warehouse, so long analytical scans run on infrastructure built for them and your production database keeps serving users.

Ask Rig

How many users completed onboarding this month?
What does the activation funnel look like by signup cohort?
Which features do our highest-value accounts use most?

Join product behaviour to revenue and support

Your application database knows what users did and knows nothing about what they paid or complained about. In one warehouse alongside billing and support, usage becomes answerable in commercial terms rather than in event counts.

Ask Rig

Do accounts using this feature churn less?
Which usage patterns precede an upgrade?
Do customers who raise support tickets use the product differently?

Give AI tools real product context

Once Supabase tables are in the warehouse with Rig's context layer over them, your AI tools can answer product questions against real schema, real joins and real column meanings, instead of guessing from table names.

Ask Rig

How many active workspaces do we have, by plan?
What is the median time from signup to first successful action?
Which onboarding step loses the most users?

Ask your Supabase data in Claude, ChatGPT or Cursor

Rig serves your Supabase data to AI assistants over MCP. Once Supabase is synced into your warehouse, you can ask questions in plain English from the tool you already use, and every answer is backed by validated, governed SQL.

Frequently asked questions

How does Rig connect to Supabase?: With standard Postgres connection details: host, port, database, username, password and schema. Supabase is Postgres, so it connects the way any Postgres database does.
Does this affect my production database?: Rig reads from it on a schedule and writes nothing. Moving analysis into the warehouse is what keeps heavy queries away from the database serving your application.
Can I sync only some tables?: You choose the schema, and Rig ingests the tables in it. If you want to narrow further, tell us which tables matter and we will scope the source.
Is this the same as connecting Postgres?: Mechanically yes, and Rig lists both because people look for the product they use rather than the engine underneath it.