Built a control plane for teams running many Supabase tenant projects

If you run multi-tenant SaaS on Supabase with one project per customer, you probably know this pain:

• You have a "golden" base project with the right schema, migrations, edge functions, and secrets
• Every new tenant means another Supabase project to provision and keep in sync
• Over time, tenants drift: missing migrations, schema differences, edge functions out of date

That's what tenantctl is for.

It's a control plane for teams managing a fleet of Supabase tenant projects from a single base template. You connect your Supabase org, define a tenant group with a base project, then provision new tenants or attach existing ones. From there you get a graph view of base → tenants, drift checks (migrations, schema, edge functions, secrets), and tools to sync tenants back to base.

Good fit if you:

• Run project-per-tenant on Supabase
• Need to provision new tenants without hand-running scripts every time
• Want visibility when tenants fall behind your golden project

Probably not for you if:

• You have one Supabase project with RLS multi-tenancy
• You're not on Supabase :)

Open source, live at tenantctl.io. Would love feedback from anyone doing this at scale, especially what's still painful in your workflow.