Supabase Hosting — Starting From $12.99/mo
Self-Hosted Supabase on Your Own Cloud
Deploy the Supabase stack with Postgres, Auth, Storage, Realtime, Studio, API services, and Edge Functions on persistent infrastructure.
- Full self-hosted Supabase service stack
- Persistent Postgres, secure endpoints, logs, and scalable resources
Supabase hosting plans sized for a real backend stack
Supabase self-hosting runs several services around Postgres, so the starter tier follows the documented 2-core, 4 GB RAM, and 40.
Monthly
Yearly (2 months free)
Backend Starter
For development, internal tools, prototypes, and smaller production backends.
$12.99 /month
$129.90 /year
Transparent monthly billing. Upgrade, downgrade, or add resources as your workload changes.
2 MONTHS FREE-
2 vCPU CPU
-
4 GB RAM
-
40 GB NVMe storage
-
PostgreSQL database
-
Supabase Auth & REST API
-
Storage & Realtime services
-
Supabase Studio
-
Edge Functions ready
-
Custom domain & SSL
-
Persistent volumes & logs
More Features
Less Features
Backend Production MOST POPULAR
For production applications with more database traffic, storage, and concurrent users.
$24.99 /month
$249.90 /year
Transparent monthly billing. Upgrade, downgrade, or add resources as your workload changes.
2 MONTHS FREE-
4 vCPU CPU
-
8 GB RAM
-
80 GB NVMe storage
-
Recommended production headroom
-
PostgreSQL + connection pooler
-
Auth, REST, Storage & Realtime
-
Supabase Studio
-
Edge Functions ready
-
Custom domain & SSL
-
Backup-ready persistent volumes
More Features
Less Features
Backend Scale
For larger self-hosted backends with heavier database, Realtime, API, and storage activity.
$49.99 /month
$499.90 /year
Transparent monthly billing. Upgrade, downgrade, or add resources as your workload changes.
2 MONTHS FREE-
8 vCPU CPU
-
16 GB RAM
-
160 GB NVMe storage
-
Higher database headroom
-
More concurrent service capacity
-
Auth, REST, Storage & Realtime
-
Supabase Studio
-
Edge Functions ready
-
Custom domain & SSL
-
Priority resource allocation
More Features
Less Features
Own the backend stack behind your application
Self-hosted Supabase combines a full Postgres database with Auth, Storage, Realtime, REST APIs, Studio, connection pooling, and Edge Functions. OnePloy packages that multi-service architecture into a repeatable deployment with persistent NVMe storage, secure environment configuration.
Deploy the Supabase services together, not one container at a time
Start with the complete backend stack on persistent infrastructure, then connect your frontend or API clients through a secure public.
-
PostgreSQL Foundation: Run the full Postgres database at the center of the Supabase architecture with persistent storage.
-
Auth, Storage & APIs: Keep the core application services deployed together instead of managing separate providers for each layer.
-
Realtime & Edge Functions: Support live database-driven experiences and self-hosted server-side functions in the same backend environment.
-
Studio & Connection Pooling: Keep operational access to the dashboard and database connection layer that make the self-hosted stack practical.
Keep application data on infrastructure you control
Self-host when your architecture, compliance needs, cost model, or product requirements call for direct control.
Scale the backend as users, data, and connections grow
Increase CPU, memory, and NVMe capacity as Postgres load, API traffic, Realtime clients, Storage usage.
View Pricing View Pricing
The Supabase backend services your product depends on
OnePloy keeps the full stack together while giving each deployment persistent storage, predictable resources, secure configuration, and operational.
PostgreSQL Database
Run the full relational database that powers Supabase with persistent.
Authentication Services
Use the Supabase authentication layer for sign-ups, logins, sessions, and.
Object Storage
Keep file and object storage services alongside the database and.
Realtime Updates
Broadcast database changes to connected clients when your application needs.
REST API Layer
Expose database-backed application data through the Supabase API services without.
Edge Functions
Run self-hosted server-side functions alongside the rest of the backend.
Supabase Studio
Use the browser dashboard to inspect and manage the self-hosted.
Database Connection Pooling
Keep connection pooling in the architecture so application traffic does.
Why developers self-host Supabase on OnePloy
Synthetic launch testimonials written around common self-hosting requirements such as data control.
We wanted Supabase features but needed the database and services on infrastructure we control. OnePloy made the multi-container.
The resource sizing is realistic. A full Supabase stack is not a 512 MB hobby container, so starting.
Having Postgres, Auth, Storage, Realtime, and Studio deployed as one backend environment gives our team a clear operational.
We use the production tier because database traffic matters more to us than the absolute lowest price. Persistent.
For client projects that require self-hosting, this is much faster than building the Docker environment from scratch every.
who want simpler cloud deployment without giving up control.
Support for the infrastructure behind self-hosted Supabase
Runtime Configuration
Get help with the OnePloy service, persistent data, environment settings, domains, and the deployment configuration around Supabase.
Resource Sizing
Increase CPU, memory, or storage when production usage shows the current tier no longer has enough headroom.
Logs & Service Health
Use runtime output and service health to distinguish infrastructure problems from application or provider configuration issues.
Supabase Hosting FAQs
What teams should know before running the official self-hosted Supabase stack on OnePloy.
The self-hosted Supabase architecture centers on Postgres and includes services such as Auth, PostgREST, Realtime, Storage, Studio, an API gateway, connection pooling.
Supabase documentation lists 4 GB RAM, 2 CPU cores, and 40 GB SSD as the minimum for running all components, with 8.
Yes. Your frontend connects to the Supabase API and authentication endpoints exposed by the deployment. The client framework is independent of where.
The Postgres data directory and other stateful service data should live on persistent volumes. OnePloy configures the hosting page around persistent storage.
Yes. Move to more CPU, memory, and NVMe storage as your database grows or API, Realtime, Storage, and Edge Function usage becomes.
Still have a deployment or sizing question? Contact Us Contact Us
Connect your Supabase backend to the rest of your stack
Deploy the frontend and supporting data services that commonly sit beside a.
PostgreSQL Hosting
Need only the database? Run a dedicated PostgreSQL instance without the additional.
Explore
Popular apps and services you can deploy with OnePloy
