Fictura
Outgoing

Supabase

The Supabase organization connection that gave apps built on Fictura a backend you own. It is no longer in the dashboard.

No longer in the dashboard

Setup no longer has an App backend card. The App Builder this connection served has been removed, so nothing creates a project from it any more.

It took your Supabase organization slug, a personal access token (sbp_…), and a region. The token was verified against Supabase before it was stored, encrypted at rest, and — like every credential in Fictura — never returned by any endpoint.

What it was for — and not for

  • For: provisioning. When the App Builder produced an app that needed a backend, the project was 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.

A token stored before the card went away stays encrypted and unused; projects already provisioned stay yours in Supabase, untouched.

On this page