Can I connect Supabase to iDBQuery?
Yes. Supabase is built on PostgreSQL, so iDBQuery connects to it directly through its PostgreSQL connector. Use the Supabase database connection string with a read-only role, and you can ask questions in plain language and get answers cited back to the exact rows.
Supabase gives you a managed PostgreSQL database, so iDBQuery connects to it exactly as it would to any Postgres — through its native PostgreSQL connector, using the connection string Supabase provides (host, port, database, user, and password).
Once connected:
- Ask in plain English — 'weekly signups and how many upgraded to paid' — and iDBQuery writes the SQL and runs it.
- Cited answers — every figure links back to the exact Supabase rows.
- One live model — blend your Supabase tables with a Stripe export, a spreadsheet, or an API in a single answer.
Best practice is to create a read-only Postgres role for iDBQuery so it can query but never modify your data, and to connect through Supabase's connection pooler for efficient connections. Supabase's Row Level Security stays enforced at the database, and you can further scope which tables iDBQuery reads.
Example: an indie SaaS runs entirely on Supabase. The founder asks 'which features do my retained users touch most in week one?' and gets a cited chart in seconds — no analyst, no dashboard build. Because iDBQuery's semantic layer understands your schema, teammates can ask in their own words, and because it can run on the Desktop app or in your own cloud, your data stays under your control.
Updated 2026-06-22