Build the Backend Your App Needs.Give Every Feature a Place to Run.

The catalogue lists a preconfigured Supabase environment with PostgreSQL, Auth, Realtime and generated APIs. Plans differ in CPU, memory, SSD storage and bandwidth. The listed service also includes automated installation and dedicated support.

Your application, schema, policies, custom domains and external service credentials still need configuration. Use the plan cards above for current prices and billing terms.

Use Pro or Business as the starting comparison. Supabase currently publishes a 2-core, 4 GB RAM minimum and a 4-core, 8 GB RAM recommendation for all components. Pro meets the minimum allocation; Business matches the recommended CPU and RAM.

Starter’s 1-core, 2 GB allocation falls below that published full-stack minimum. Confirm whether a reduced service set is supported before choosing it for a specific workload.

No. This is hosting for a self-hosted Supabase environment. Supabase Cloud is Supabase’s separate managed platform with its own account, billing and features.

The self-hosted stack is one project. Cloud features such as managed backups, PITR and branching are not part of the standard self-hosted stack. Compare the features you depend on before migrating.

It provides backend services for an app you build. Your frontend still needs its own code and hosting. The frontend can connect to the Supabase API for data, authentication and other configured services.

Auth identifies the user; row-level security decides which database rows that user may access. A successful sign-in alone does not create correct data permissions.

1. Create the table and enable RLS.
2. Add policies for the intended roles and actions.
3. Test with two separate users to catch cross-account access.

Review Supabase’s RLS guide before exposing real customer records.

Use it where live changes improve the experience. A shared queue or presence display can benefit from subscriptions. Ordinary profile pages may work better with a normal request.

Realtime traffic and database changes use server resources. Test the number of connected clients and updates your workload needs.

Supabase Storage can manage files when configured in the deployment. Choose bucket access rules for public and private files, and budget disk space and backups for the content you retain.

The catalogue’s short feature list does not detail storage configuration. Confirm the supplied setup before relying on it for production uploads.

The hosting catalogue lists generated REST and GraphQL APIs. What a client can query still depends on your schema, grants and row-level security policies. Test the exact endpoints and permissions before connecting a production frontend.

The public plan list does not specify a backup schedule or point-in-time recovery. Supabase’s self-hosting guide says its managed backups and PITR do not come with the standard self-hosted stack.

Agree on who runs backups, where they are kept and how a restore is tested before production data depends on the instance.

The catalogue confirms automated installation and dedicated support, but does not define the ongoing maintenance scope. Confirm update cadence, incident handling and monitoring responsibilities for the selected plan.

Keep a record of stack versions and test key app journeys after upgrades.

Migration is possible, but the move is more than a database export. Inventory Auth users, files, functions, secrets and any Cloud-only features. Plan cutover and test the new endpoint with your app before switching traffic.

Use Supabase’s platform-to-self-hosted guide as the technical starting point.

Choose a standard VPS when you need your own mix of services. This offer is presented as a preconfigured Supabase environment. A standard VPS gives you a separate route for a custom stack.