Self-host everything, slot by slot, without rewriting your app
Every managed layer of your stack has an open source equivalent you can run on your own server: Coolify instead of Vercel, Ollama instead of a model API, GlitchTip instead of Sentry, OpenReplay instead of PostHog. The recipe stays the same, only the provider of each brick changes.
Why
The bill does not disappear. It moves to another line. Self-hosting gets sold to you as savings. Not false, just incomplete. What you stop paying in subscriptions, you pay in a server to maintain, security updates, backups to actually test, and above all hours. The right question is not "how much do I save", it is "will anyone here still be running this in six months". If the answer is no, you just converted a predictable expense into invisible debt. What makes this move practical is that it forces no rewrite. Every brick swaps out at constant recipe: your app still talks to a Postgres…
When
This kit's axis: managed versus self-hosted. Every brick exists in two versions, you pick yours slot by slot in the tool list above. The kit assumes the self-hosted version, the managed one stays reachable on each line. ✅ You know it's your kit when You have a sovereignty constraint: health data, public sector, a client demanding nothing leaves your infrastructure A cost line has become…
Tools included
- Coolify
- Glitchtip
- Supabase
- Ollama
- Kokoro
- Openreplay
- Asterisk
- Stripe