Wunderlandmedia

Your SaaS Stack Is Bleeding You Dry. Here's What I Self-Host Instead.

I was spending over $400/month on SaaS tools I barely used. Here is the self-hosted stack that replaced most of them for under $50/month.

Kemal EsensoyModified on April 16, 2026
Your SaaS Stack Is Bleeding You Dry. Here's What I Self-Host Instead.
Insights & Ideas

Last month I did something I'd been avoiding for years. I opened a spreadsheet, pulled up every single recurring charge on my business accounts, and added them all up.

$437 a month. On SaaS tools. For a one-person agency.

Some of these I used daily. Some I used once a month. A few I'd genuinely forgotten existed. One was a project management tool I signed up for during a "productivity phase" in 2024 and never logged into again. It was still happily charging me $12 every month.

Here's the thing: none of these charges felt like a lot when I signed up. $15 here, $29 there. It's only $10 a month. But stack twenty of those on top of each other and suddenly you're bleeding over $5,000 a year on software you could replace with a $30 server.

So I did.

I Added Up My SaaS Bills and Almost Threw Up

I'm not being dramatic. Okay, maybe a little. But the feeling was real.

I'd been running Wunderlandmedia for over six years at that point, and every year the stack grew. A new analytics tool here, a monitoring service there, an automation platform because the old one raised prices. Each decision made sense in isolation. Together, they were eating my margins alive.

SaaS subscription costs adding up on a long unrolling receipt

Turns out I'm not alone. Research shows 42% of subscribers feel overwhelmed by recurring payments, and most people dramatically underestimate what they spend. The average consumer thinks they're paying about $86 a month on subscriptions. The actual number? $219. That gap is wild.

And it gets worse. 54.9% of people have at least one subscription they're not even using, and nearly 65% have been charged for a free trial they forgot to cancel. Sound familiar? I had three of those.

I'd written about SaaS ideas that burn your money before. Turns out I was doing the same thing to myself, just from the buyer's side.

The SaaS Tax on Small Agencies

For larger companies, SaaS spending is a known budget line. Companies with 10 to 100 employees spend between $250,000 and $1 million per year across 50 to 70 different apps. The average SaaS spend per employee hit $5,607 in 2026, up 7% from 2023.

But here's what nobody talks about: the math hits different when you're solo.

A 10-person agency can spread a $200/month tool across the team. For me, that same $200 comes straight out of my pocket. And per-user pricing means that if I ever do bring someone on, most of these costs instantly double or triple.

The global subscription economy reached $904 billion in 2026, with SaaS as the largest segment at $307 billion. That's a lot of recurring revenue flowing in one direction. And for small operators, every dollar of it compresses your margins further.

I learned early that pricing isn't just about what you charge, it's about what you keep. And I was keeping less than I thought.

