Self-hosting in 2026
A few years ago, self-hosting was a Linux-nerd hobby. In 2026 it's a $5/mo VPS, Coolify, an install flow, and a serious IndieWeb movement that's finally addressing creators with a domain, not just engineers.
A few years ago, running your own server was a hobby. You needed the right hardware, the right Linux distro, and a tolerance for compiling things from source and writing init scripts. The kind of people who self-hosted were the kind of people who liked the configuring as much as the result.
That's changed. The 2026 self-hosting toolchain is genuinely accessible: a $4–6/month VPS from Hetzner or DigitalOcean, Coolify or Portainer for the orchestration layer, Cloudflare Tunnels for getting traffic in without exposing your network. Setting up a Ghost blog, an Umami analytics instance, or a Mastodon node is closer to "deployed a static site to Netlify" than to "spent the weekend configuring nginx." The tools moved.
The IndieWeb movement noticed. The recent reframings of what the IndieWeb is for in 2026 are pointed at people who weren't being addressed before: not engineers, but creators with a domain and an opinion about owning their work. Own your domain, publish on your own site first, own your content. Each of those used to imply running a server; now it implies clicking through an install flow.
This is the cultural moment Beacon was waiting for. When we started, the argument for a self-hosted link-in-bio sounded like a hobby pitch — yes, but only the Linux nerds will do this. The pitch in 2026 is a different one: you already own a domain, you've already deployed a static site somewhere, you already know enough to point DNS records, and the rest is in your wheelhouse. The bar moved into reach.
You don't have to self-host everything, and most creators shouldn't try. The right framing is to ask which dependencies you can survive without, and put those on hosted services that take your time and your money for the convenience. The dependencies you can't survive losing (the canonical version of your presence on the web, the email list that took years to build, the archive of work you'd hate to rebuild) are the ones worth taking onto infrastructure you control.
Beacon is the maximum-ownership end of one of those dependencies: a self-hosted link-in-bio that costs $39, once, and runs from your own domain. That bet only works because self-hosting got easy. The toolchain caught up in 2026, and the cost is now worth paying for the part of your presence you can't afford to lose.