How much would you save self-hosting your stack?
Plug in your current SaaS bills. See real savings against an honest VPS cost. Get a personalized roadmap for what to host first.
Your current SaaS spend
Pick what you're on (or leave a category blank if you don't use it). Defaults are based on common 2026 plan pricing. Override with your actual bill.
VPS estimate is honest, not magical. It scales with how much you're hosting (light: $6/mo VPS S → heavy: $25/mo VPS L). Real provider picks are in the VPS providers directory.
Your self-hosting roadmap
Ordered by impact (highest-cost line first). Tackle them in any timeframe that works for you — some people migrate in a weekend, others spread it over months. The order matters more than the speed.
When self-hosting is exactly right for you
Saving money is the obvious win. But for the right builder, self-hosting unlocks something more valuable than the savings: freedom to experiment, ship faster, and own your stack forever.
Want to try a self-hosted analytics tool, a Discord alternative, a niche password manager? With Coolify on your VPS, deploy it in one click. No new card, no new trial, no new subscription. Self-hosting drops the cost of curiosity to zero.
A $12/mo VPS can run 10+ small projects side by side. Client demos, throwaway prototypes, weekend builds. None of them adds a separate bill. Your monthly cost stops scaling with how much you ship.
Every SaaS abstracts something away. Self-hosting puts you face-to-face with databases, queues, DNS, SSL, networking. That knowledge compounds across every project you build for the rest of your career.
No signup forms, no payment approvals, no waiting. Need a database? Container's already running. Need email sending? Postal's right there. Friction is the silent killer of side projects — self-hosting kills the friction.
The side project you built three years ago and forgot about? Still running. No subscription to reactivate, no plan that got deprecated, no forced migration to a new tier. You own the data, the config, all of it.
The first self-hosted tool takes a weekend. The second takes an evening. The fifth takes 20 minutes. Each one teaches you patterns you reuse in the next. SaaS skills don't transfer like this — knowing one platform doesn't help you with the next.
The honest test: if you're the kind of builder who reads release notes for fun, likes understanding what's under the hood, and wants to ship more without scaling your monthly bills, self-hosting is one of the highest-leverage skills you can pick up. Most of Hasan's own products live on the same stack he teaches.
When you should NOT self-host
Self-hosting saves money, but it costs time, attention, and a willingness to be the one who fixes things. Here's when paying for SaaS is the right call.
Linux, Docker, DNS, SSL certificates, backups. You don't need to be an expert, but you need to be willing to learn. If you'd rather not, the SaaS bill is worth it.
Self-hosted means you're ops. The day something goes down, that's your Saturday. SaaS providers have on-call engineers. You don't.
If you're not shipping your actual product because of low-leverage work, adding infrastructure to your plate is the wrong move. Ship first, optimize cost later.
Nothing wrong with this. Some people love the infrastructure layer; others want to stay focused on product, marketing, or design. Know which one you are.
SOC2, HIPAA, or strict GDPR requirements that the SaaS provider already meets? Self-hosting puts that responsibility on you. Often not worth the savings.
If your total SaaS spend is under $40/month, self-hosting probably costs more time than it saves money. The math works at scale, not at small.
The honest test: if reading this list made you nod along, self-hosting probably isn't for you right now. That's a real answer, not a failure. Come back when your SaaS bills are bigger and your time is freer.
Frequently asked questions
Honest answers to the questions builders ask before they commit to the swap.
How accurate are these savings estimates? ▾
The defaults use representative 2026 plan pricing for each SaaS provider, and the math subtracts an honest VPS cost (not zero). Your real number will vary based on your actual bills, usage volume, and which plans you're on — override any price field with your real invoice to get a precise estimate.
Is self-hosting actually worth the time? ▾
Below ~$40/month of total SaaS spend, the math rarely works — your time is worth more than the dollars you'd save. Above ~$100/month, the savings compound: every new tool you self-host adds revenue without adding a subscription. Many builders also find the ops experience and stack ownership more valuable than the dollar savings.
How big a VPS do I actually need? ▾
This calculator scales VPS cost with category count: light setup (1–2 tools) on a ~$6/mo VPS, medium (3–4) on ~$12/mo, heavy (5+) on ~$25/mo. A single mid-tier VPS comfortably handles email + hosting + databases + automation for most solo builders. Real provider picks are in the VPS providers directory.
What if I'm not technical enough to self-host? ▾
Coolify makes most of the work click-through — deploys, HTTPS, persistent databases, one-click updates. Postal SMTP, Mautic, n8n, and PyRunner all install in roughly 5–30 minutes following the guides on this site. The learning curve is real but bounded; you're not running infrastructure for thousands of strangers, just yourself.
What happens if my server goes down? ▾
For a solo-builder stack: take nightly automated backups (one cron command), host on a reputable VPS provider, and you're at ~99.9% uptime. The same outage risk exists with SaaS — you just don't see it. Self-hosting moves reliability into your control instead of theirs.
Ready to start self-hosting?
If the math works for you and the warning list didn't scare you off, the next step is picking the right VPS and learning the stack. The Self-Hosting Course walks through every piece — the same setup Hasan uses across all his own products.