When you choose hosting, the question comes up fast: run the server yourself, or let the provider do it for you? That’s the difference between self-hosted and managed hosting. Here’s what they mean and how to choose.
What does managed vs self-hosted mean?
- Self-hosted: you get a server and are responsible for everything on top — installation, updates, security, backups and troubleshooting.
- Managed hosting: you get the same performance, but the provider handles ops, updates, security, backups and support for you.
What you’re responsible for (self-hosted)
- Keeping the OS and software updated — on time, not when you get around to it.
- Security: firewall, hardening, monitoring and closing holes.
- Backups you can actually restore — and testing the restore.
- Troubleshooting when something breaks, often in the middle of the night.
The cost: time vs money
Self-hosted looks cheaper on paper, but you pay with your time — and risk. Managed hosting costs more per month but removes the hours of ops, security work and stress. For most businesses that difference is smaller than a single major incident costs.
When does self-hosted fit?
If you have a technical team, want full control and enjoy tinkering — self-hosted can be right. You get maximum freedom, but you also carry all the responsibility.
When does managed hosting fit?
If you’d rather spend time on your business than the server — managed is right. Especially for WordPress: updates, security and backups are critical and easy to miss. With Managed WordPress at Kepler we handle it for you, on Swedish hardware. If you still want your own server to build on, there’s Compute.
In short
Self-hosted gives control but all the responsibility; managed gives you the performance without the upkeep. The choice is about where you want to spend your time — on the server, or on what you’re actually building.