Open source

Multi-tenant control plane for supabase

Provision tenant projects from a golden base. Catch migration and schema drift before production diverges.

How it works

From base project to tenant fleet

  1. 01

    Connect Supabase

    Authorize tenantctl with the Supabase orgs you operate. OAuth is per organization.

  2. 02

    Define a tenant group

    Pick a base project as the golden template. Add tenant projects or provision new ones.

  3. 03

    Sync and ship

    Run drift checks, apply migrations, and close schema gaps before tenants fall behind base.

Features

Operate many tenants like one codebase

Everything you need to provision, compare, and sync Supabase tenant projects without one-off scripts.

  • Tenant groups

    Point at a golden base project once. Every tenant inherits the same starting schema, functions, and secrets policy.

  • Drift map

    See base and tenant projects on one graph. Check migrations, live schema, edge functions, and secrets per node.

  • Provisioning pipeline

    Create the Supabase project, replay migrations, clone schema, deploy edge functions, and sync secrets in one flow.

  • Migration sync

    Spot missing or extra migrations, apply from base, and keep tenant history aligned with your golden project.

  • Live schema diff

    Generate SQL to close Postgres drift when migration history is not enough.

  • Attach existing projects

    Bring live Supabase projects under a tenant group without reprovisioning from scratch.