Need a comparison that includes operations rather than only a VM price? WZ-IT assesses the target architecture and offers a Supabase migration from €3,490 plus ongoing managed operations.
Supabase cost is not a single monthly fee. In Supabase Cloud it depends on plan, compute, database, storage, egress, auth usage and add-ons. Self-hosting includes infrastructure and complete platform operations.
A fair comparison therefore uses Total Cost of Ownership (TCO) and compares the same service level on both sides.
Current Supabase Cloud plans
The official Supabase pricing page lists these entry points on 25 August 2026:
| Plan | Entry price | Typical position |
|---|---|---|
| Free | $0 | Development, testing and small projects |
| Pro | from $25/month | Production projects and teams |
| Team | from $599/month | Advanced team, governance and support requirements |
| Enterprise | custom | Larger organisations and contractual requirements |
The entry price is not necessarily the eventual bill. Relevant variable items include:
- compute size and number of projects
- database and storage volume
- egress and image transformation
- monthly active users and selected auth capabilities
- realtime usage and function invocations
- custom domains
- Point-in-Time Recovery
- support and team capabilities
Limits and included usage change. A current decision should use the official calculator with real workload data.
Cloud backup and PITR cost
Supabase documents daily database backups with plan-dependent retention for paid plans. Point-in-Time Recovery is priced separately and requires eligible compute. The backup documentation currently lists approximately $100 per month for seven days of PITR retention, $200 for 14 days and $400 for 28 days.
These database backups do not include files stored through the Storage API, only their metadata. A complete independent backup still needs a strategy for storage objects.
What self-hosting costs
Direct infrastructure
- servers or virtual machines
- block, object and backup storage
- network, traffic and public IPs
- load balancer or reverse proxy
- domain, DNS and TLS automation
- off-site backup and potentially a WAL archive
- monitoring and log storage
One-time project work
- architecture and sizing
- installation and hardening
- SMTP, domains and auth providers
- backup and restore design
- monitoring, alerting and documentation
- migration from an existing platform
- testing and production handover
Recurring operations
- operating-system and platform updates
- Supabase and PostgreSQL upgrades
- backup assurance and restore tests
- capacity and performance analysis
- vulnerability and configuration review
- incident response and on-call coverage
- documentation and change management
The most common error is treating self-hosting as a server invoice. An inexpensive VM does not replace recovery or competent response.
A practical TCO formula
For a 36-month period, a simplified model is:
Cloud TCO = plans + compute + usage + add-ons + internal support
Self-hosted TCO = setup + migration + infrastructure
+ operations + on-call + recovery effort
Both sides should deliver the same objectives. A Cloud project with daily backup should not be compared to a self-hosted server without off-site protection. A highly available Cloud service should not be compared to a single Docker host either.
Four common cost scenarios
1. MVP or new application
Cloud is usually more economical. There is no stable load profile and platform operations would distract the development team too early.
2. Predictable production application
Self-hosting can become interesting when load, storage and operational objectives are known and platform tasks can be operated efficiently across multiple workloads.
3. Storage- or egress-heavy workload
Customer-controlled infrastructure may provide a different cost profile. Object backup, capacity, availability and transfer paths still need an engineering solution.
4. Critical application with HA and on-call
Infrastructure cost rises in both models. Self-hosting requires multiple failure domains, PostgreSQL HA, redundant storage, monitoring and response. The required service level matters more than the cheapest VM.
Migration cost
A cloud-to-self-hosted move covers more than PostgreSQL. Auth, Storage, Functions, secrets, application configuration, a rehearsal and cutover all affect the effort. WZ-IT offers a Supabase migration from €3,490 excluding VAT as an individually scoped project entry. Binding scope and price follow the technical assessment.
After migration, either internal operating cost or a monthly managed-service fee remains. It belongs in the TCO model before approving a cloud exit.
Cost is not the only decision factor
The assessment should also include:
- availability and recovery objectives
- required Cloud capabilities
- operating location and private data paths
- internal platform capability
- planned product development
- key-person dependency
- time to production
An economical cloud exit is an outcome of engineering and operations. Starting self-hosting for a small monthly difference alone often underestimates the lasting responsibility.
