Loading…
Talk to your Supabase Postgres database in plain English.
Supabase is Postgres at its core, and iDBQuery treats it that way. Grab the connection string from your Supabase project's Database settings, paste it into iDBQuery, and the schema — including the `public` schema and any custom schemas you've added — is introspected in seconds. Every chat question becomes a safe parametrized SQL statement run against your Supabase Postgres, returned as a chart, table, stat card, or full dashboard. Auth tables, storage metadata, foreign keys, RLS-protected views, JSONB columns, arrays, ENUMs, and PostGIS geometry are all picked up automatically. You can pick which schemas iDBQuery is allowed to introspect, and creating a dedicated read-only Postgres role with restricted GRANTs is the recommended pattern for production. Connection details are encrypted at rest with strong symmetric encryption and used only at query time. The free tier — 1M tokens per month, three sources, five reports, no credit card — is enough to validate the integration end to end on a real Supabase project before committing. iDBQuery makes the data inside Supabase explorable to your whole team, not just whoever knows SQL.
Everything iDBQuery's Supabase connector supports out of the box.
Project → Add source → PostgreSQL. Supabase exposes a standard Postgres endpoint, so the Postgres connector is what you want.
Supabase dashboard → Project Settings → Database → Connection string (URI). Use the direct connection or the connection pooler, whichever fits your workload.
For tighter control, create a Postgres role with SELECT-only GRANTs on the schemas you want exposed and use that user.
Ask 'How many new sign-ups per day for the last 30 days?' — the AI writes the SQL and renders the result.
Free tier covers most teams. No credit card.
No credit card required · 1M tokens / month free