Supabase

Prove what worked, from the tables you already have.

Start with the schema: the tables and fields behind each customer milestone. When you are ready to measure a change, link the tables its success formula needs. The result stays tied to data you can inspect.

Read-only by default. No card.

Illustrative product view. Schema access starts with structure.
accounts
id
plan
events
account_id
event_name
plan
tables · columns · relationships

Schema analysis reads database definitions, not row values. Measurement checks can read connected data.

  • Grounded in your real schema

    Schema analysis reads table and column definitions to ground the journey. It does not read row values.

  • Readiness and samples are separate

    Readiness checks the required events and fields against code or runtime evidence. A missing database sample does not block verification.

  • Owner-controlled connection

    Only a workspace owner can start or change it. Tokens are encrypted at rest.

SupabasePostHogMixpanelBigQueryResend

One source is enough to start.

Supabase over OAuth, GitHub through an app scoped to the repositories you pick, or both. An unlinked environment reports as not linked.

  • No workspace-wide switch between development and production
  • Deploys and trigger installs target the production slot only
Illustrative product view. Each connection keeps its own sample state.
database
accountsok
12
sample rowsread-only
Open source

Or point the CLI at exported SQL.

Skene OSS reads your repository and writes the customer journey it finds to skene-context/journey.yaml. It needs no Skene account, and you point it at your own model provider.

Command
uvx skene analyse-journey . --schema-dir ./exports
Or use --db-url for a live schema. Pass one schema flag, never both. Pass neither and no database is read.
The two Supabase apps

What changes when you opt in.

CapabilityRead-only (default)Read-write (opt-in)
Table, column and type definitionsYesYes
Table countsNot includedYes
Trigger deployment for automationsNot includedYes
Capability
Table, column and type definitions
Read-only (default)
Included
Read-write (opt-in)
Included
Capability
Table counts
Read-only (default)
Not included
Read-write (opt-in)
Included
Capability
Trigger deployment for automations
Read-only (default)
Not included
Read-write (opt-in)
Included

The two Supabase OAuth applications, and what each one reaches. Either is started by a workspace owner, and OAuth tokens are AES-256-GCM encrypted at rest in both.

Start with the read-only connection.

Connect Supabase over OAuth, read-only by default. Reconnect with read-write when you want table counts or triggers.