Supabase connector

Query Your Supabase Postgres Data with AI

Connect your Supabase database to Better Analyst and ask plain-English questions about live product, user, billing, and event data. No SQL required.

  • Free to try
  • Read-only access
  • Encrypted credentials

Try a real question

Your question carries into your free workspace

  • Quick setup

    Use the Session pooler details from the Supabase Connect dialog. Most teams connect with host, port 5432, database postgres, and SSL set to require.

  • Secure by default

    Credentials are encrypted and connections use SSL. Read only is the default; optional destination writes are restricted to an explicitly approved schema. The connector is tuned for your application tables, not API keys or admin workflows.

  • Live Postgres access

    Query current tables directly instead of exporting CSVs or waiting for sync jobs. Ask questions against the same live Postgres data your product already runs on.

What you can analyze

  • Product Analytics

    • “Show me signups and logins by day for the last 30 days”
    • “Which events are growing the fastest week over week?”
    • “Break down account_created by acquisition channel”

  • User & Event Analysis

    • “List the top users by event volume this week”
    • “Which event types are increasing fastest month over month?”
    • “Find rows missing a user_id, plan_id, or created_at value”

  • Schema Exploration

    • “What tables are available in my Supabase public schema?”
    • “Describe the columns in the events table”
    • “Which tables look related to users and billing?”

  • Operational Dashboards

    • “Build a retention dashboard from my events table”
    • “Create a product usage dashboard with daily active users and paid conversions”
    • “Show weekly trends for account creation, login, and trial activation events”

Smarter Over Time

Teach the AI your data

Upload documentation and provide feedback to make every query more accurate for your Supabase data.

  • Knowledge base

    Upload schema definitions, data dictionaries, and business logic docs to help the AI understand your Supabase structure.

  • SQL feedback loop

    Rate generated queries as correct or incorrect. Your feedback is saved and used to improve future Supabase queries.

    Generated SQL

    SELECT product, SUM(revenue)
    FROM sales
    GROUP BY product
    ORDER BY 2 DESC

    Was this correct?

How it works

  • 01

    Upload context

    Add schema docs, data dictionaries, or SQL files that describe your Supabase tables and business logic.

  • 02

    Ask questions

    Query your data in plain English. The AI uses your uploaded context to write more accurate SQL.

  • 03

    Refine with feedback

    Mark queries as correct or incorrect. The AI learns from your feedback and improves over time.

Detailed setup guideStep-by-step instructions for connecting and configuring Supabase.

Explore other connectors

Frequently asked questions

Does Better Analyst connect to Supabase with OAuth?
No. Supabase connections use database credentials, not Supabase API OAuth. Use your Postgres host, port, database, username, and password from the Supabase Connect dialog.
What Supabase credentials do I need?
Use the Session pooler host from the Supabase Connect dialog, port 5432, database postgres, a database username, and the matching database password. For hosted projects, the username often looks like postgres.<project-ref>. SSL should stay set to require.
Should I use Supabase API keys instead?
No. The Supabase connector talks to Postgres directly, so it needs database credentials rather than the anon or service_role API keys that power the REST and client SDK layers.
Should I use Session pooler or the direct connection?
Use Session pooler as the default. Supabase recommends it for persistent application traffic and for environments that need IPv4 compatibility. Use the direct connection only if your environment supports it and you intentionally want that path.
Can Better Analyst access auth or storage schemas?
No. The dedicated Supabase connector is intentionally focused on your application schema, with public as the default. That keeps analysis on your product tables instead of Supabase-managed system schemas.
Is this different from using the PostgreSQL connector?
Yes. Under the hood Supabase is Postgres, but Better Analyst uses a dedicated Supabase connector with the right defaults for SSL, schema handling, and connection guidance. That removes a lot of setup guesswork.
Will this work with hosted Supabase projects?
Yes. Hosted Supabase projects are the primary use case. Session pooler works especially well for deployed apps and other environments that do not have direct IPv6 database access.

Ready to Query Your Supabase Data with AI?

Connect Supabase