What I Actually Replaced (And What I Didn't)

Let me be specific about what I swapped. No vague "just self-host everything" advice. Here's my actual before and after:

What I replaced:

  • Vercel (hosting/deployments) replaced with Coolify on a Hetzner VPS
  • Zapier (automations) replaced with n8n (self-hosted)
  • Google Analytics replaced with Plausible (self-hosted, GDPR-compliant, no cookie banner needed)
  • Calendly replaced with Cal.com (self-hosted, open source)
  • 1Password Teams replaced with Vaultwarden (Bitwarden-compatible, self-hosted)
  • Paid uptime monitoring replaced with Uptime Kuma (self-hosted)
  • Website change monitoring replaced with ChangeDetection.io, which I've written about before

Developer replacing SaaS tools with self-hosted alternatives on a single server

What I kept as SaaS:

  • Email (Fastmail). Self-hosting email is a nightmare. Deliverability alone makes it not worth it.
  • Domain registrar (Cloudflare). Obviously.
  • Figma. No real self-hosted alternative that doesn't make me want to throw my laptop.
  • Claude/AI tools. These earn their subscription many times over.

The key insight: I didn't try to replace everything at once. I started with the tools where the self-hosted alternative was clearly mature and the SaaS cost was hard to justify.

Coolify Is the Backbone of My Self-Hosting Setup

If you're going to self-host anything, you need a platform to manage it all. For me, that's Coolify.

Think of it as a self-hosted Heroku or Vercel. You point it at a VPS, connect your Git repos, and push to deploy. It handles container orchestration, SSL certificates, database management (Postgres, MySQL, Redis, the works), and automatic backups. All from a clean web UI.

Coolify self-hosting platform managing multiple app deployments from a single server

The numbers speak for themselves. Coolify has over 52,000 GitHub stars and 325,000+ users. It's Apache 2.0 licensed, meaning the self-hosted version is free forever.

I already wrote about how Coolify saved my Next.js builds, but it does way more than that. It's the single tool that makes everything else possible. Every self-hosted app I run, from Plausible to n8n to Cal.com, lives inside Coolify containers on a Hetzner VPS.

Here's the cost comparison that convinced me: one analysis showed that a managed Coolify setup at $89.99/month handled the same workload as a $601 Vercel bill. That's 85% cheaper for identical functionality. And if you manage it yourself on a VPS, it's even less.

The Honest Downsides of Self-Hosting

I'd be lying if I said this was all upside. It's not. And I think the self-hosting community sometimes undersells the real costs.

You become your own IT department. When Plausible throws an error at 11pm, there's no support ticket to file. It's you, a terminal, and Docker logs. If you don't know your way around a server, this will eat your evenings.

The upfront time investment is real. Setting up my full stack took about 8 to 10 hours spread over a weekend. That's not nothing. And I already knew Docker and basic server administration. If you're starting from zero, double that estimate.

Updates are on you. SaaS tools update themselves. Self-hosted tools need you to pull new versions, test them, and deal with breaking changes. Coolify makes this easier with one-click updates for most things, but it's still a responsibility.

It's not actually free. A realistic production stack with proper monitoring, backups, and enough resources runs about $30 to $50 a month in server costs. Not $0. Anyone telling you self-hosting is completely free is forgetting the electricity bill and their own time.

As I've learned with AI-built software, things break when you're not looking. Self-hosted tools are no different. You need to actually maintain them.

My Actual Monthly Cost Breakdown

Here's what I actually pay now versus what I was paying before:

Before (SaaS): ~$437/month

  • Vercel Pro: $20
  • Zapier: $49
  • Google Workspace (extra storage): $12
  • Calendly Pro: $12
  • 1Password Teams: $8
  • Analytics tools: $39
  • Monitoring tools: $25
  • Various smaller subscriptions: ~$272

After (self-hosted + remaining SaaS): ~$85/month

  • Hetzner VPS (2 servers): $38
  • Remaining SaaS (email, domains, Figma, AI): $47

Balance scale comparing SaaS costs versus self-hosting savings

Net savings: ~$350/month, or about $4,200 per year.

Factor in the 8 to 10 hours of initial setup and maybe 2 to 3 hours of maintenance per month, and the ROI is still overwhelming. I'm saving over $4,000 a year in exchange for about 30 hours of work annually. That's over $130 per hour of "maintenance time," which is better than most of my billable rates.

For a team of 10, the math gets even more dramatic. Per-user SaaS pricing means you could be looking at $500 to $3,000 per month in tools that a $50 server could replace.

Should You Actually Do This?

Honest answer: it depends.

If you're a developer or agency owner who's comfortable with a terminal, basic Docker commands, and the occasional late-night debugging session, yes. The savings are significant and the tools are mature enough for production use.

If the words "SSH" and "container" make you nervous, maybe not yet. Or at least, start very small.

Best first candidates for self-hosting:

  • Analytics (Plausible or Umami). Dead simple to set up, immediate cost savings, and you get better privacy compliance as a bonus.
  • Uptime monitoring (Uptime Kuma). Literally takes 5 minutes to deploy on Coolify.
  • Deployments (Coolify itself). This is the big one that unlocks everything else.

Worst candidates for self-hosting:

  • Email. Please don't. Deliverability is a full-time job.
  • Authentication providers. Security is not where you want to cut corners.
  • Payment processing. For obvious legal and compliance reasons.

The SaaS subscription fatigue is real, and it's only getting worse as more tools move to per-seat pricing. But the solution isn't to rage-quit every subscription overnight. It's to be intentional about what earns its monthly fee and what doesn't.

Start with one tool. Replace it. Live with it for a month. If it works, replace another. That's how I did it, and I haven't looked back.

If your website needs optimization beyond just the hosting layer, that's a bigger conversation. But getting your infrastructure costs under control is a solid first step.

Ready to stop bleeding money on SaaS you barely use? Let's talk about building a leaner, self-hosted stack that actually fits your business.

About the Author

KE

Kemal Esensoy

Kemal Esensoy, founder of Wunderlandmedia, started his journey as a freelance web developer and designer. He conducted web design courses with over 3,000 students. Today, he leads an award-winning full-stack agency specializing in web development, SEO, and digital marketing.

SaaS Subscription Fatigue? Self-Host Instead | Wunderlandmedia