Self-hosted Supabase is not one small application. It is a stack built around PostgreSQL plus authentication, APIs, realtime services, storage components, and supporting containers. That makes server sizing closer to a multi-service platform than to a basic database VM.
The right VPS depends on which Supabase services you actually enable, how large PostgreSQL becomes, and whether storage and backups live on the same machine.
Key takeaways
- 4 GB is a practical minimum for small self-hosted Supabase stacks.
- 8 GB is more comfortable for production, larger databases, and multiple services.
- PostgreSQL usually determines the long-term memory and storage requirement.
- Docker Compose simplifies deployment but persistent state still needs backups.
- Storage and backup growth should be planned separately from compute.
Why self-hosted Supabase needs more than a tiny VPS
The stack combines several services, each with its own memory and process overhead. A server that can run PostgreSQL alone may feel constrained once auth, realtime, APIs, storage, and proxy services are added.
Four gigabytes is a useful starting point for small development or light production deployments.
PostgreSQL is the core capacity driver
Database size, cache requirements, query load, and connections grow with application usage. Eight gigabytes gives more room for PostgreSQL plus the surrounding services.
Tune database memory to the actual server rather than copying settings from larger managed environments.
Docker and persistent storage
Containerization makes the stack reproducible but does not protect data. PostgreSQL, object storage, configuration, and secrets need deliberate persistence and backup.
Monitor disk use from database growth, logs, and stored files.
When to stop self-hosting
Self-hosting gives control but also transfers upgrades, security, backups, monitoring, and incident response to you. Managed Supabase can be cheaper in total effort when infrastructure operations are not part of the product.
Use self-hosting when control, locality, or architecture requirements justify the work.
Frequently asked questions
How much RAM does self-hosted Supabase need?
Four gigabytes is a practical minimum for a small stack, while 8 GB is more comfortable for production.
Does Supabase require Docker?
The self-hosted stack is commonly deployed with Docker Compose, though the underlying requirement is running its component services reliably.
What is the main bottleneck in self-hosted Supabase?
PostgreSQL, storage growth, and the combined memory use of multiple services are common constraints.
Should I self-host Supabase?
Do so when control or infrastructure requirements justify maintaining the full stack yourself.