Something strange has been happening on r/selfhosted, r/homelab, and the various Discord servers where developers talk about their personal infrastructure. The activity has been climbing for years. The questions have gotten more sophisticated. The hardware purchases have gotten more serious. After almost two decades of every developer dutifully moving their stuff to the cloud, a significant slice of the developer population is quietly moving it back.

This isn't a fringe movement anymore. It's not just retired sysadmins running Plex servers in their basements. It's working developers (people who use AWS at their day jobs) building serious infrastructure at home and self-hosting services they used to pay for. The reasons are worth understanding because they tell you something about where the industry is heading.

The cloud bill that broke the camel's back

The first reason is the simplest. Cloud bills got expensive. A small startup that spends 500 dollars a month on AWS is doing fine. A small startup that spends 5,000 dollars a month is starting to question its life choices. A small startup that spends 50,000 dollars a month (and there are many of these) is paying more for cloud infrastructure than it would cost to hire a full-time engineer to manage their own.

The cloud was sold as cheaper, but for many workloads it's only cheaper at small scale or extremely large scale. The middle tier, too big for free tiers and too small for negotiated enterprise pricing, gets crushed. A lot of the engineers building at this middle tier started doing the math and realized they could buy a few used servers, host them in a colocation facility, and save 80 to 90 percent of their monthly cloud spend.

The same math works at the personal level. A developer paying 30 dollars a month for a managed Postgres database, 10 dollars a month for object storage, 15 dollars a month for hosting, 8 dollars a month for transactional email, and another 20 for various other services is spending 80 dollars a month on infrastructure. That's almost a thousand dollars a year. For a thousand dollars you can buy a used Dell PowerEdge server, a UPS, and have change left over. The server lasts for years.

Sovereignty and control

The second reason is more philosophical and harder to put a number on. People are tired of their data living on someone else's computer. They're tired of services they depend on getting acquired and ruined, or being shut down without warning, or quietly changing their terms of service in ways that make the tool unusable for the original purpose.

Every developer over thirty has a long list of dead services they used to rely on. Google Reader. Heroku's free tier. Tumblr. Sunsetted Google products too numerous to count. Twitter's API changes. Reddit's API changes. The pattern is consistent: you build your workflow around a service, the service makes a business decision that breaks your workflow, you start over.

Self-hosting solves this completely. If you self-host your RSS reader, nobody can shut it down. If you self-host your photo storage, nobody can scan your photos for ads. If you self-host your password manager, nobody can have a data breach that exposes your credentials. The services you control will keep working as long as you keep them running. There's no vendor lock-in because you are the vendor.

This is especially appealing for developers because we tend to be the kind of people who value control. We picked careers where we get to tell computers exactly what to do. Then we spent twenty years giving up that control to managed services in exchange for convenience. Some people are starting to wonder if the trade was worth it.

The tooling has gotten incredibly good

The third reason is purely practical. Self-hosting in 2026 is dramatically easier than it was in 2010. The open source community has spent the last decade building tools that make it possible to run sophisticated services with very little operational overhead.

Docker and Docker Compose let you run any application as a single command. You don't need to worry about dependency conflicts or installation procedures or environment setup. The application comes packaged with everything it needs. Want to run a self-hosted RSS reader? docker compose up -d and you have one. Want to run a self-hosted password manager? Same thing. Want to run a self-hosted git server? Same thing.

Reverse proxies like Caddy and Traefik handle automatic HTTPS certificates from Let's Encrypt with zero configuration. You no longer have to know how to generate a certificate signing request or configure nginx to renew SSL certs. You just point Caddy at your service and it works. This was hard in 2014. It's effortless in 2026.

Tools like Cloudflare Tunnels let you expose self-hosted services to the internet without opening ports on your home router. Your service can live on a Raspberry Pi in your closet and be accessible from anywhere in the world without you ever touching your firewall. The security model is excellent and the setup takes about ten minutes.

The applications themselves have gotten dramatically better too. Self-hosted alternatives to commercial services used to be janky open source projects with bad UIs. Now many of them are actively better than the commercial versions they replace. Vaultwarden replaces Bitwarden. Immich replaces Google Photos. Nextcloud replaces Google Drive. Jellyfin replaces Plex (which itself replaces Netflix for many use cases). PiHole gives you network-wide ad blocking that no commercial service offers. The list keeps growing.

What people are actually self-hosting

The current wave of self-hosting isn't about running Linux From Scratch on dusty hardware. People are running serious services with good UIs and reliable uptimes. The most common things in 2026 homelab setups:

Each of these replaces a commercial service that costs somewhere between five and fifty dollars a month. Run all of them on a single homelab server and you're saving a few hundred dollars a year while gaining complete control over your data.

The downsides are real but manageable

Self-hosting isn't free. The cost is your time. You become responsible for backups, updates, security patches, hardware maintenance, and troubleshooting when things break. If your home internet goes down, your services go down. If your hard drive dies, you'd better have a backup.

But these downsides are smaller than they used to be. Modern self-hosted applications mostly handle their own updates. Docker images get pushed automatically. Backup tools like Restic make encrypted offsite backups straightforward. UPS units handle brief power outages. The total time investment for a well-set-up homelab is probably one or two hours a month after the initial setup.

For a lot of developers, that's a price worth paying. Two hours a month to control your own infrastructure, save real money, and stop worrying about which cloud service is going to die next. The math is starting to make sense to a lot of people.

Where this is heading

I don't think self-hosting will ever fully replace cloud computing. There are workloads where the cloud genuinely is cheaper and easier: anything that needs to scale rapidly, anything that requires global distribution, anything that's mission critical for a business. The cloud isn't going anywhere.

But I do think the pendulum is swinging back from "everything in the cloud" to a more balanced approach where personal and small-business workloads live on owned hardware, and only the things that genuinely benefit from cloud infrastructure stay there. The default for the last decade was "move it to the cloud unless you have a reason not to." The new default for the next decade might be "host it yourself unless you have a reason to use the cloud."

If you've never set up a homelab, try it with a single service. Pick one cloud subscription you'd like to stop paying for. Find the self-hosted alternative. Run it on a Raspberry Pi or an old laptop. See if you can live with it for a month. You might be surprised how good it feels to own your own infrastructure again.

Track GitHub trending repos, dev/ops status, and more on the TerminalFeed dashboard.

Open TerminalFeed Dashboard