Managed vs. Self-Managed VPS
This choice is less about features and more about responsibility.
Who should be on the hook for the operating system and the core server stack when something needs attention?
Updated: January 2026
The short version
With Arcustech, you always own your application and content. The difference is who maintains the server environment underneath it.
Plain language: Managed VPS means we maintain the OS and core web stack. Self-Managed VPS means you (or your developer) do. Either way, you control your site, your code, your content, and how you deploy.
See also: Self-Managed VPS, PHP Managed VPS, Craft CMS Managed VPS, Node.js Managed VPS.
Who manages what?
If you are unsure which bucket you are in, this table is usually enough to make the answer obvious.
| Area | Self-Managed VPS | Managed VPS |
|---|---|---|
| Operating system updates | You / your developer | Arcustech |
| Web stack setup and tuning | You / your developer | Arcustech |
| Security patching and hardening (OS and stack) | You / your developer | Arcustech |
| Application code and content | You / your developer | You / your developer |
| Deployment workflow (Git, CI/CD, SFTP) | You choose | You choose |
Common misconceptions
“Managed VPS means you manage my website.”
Managed VPS means we manage the server environment. Your CMS updates, plugins, content,
and application behavior remain under your control (or your developer’s).
“Self-Managed VPS is only for hardcore sysadmins.”
Many Self-Managed customers use modern deployment tools like Ploi or Forge.
You still own the server decisions, but you are not starting from scratch.
“Switching later is automatic.”
Moving between Self-Managed and Managed VPS is not a simple toggle or in-place conversion.
If you decide to switch in either direction, the process involves provisioning a new server
under the desired service type and migrating your data from the old server to the new one.
Because Managed VPS uses a curated and standardized environment while Self-Managed allows
full customization, the two service types are treated as separate deployments. Migration
is handled by the client or their developer.
Self-Managed VPS at Arcustech
Self-Managed VPS is for teams that want root-level control of the server environment and prefer to own system-level decisions. That includes OS updates, security hardening, and web stack choices.
We keep the baseline predictable: Ubuntu LTS only. Most developers choosing Self-Managed are using a deployment tool, or they have an established Ubuntu workflow already.
Common tooling: Ploi, Laravel Forge, ServerPilot.
- Ideal if your developer wants full control over OS and stack decisions.
- Works well with modern deployment tooling, and also with hand-built Ubuntu stacks.
- Root access is provided by default.
If your project requires dozens of operating systems, custom ISO installs, or experimental stacks, Arcustech is intentionally not that kind of provider. We focus on a clean Ubuntu LTS baseline because it makes deployments and long-term maintenance more predictable.
Managed VPS at Arcustech
Managed VPS is for teams that want a maintained server environment without becoming full-time sysadmins. We handle OS installation, secure baseline configuration, critical updates, and ongoing stack maintenance.
The key idea is separation: we manage the server environment, while you (and your developer) manage the application.
- PHP Managed VPS for common PHP applications and frameworks.
- Craft CMS Managed VPS with additional Craft-specific preparation informed by real-world requirements.
- Node.js Managed VPS for modern JavaScript frameworks and long-running Node applications.
- SSH and SFTP access is provided at a Linux user level (not root).
Your deployment workflow is still your choice. Some teams deploy via Git and CI/CD, others use SFTP, and plenty do a mix. Managed VPS is about who maintains the server environment underneath that workflow.
Which option should you pick?
If you are a developer, this usually comes down to whether you want to own OS and stack responsibilities long-term. If you are a site owner, it usually comes down to how much server work you want your developer to carry (and how comfortable you are with that risk).
- Pick Self-Managed if you want root-level control and you have a plan for OS and stack maintenance.
- Pick Managed if you want Arcustech to maintain the server environment so your team can focus on the application.
- Pick Managed (Craft) if Craft CMS is central to the project and you want a server environment prepared around that workload.