Supabase

Dashboard → Setup → App backend. You provide your Supabase organization slug, a personal access token (sbp_…), and a region (seven to choose from). The token is verified against Supabase before it's stored, encrypted at rest, and — like every credential in Fictura — never returned by any endpoint; the dashboard shows only a hint.

What it's for — and not for

• For: provisioning. When the App Builder produces an app that needs a backend, the project is created inside your org, in your region, on your billing — you keep root.
• Not: data sync. Fictura does not mirror events or analytics into Supabase. Continuous data out is PostHog; moment-by-moment pushes are outgoing webhooks.

Disconnecting removes the stored token; projects already provisioned stay yours in Supabase, untouched.