Self-hosting a small SaaS in 2026 is cheaper, easier, and more reliable than it has ever been — and yet most indie founders still default to the most expensive cloud they can find. This guide is the alternative stack: simple components, sensible providers, real monthly numbers, and the parts no one talks about until 2am.
It is the setup we use for our own projects.
What changed in 2026
Three shifts made self-hosting realistic for small teams again.
- Hetzner, OVH, and Latitude.sh keep eating market share. A 4-vCPU 16 GB box is under $20/month.
- Managed Postgres is commoditized. Neon, Supabase, Crunchy, Render — pick one and forget about replication.
- Coolify, Dokploy, and Caprover matured. PaaS-style deploys on your own hardware, no Kubernetes.
How we picked the stack
Five rules.
- Boring tech only
- Managed where data lives
- Self-hosted where compute lives
- Backups before launch, not after
- Monitoring on day one
1. Compute — one VPS, then two
Start with one Hetzner CCX or AX box. $20–$50/month gets you 4–8 cores and 16–32 GB of RAM, which is more than enough for thousands of users. Run Docker Compose, Coolify, or Dokploy. Add a second box only when you need redundancy or when you split workloads.
The trade-off: you are responsible for the operating system. Plan an hour a month for patching.
2. Database — managed, always
Run Postgres on Neon, Supabase, Crunchy Bridge, or DigitalOcean Managed Databases. $20–$40/month for a small instance with daily backups, point-in-time recovery, and a real on-call team. Self-hosting Postgres for a SaaS is one of the few places where the cheap option is the wrong option.
3. Storage, email, monitoring
Object storage on Cloudflare R2 or Backblaze B2 — both about $0.005/GB and zero egress fees. Transactional email on Resend, Postmark, or Mailgun — $10–$20/month for the volume a small SaaS will hit. Monitoring on Better Stack, Uptime Kuma (self-hosted), or Hyperping. Error tracking on Sentry's free tier or self-hosted GlitchTip.
Comparison: Self-hosted SaaS stack in April 2026
| Component |
Pick |
Monthly cost |
Notes |
| VPS |
Hetzner CCX |
$20–$50 |
EU + US locations |
| Postgres |
Neon or Supabase |
$20–$40 |
Always managed |
| Object storage |
Cloudflare R2 |
$1–$5 |
No egress fees |
| Email |
Resend / Postmark |
$10–$20 |
Watch bounce rate |
| Monitoring |
Better Stack |
$0–$15 |
Free tier works |
Common mistakes to avoid
Self-hosting your database. It is the single workload where managed is worth it. The cost of a 3am page is higher than the price difference.
Skipping backups. "I'll set it up next week" is how data loss happens. Test the restore on day one.
Going to Kubernetes. Unless you have a real multi-region distributed-systems problem, Docker Compose plus a single VPS is a better answer for years.
FAQ
Is self-hosting compliant with SOC 2?
Yes, but you take on more of the work. Managed providers (Neon, Resend, Cloudflare) carry compliance certifications you can inherit.
What about Kamal or Coolify?
Both are great. Kamal is a deploy tool, Coolify is a full PaaS. Pick whichever fits your operational comfort level.
When should I leave self-hosting?
When the time you spend on infrastructure costs more than the savings. For most indie SaaS, that is somewhere past $10k MRR.
Where to go next
For related guides see How to ship a SaaS in 30 days in 2026, Cost of running a side project in 2026, and Best web hosting for developers in 2026.