Managed self-hosting vs doing it yourself: the honest math

"Self-hosting is free" is the most expensive sentence in this hobby. The software is free. The server is cheap. The time — that's where the bill actually lands, and it's a recurring charge you pay in evenings and weekends for as long as the app is running.

We run a managed self-hosting platform, so we have an obvious bias here. We're going to try to earn your trust by being straight about it anyway, including the cases where you should absolutely do it yourself and not pay us a cent.

What "doing it yourself" actually costs

The upfront part is easy and genuinely fun: spin up a VPS, run a container, point a domain at it. An afternoon, tops. The bill comes later, and it's not money — it's the standing list of things that are now your job:

• Updates. Every app you run ships new versions, some with security fixes you can't skip. That's a pull, a restart, and occasionally a broken container to debug — forever, per app.
• TLS. Certificates that issue, renew, and don't silently expire at 2am.
• Backups. Not "I set up backups" — "I restored from a backup last month and it worked." The untested kind isn't a backup.
• Security. A firewall that's actually closed, an SSH port that isn't getting brute-forced, an admin panel that isn't open to the internet.
• The 2am problem. When the disk fills or the host reboots, you are the on-call engineer, because there is no one else.

None of this is hard in isolation. The cost is that it never stops, it scales with every app you add, and the failure modes are quiet — you find out backups were broken when you need one.

When you should absolutely DIY

We mean this. Run it yourself when:

• The plumbing is the point. If Linux, Docker and networking are things you want to get better at, self-hosting is one of the best teachers there is. Paying someone to do it would be paying to skip the fun.
• You have the time and it's steady. A homelab you tend on weekends is a great use of a Sunday.
• You need total control — custom kernels, weird hardware, air-gapped networks, licensing you have to own outright.

If that's you, close this tab and go build something. Genuinely.

When managed is the honest call

The other side is just as real. Managed hosting earns its keep when:

• You want the outcome, not the hobby. You want your photos off Google, your passwords off a subscription, your team on a self-hosted chat — and you do not want to become a part-time sysadmin to get there.
• The app matters. A password manager or your company's files are not where you want to discover your backup script had a typo.
• Your time is worth more than the difference. If maintaining ten apps costs you an evening a month, and managed hosting costs less than an evening of your time, the math isn't close.

The part that's the same either way

Here's what doesn't change: it's still self-hosting. Managed doesn't mean a reseller's dashboard bolted onto someone else's SaaS. The apps are the real, open-source apps — the same catalog you'd install yourself. Your data is yours. You can export it and leave. The only thing you're outsourcing is the plumbing: the server, the updates, the TLS, the backups, the firewall, the 2am pager.

That's the whole pitch, and it's the whole honest math. DIY if the work is the reward. Go managed if the app is. Either way, own your data — that part was never negotiable.

See what one-click deploys look like → — real apps, your data, none of the plumbing. Or read exactly where and how we run them.