What does managed hosting actually mean?
“Managed hosting” sounds straightforward, but it is one of the most overloaded terms in hosting.
Here is what it means at Arcustech, in plain language, without implying we “manage your website.”
Updated: January 2026
The short version
Managed hosting is not a promise that someone else will run your website day to day. It is a responsibility split.
Plain language: On a Managed VPS, Arcustech maintains the operating system and core server environment. You (and your developer) still own the application, content, and deployment workflow.
Related: Managed vs. Self-Managed VPS, PHP Managed VPS, Craft CMS Managed VPS, Self-Managed VPS.
Why this term confuses people
Two companies can both say “managed hosting” and mean completely different things. Sometimes it means “we keep the server updated.” Sometimes it means “we also handle the app.” And sometimes it is just a nicer way of saying “support is available.”
We prefer to define it by the parts that actually create work and risk: the OS, the core services, and the boundaries.
Who manages what at Arcustech?
If you only read one section, read this one.
| Area | Self-Managed VPS | Managed VPS |
|---|---|---|
| Operating system updates | You / your developer | Arcustech |
| Core server environment (web stack) | You / your developer | Arcustech |
| Security patching and hardening (OS and stack) | You / your developer | Arcustech |
| Infrastructure and VPS availability monitoring | Baseline platform monitoring only | Arcustech |
| Application code, CMS, plugins, content | You / your developer | You / your developer |
| Deployment workflow (Git, CI/CD, SFTP) | You choose | You choose |
What we mean by “monitoring” (and what we do not)
This is where most hosting descriptions accidentally over-promise, so we are careful with wording here.
When we say we monitor and respond, we mean the platform and infrastructure: the VPS host systems, network connectivity, and whether your VPS itself is running and reachable.
Important: We do not monitor application-level behavior like “your website returns a 500 error” or “a page is down.” A site can intentionally return a maintenance page, a 403, or a temporary error during deployments, upgrades, or app changes. Those signals are not reliably “hosting problems,” and treating them as such creates confusion fast.
In practice, this boundary keeps things clean: we keep the server environment stable and secure, and your team controls what the application does on top of it.
So what does “managed” include, day to day?
Managed hosting is mostly boring, and that is the point. It is the steady maintenance work that keeps the environment predictable over time.
- OS maintenance and security updates for the managed environment.
- Core service management for the curated stack (web and database services as provided by the plan).
- Platform-level guardrails that keep the environment consistent.
- Backups and recovery tooling at the VPS level, so you have a reliable restore path.
Root-level changes: what we handle for you
On Arcustech Managed VPS plans, customers get SSH and SFTP access at the Linux user level, but Arcustech retains root and sudo access. That is intentional. It keeps the environment consistent, and it means you still have a path to make system-level changes when they are actually needed.
If a task requires root access, you can request it from our Support and Technical teams. Common examples include:
- Adding a new domain name and mapping it to a document root in the web server.
- Tuning PHP or web server settings for a specific workload (upload limits, memory limits, timeouts, and similar).
- Installing supported Ubuntu packages that are not included by default.
We also do a quick sanity check on requests like these, because the internet is full of advice that ignores real constraints. For example, setting PHP memory limits higher than available RAM can make a server unstable, and large uploads can require enough memory to buffer safely during the upload process. We would rather help you choose settings that actually work than blindly apply values that look good in a blog post.
The goal is not to block you. It is to keep the environment reliable while still giving you a clear way to get root-level work done when your project needs it.
If you are looking for “someone to manage my CMS updates and plugins,” that is a different category of service. Arcustech Managed VPS is about the server environment underneath your application, not controlling the application itself.
A simple comparison callout
Managed VPS is for teams that want Arcustech to own OS and core server maintenance,
while the developer team owns code, deployments, and application changes.
Self-Managed VPS is for teams that want full root control and prefer to own OS and stack decisions long-term.
How to choose without overthinking it
The decision is less about features and more about responsibility and risk.
- Pick Managed VPS if you want a maintained server environment and do not want OS and stack work to become your ongoing problem.
- Pick Self-Managed VPS if you want root-level control and already have a plan for OS updates, hardening, and stack maintenance.
If you are unsure, tell us what you are building and how you deploy. The answer is usually obvious once responsibilities are spelled out.