apps/www/_blog/2025-12-05-introducing-supabase-for-platforms.mdx
Today, we're launching Supabase for Platforms—a white-label offering that lets platforms provision and manage fully managed backends on behalf of their users.
AI builders and agentic coding have fundamentally changed how software gets built in 2025. Supabase has become the default backend for this shift, with Lovable, Bolt.new, Vercel's v0, Figma Make, and many others building on top of Supabase projects owned by their users to develop full-stack applications. The growth has been staggering:
But as these platforms scaled, we heard consistent feedback: they wanted a more seamless flow so their users don't have to think at all about provisioning and configuring their backends. That's when Supabase for Platforms was born.
Leading AI builders like Lovable, Bolt.new, and Baidu's MeDo have already started using Supabase for Platforms to create millions of Supabase projects in the last few months alone, making full-stack development more accessible and easier than ever.
And while AI builders are leading the way, Supabase for Platforms is built for any platform or tool that wants to offer managed backends.
Supabase for Platforms lets you white-label Supabase and provision backends for your users—all managed through our Management API or remote MCP Server.
Your users get the full Supabase stack:
You control the entire experience. Your users get the full power of Supabase.
With Supabase for Platforms, you can:
Supabase for Platforms and the full feature set is available to select AI Builders. Contact us if you'd like to get started.
Some AI builders want to manage infrastructure on behalf of their users. With a central organization, you create and own projects in your Supabase org. Users can claim those projects into their own Supabase org later if they want full control.
This model works well when your users don't know or care about infrastructure. You handle the complexity—they focus on features.
<Admonition title='Want users to bring their own Supabase accounts instead?'>With OAuth integrations, users connect their existing Supabase org to your tool. They own and manage their projects directly, and you get API access to help them build.
This model works well when your users are developers who already use Supabase or want more control from the start.
</Admonition>Contact us to enable central organization management.
These features are available through the Management API or remote MCP Server right now.
Create projects programmatically. We highly recommend using smart region selection to ensure capacity.
Update settings for Auth, Data API (PostgREST), Edge Functions, Storage, and Realtime through the Management API. Every setting in the Supabase Dashboard is available for configuration programmatically.
Deploy functions directly through the API. No CLI required.
Upgrade or downgrade compute as your users' needs change.
Use the security advisor API to check projects before deploying to production. Catch issues before your users, and their users, do.
Get and manage API keys for each project. We recommend using the publishable and secret API keys instead of the legacy anon and service_role keys.
For more information, read the announcement here.
Create ephemeral development environments for each project using branching. Your users can make changes safely on a branch, then merge to production. If something goes wrong, destroy the branch and start fresh based off production.
We built Platform Kit, a collection of UI components for the Management API. Embed a lightweight version of the Supabase Dashboard directly in your app. Your users can manage their backend without leaving your product.
These features are available to a subset of our AI Builder customers. Contact us to get access.
We offer Pico instances that scale to zero when not in use. This is ideal for platforms with many projects that have variable usage. You only pay for what your users actually use.
Once you have development environments, create restore points after every backend change. Roll back if something goes wrong. This gives your users confidence as they’re developing.
Run schema migrations through the API. Changes are tracked automatically. If a migration fails, it rolls back.
Let users transfer projects from your organization to their own. You retain API access to continue helping them build. They get full ownership and control.
This is useful when users want to eventually manage their own infrastructure and billing.
Supabase stores data. You cannot simply roll back production changes without risking data loss. Check out the docs for our recommended dev/production workflow.