If you run multi-tenant SaaS on Supabase with one project per customer, you probably know this pain:
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:
Probably not for you if:
Open source, live at tenantctl.io. Would love feedback from anyone doing this at scale, especially what's still painful in your workflow.
The user introduces 'tenantctl', a control plane for managing multiple Supabase tenant projects from a single base template. It helps teams provision and sync tenant projects, ensuring consistency across migrations, schemas, and edge functions. The tool is open source and seeks feedback from users managing multi-tenant SaaS on Supabase.
I am building a multi Saas Tenant but it’s not completed due to Supabase globally technical issue going on. I am not aware about the pain point you mentioned yet so can you please clarify what problem you are solving for multi tenant Saas please. Thank you
Yes so this helps people who are building SaaS products where every client needs a separate Supabase project. What they can do is hook up their organization and just replicate the "base" project theyre developing on to create customer environments