SURVIVAL APPS2026 and the Return to Self-Hosting: What It Means for a Solo Developer
In the undergrowth of the net, people are going back to growing their own. For years the corporations handed out fertile land to anyone: you planted your project, it grew on their servers, and you never asked whose ground it was. Then the harvests got interesting, and the land stopped being free. Those who had only learned to sow, not to build the field, discovered the difference between farming and renting.
How we got here
We've watched the cycle repeat more than once: a hosting platform offers a generous free plan, a whole generation of projects is born on top of it, then the free plan shrinks or disappears — the most famous case is still Heroku, which in 2022 killed overnight the free tier that thousands of hobby projects were running on[1]. It isn't malice: it's the business model maturing. But for those who build, the lesson is always the same: what you don't pay for, you don't control; and often not even what you do pay for.
Meanwhile, on the other side of the scale, self-hosting has become radically more accessible. A VPS[2] with 2-4 GB of RAM now costs about as much as two coffees a month, and tools like Docker first, then open source deploy panels (Coolify, Dokploy and the like), have brought the "push and go live" experience to hardware you run yourself. The convenience gap between the managed platform and your own server, which ten years ago was a chasm, is now a flight of steps.
What a solo developer gains
- FLAT, PREDICTABLE COSTS — a VPS costs the same in January and in December. No usage-based surprises, no "your plan has been upgraded"
- NO LOCK-IN — if you stop liking your VPS provider, you move a backup and a docker-compose file. Migrating off a proprietary platform is a project; migrating between VPSs is an afternoon
- ONE SERVER, MANY PROJECTS — for anyone who piles up side projects, the platform model multiplies costs per project; your own server drives the marginal cost to zero
- SKILLS THAT STAY WITH YOU — every hour spent understanding nginx, systemd or backups is a tool you carry with you forever. Hours spent learning the proprietary dashboard of the moment, not so much
What it costs you (saying so is only honest)
Self-hosting isn't free: you pay in responsibility. Security updates are your business. Backups are your business — and a backup you've never test-restored is a superstition, not a backup. Uptime is your business: if the project you're hosting is a client's site with a contract, the difference between the 99.9% a provider guarantees and your server's "up pretty much always" has legal value, not just technical. That's why my position isn't ideological: self-hosting for your own tools and for projects that can afford an hour of downtime; managed infrastructure where downtime costs more than sovereignty.
> personal project / internal tool → own VPS
> sensitive data, full control → own VPS
> client site with SLA → managed hosting
> rule: OWN WHAT YOU CAN'T AFFORD TO LOSE
Frequently asked questions
Why are more and more developers going back to self-hosting?
Because the free plans of managed platforms are shrinking or disappearing (the best-known case is Heroku in 2022), while a VPS with 2-4 GB of RAM now costs about as much as two coffees a month, with deploy tools (Coolify, Dokploy) that have narrowed the convenience gap.
When does self-hosting make sense, and when managed hosting?
Self-hosting for personal projects, internal tools and sensitive data where you can afford an hour of downtime; managed hosting where downtime costs more than sovereignty, such as a client site with a contractual SLA.
What do you give up by moving to self-hosting?
Security updates, backups and uptime become your own responsibility — a practical example is the personal dashboard in Python stdlib and SQLite that runs on a self-managed server.
The construct points out that even it, technically, runs on someone else's server. Touché. No sovereignty is total — but the direction of the journey matters more than the destination.
Notes
- Heroku and the free tier — in August 2022 Salesforce announced the end of Heroku's free plans (free dynos, Postgres and Redis), effective at the end of November 2022, citing abuse and costs. It remains the textbook case, cited in every discussion of platform risk. ↑ back to text
- VPS — Virtual Private Server: a virtual machine with full root access, rented from a datacenter. The middle step between shared hosting and a dedicated physical server. ↑ back to text