Must have
Hard prerequisites
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.
- Persistent database and file-storage volumes.
- Configured application URLs, passwords and service secrets before public access.
Application hosting
Hosting Supabase
A backend platform built around PostgreSQL, with authentication, storage, realtime features and functions. Self-hosting gives you control over the deployment and responsibility for its operation.
- Min vCPU
- 2
- Min memory
- Depends on workload
- Min storage
- Depends on workload
Recommended
Documented guidance
No further general recommendations are published for this version.
Published starting requirements
The documented stack minimum is 4 GB RAM, 2 CPU cores and 40 GB SSD. Recommended resources are 8 GB+ RAM, 4+ cores and 80 GB+ SSD. These published GB values are not exact GiB values. Enabling optional services changes resource needs.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
The host must provide
Runtime
- Docker Compose
- Use the maintained official stack
- PostgreSQL
- Provided by the stack
Storage
Persistent data
Preserve the PostgreSQL and Storage volumes and any deployed function files. Plan database and object-storage backups separately.
Step by step
Plan a self-hosted Supabase deployment
-
Configure the stack
Follow the maintained Compose instructions and replace example passwords and keys before exposing any services.
Official instructions -
Prepare operations
Arrange backups, monitoring and upgrades; self-hosting leaves these responsibilities with the operator.
Official instructions
Security
Before you go public
- Keep privileged service keys server-side.
- Protect the dashboard and configure HTTPS for public endpoints.
Cost
Beyond the server price
- Include backups, outbound traffic, email delivery and maintenance in the budget.
Matching plans
Plans with published evidence
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Git, Docker Engine and Docker Compose on Linux, or Docker Desktop on a supported host.This prerequisite has no comparable published plan field.
- Persistent database and file-storage volumes.This prerequisite has no comparable published plan field.
- Configured application URLs, passwords and service secrets before public access.This prerequisite has no comparable published plan field.
Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.