Analyze your Supabase data with AI today.
Build dashboards, automate reports, and ask questions in plain English — all from your Supabase data, no complex infrastructure to maintain.
Have multiple Supabase accounts? Analytics across multiple Supabase accounts →
Everything Supabase exposes, modeled and queryable.
Extracts tables and views from the Postgres database that backs a Supabase project across one or more schemas. Supports full-table loads, incremental replication via a replication key, and log-based change data capture (CDC) using Postgres logical replication. Centralizes your application's operational data — auth, storage, and your own tables — into a warehouse for analytics and BI.
Tables & streams
Core identity records representing individual end-users of the application; supports cohort analysis, activation funnels, retention tracking, and user-level KPI attribution.
Organization or company entities that group users under a single billing and permissions boundary; enables account-level revenue analysis, expansion tracking, and segmentation.
Recurring billing agreements linking accounts to plans; drives MRR/ARR calculations, churn analysis, upgrade/downgrade tracking, and renewal forecasting.
Billing documents issued for subscription periods or one-time charges; supports revenue recognition, collections analysis, and accounts-receivable reporting.
Individual monetary transactions tied to invoices; enables cash-flow analysis, payment-method mix reporting, failure-rate tracking, and reconciliation.
Purchase transactions capturing line items, quantities, and totals; powers GMV reporting, average-order-value analysis, and fulfillment metrics.
Catalog items or SKUs available for purchase or subscription; supports product-mix analysis, attach rates, pricing optimization, and inventory tracking.
Pricing tiers or packages that define feature sets and billing amounts; enables plan-distribution analysis, upgrade-path modeling, and pricing experiments.
Timestamped application activities such as clicks, page views, and API calls; drives engagement scoring, funnel analysis, and behavioral segmentation.
Grouped sequences of user events bounded by inactivity timeouts; supports session-duration analysis, bounce-rate tracking, and conversion-path modeling.
Collaborative groups within an account that share workspaces or permissions; enables team-level adoption metrics, seat-utilization analysis, and collaboration tracking.
Discrete workstreams or initiatives created by users or teams; supports project-velocity reporting, resource-allocation analysis, and feature-usage attribution.
Authenticates to your Supabase project's Postgres database with the database user and password from the project's connection settings. Use the direct/session connection string on port 5432 (not the transaction pooler) over SSL.
Requires a Supabase project (Postgres database) to connect.
Relational data, transactional records, and business metrics.
Three steps. One afternoon.
Authenticate Supabase in a few clicks. OAuth, API key, or IAM role — we handle secrets and rotation.
We pull every stream into your warehouse. CDC where the API supports it; full + incremental otherwise. Hourly-or-faster, row-level secure.
SQL, dashboards, or ask Fi in plain English. Your Supabase data lives next to every other source — ready to join.
Build your own with the Definite SDK, or request it. Most go live in days.
Pair Supabase with the rest of your data.
Join Supabase with the rest of your data, then ask Fi questions across all of it.
