Connect your own Supabase

Pro, Business, and Custom tiers can attach a Supabase project so platform record APIs persist to your Postgres instead of the default store—useful for compliance, reporting, or reusing an existing data estate.

Prerequisites

Collect the project URL, anon key, and service role key. The service role is mandatory for the backend to perform record storage on your behalf; it is stored encrypted server-side.

Keys grant powerful access—rotate them if leaked, and never embed the service role in browser bundles.

Schema verification flow

Prowpt cannot silently run DDL on your tenant. Instead, the platform validates that required tables exist via PostgREST. If anything is missing you will see a schema_pending status, can download supabase_per_app_schema.sql, run it in the Supabase SQL editor, and save again.

Metadata-only mode stores URL + anon for client/export scenarios without switching the record store.
Active + service role means production traffic uses your database.
Schema pending blocks the switch until verification succeeds.

supabase-connect-flow

Placeholder: paste keys → validate → download SQL → success.

Data migration expectations

Connecting Supabase does not automatically migrate historical platform rows. Export ZIP from the prior environment and import, or run an ETL you control.