You know the feeling. That monthly SaaS invoice that makes your stomach drop. $29 for analytics. $49 for something else. And the worst part? They own your data. Privacy regulations tighten, and you’re stuck. You want sovereignty. You want control. So you decide to self-host.
But here’s the dirty secret nobody tells you: What we call ‘self-hosting’ today is actually just distributed renting from Big Tech’s free tiers. You’re not running your own servers. You’re orchestrating a fragile ballet of Cloudflare Workers, Fly.io containers, and Supabase databases. You’ve traded a single vendor lock-in for a multi-point failure cascade. And you’re paying for it in complexity, not cash.
I spent last weekend building exactly this stack. Umami — the privacy-first analytics — running on Cloudflare Pages, Fly.io for the backend, Supabase for the database. All free tiers. All zero dollars. It felt like a win. Until I realized I’m now holding 12 different ‘you’ve exceeded free tier limits’ emails waiting to happen.
Let’s be honest. You’re not doing this because you love managing infrastructure. You’re doing it because the SaaS industry has made you feel like a hostage to your own data. You want out. And you’ve found a clever loophole: stitch together three giant corporations’ free offerings into your personal analytics stack. Genius? Absolutely. Sustainable? That’s the question.
I built it. Umami tells me how many people visit my blog without selling their soul to Google Analytics. The setup is elegant: Cloudflare Pages serves the static frontend, Fly.io runs the Node server, Supabase stores the events. Each component is a free-tier masterpiece. Each component is also a single point of failure. When Fly.io changes their free plan next quarter, my analytics disappear. When Supabase decides to limit row counts, my data gets truncated.
But here’s the twist: The fragility is the feature, not the bug. By embracing the ephemerality of free tiers, you’re forced to keep things simple. You can’t offload gigabytes of useless tracking. You can’t scale to millions of events. You’re forced to design for a modest scale, which is exactly what most indie hackers and small creators need. The constraint becomes the guardrail.
I’m not saying you shouldn’t do it. I’m saying you should know what you’re signing up for. You’re trading predictable cost for unpredictable complexity. You’re trading a single neck to choke for a distributed chaos. But if you’re willing to accept that your ‘self-hosted’ stack is actually a leased condo in Big Tech’s sprawling development, then yes — it’s brilliant.
This works because you’re not really self-hosting. You’re subletting. And subletting requires vigilance. You need to monitor the health of each platform. You need to have an exit plan when Fly.io introduces a usage cap. You need to accept that your free tier is a gift that can be revoked at any moment.
True digital sovereignty doesn’t come from stitching free tiers together. It comes from understanding the trade-offs and making peace with them. So go ahead. Build your Umami stack. Feel that thrill of outsmarting the SaaS economy. But remember: you’re not a rebel hacking the system. You’re a tenant who’s figured out how to pay rent with favors instead of cash. And that’s okay — as long as you know your lease might expire.
FAQ
Q: Isn't this just a more complex version of using a hosted analytics service?
A: Yes and no. You retain full data ownership and avoid privacy regs like GDPR by not sending data to third parties. But you introduce operational risk: three separate free tiers can each change their terms. The trade-off is control vs fragility.
Q: What happens when one of these free tiers shuts down or changes pricing?
A: Your stack breaks. You need to rebuild that component. This is why the 'self-hosting' label is misleading — you're not hosting, you're borrowing. Have a migration plan for each piece: export your Supabase data, keep your Cloudflare Pages code portable, and design your Fly.io deployment to be easily redeployable elsewhere.
Q: Is this actually cheaper than paying for a $10/month analytics SaaS?
A: Financially, yes — zero dollars. But your time and attention are not free. Every time a free tier limit shifts, you spend hours debugging. For most indie hackers, the $10/month SaaS is cheaper if you value your time. The real win is data sovereignty and privacy compliance, not cost savings.