Do you already have a root, cloud, or dedicated server and want to have the Linux server managed? WZ-IT takes over maintenance, monitoring, and the agreed operations at the existing provider. The Linux server maintenance entry describes the same service from the perspective of ongoing maintenance tasks.
Managed and unmanaged look like two clear categories in product listings. In practice, however, they describe very different boundaries. A provider may use managed server for a fixed web-hosting product without root access. An operations partner may use it for a freely configurable server in the customer's account. Both offers are called managed, but they are not technically or contractually identical.
A useful comparison therefore starts with responsibility for each system layer, not with the product name or monthly price.
Contents
- What is an unmanaged Linux server?
- What can managed server mean?
- Responsibility matrix
- Three operating models compared
- Questions to answer before deciding
- Adding management to an existing Linux server
What is an unmanaged Linux server?
With an unmanaged product, the provider generally supplies the technical infrastructure: a virtual or dedicated server, network access, a control panel and a reinstall or console mechanism. Responsibility from the operating system upwards typically sits with the customer.
That includes:
- operating system installation and configuration
- security updates and release upgrades
- users, SSH, firewall and hardening
- web servers, databases, containers and applications
- monitoring and response to alerts
- backup, retention and recovery
- troubleshooting and incident handling
- operations documentation
The exact boundary always comes from the contract. For example, Hetzner explicitly states for dedicated and cloud products that customers are responsible for administration, maintenance and security of their systems. Other providers may allocate individual infrastructure services differently.
An unmanaged server is therefore not an incomplete product. It is infrastructure that assumes an operations team on the customer side.
What can managed server mean?
At least three variants are common:
1. Standardised managed hosting
The infrastructure provider and operator are the same party. The customer receives a predefined platform, often without full root access. The provider handles updates and baseline operations while software selection and configuration are more constrained.
This suits standardised websites or applications when the offered versions, components and operating limits are sufficient.
2. External management of a customer-owned server
The server stays in the customer's account and contract. An operations provider receives documented administrative access and assumes the agreed scope. Root control, provider selection and technical architecture generally remain with the customer.
This model suits custom applications, existing root servers, Docker environments, databases or organically grown systems that do not fit into a fixed hosting product.
3. Co-managed operations
The internal team and an external provider share responsibility. For example, the customer team develops the application while WZ-IT manages the operating system, monitoring, backups and incident process. Alternatively, routine maintenance remains internal while a second team provides monitoring and escalation.
A co-managed model requires a written handover matrix. Otherwise, a gap appears precisely at the boundary between application and infrastructure.
Responsibility matrix
The following table shows typical, not universal boundaries. The actual contract may differ.
| Task | Unmanaged infrastructure | Standardised managed hosting | External Linux server management |
|---|---|---|---|
| Physical hardware and base network | Provider | Provider | Provider or customer |
| Provider account and contract | Customer | often part of provider product | Customer |
| Operating system installation | Customer | Provider | WZ-IT by scope |
| OS and package updates | Customer | Provider within standard scope | WZ-IT by scope |
| Root access | fully with customer | often restricted | remains with customer, operating access documented |
| Custom software | unrestricted, customer responsible | limited by platform | unrestricted, operability assessed |
| Monitoring | Customer | platform-specific | WZ-IT by scope |
| Response to alerts | Customer | depends on product | WZ-IT by service level |
| Backup and restore | Customer | depends on product | according to agreed recovery scope |
| Documentation and exit | Customer | depends on provider | part of agreed operations |
Two offers are only comparable when these rows are allocated similarly. Monitoring included may, for example, mean only that an email is sent. A defined technical response is an additional service.
Three operating models compared
Unmanaged with an internal team
Suitable when: Linux expertise, substitution, monitoring and documented processes are continuously available internally.
Advantages: full technical freedom, direct control and no additional operator contract.
Review: on-call coverage, vacation and illness, concentration of knowledge, patch cadence, backup ownership and actual personnel cost.
Managed product from the infrastructure provider
Suitable when: the application fits the provider's standard and technical freedom matters less than a simplified platform.
Advantages: few interfaces, standardised provisioning and clear limits within the product.
Review: root access, supported components, response scope, backup and restore, migration paths and exit.
Customer-owned server with external operations
Suitable when: provider, root access and the custom stack should remain while ongoing Linux operations are outsourced.
Advantages: hosting and operations can be selected separately. Changing provider is not a precondition for operational takeover.
Review: audit before takeover, access model, service schedule, service level, application boundaries, recovery scope and orderly handover.
Questions to answer before deciding
Before comparing offers, answer these questions in writing:
- Who assesses and installs security updates?
- Who decides on maintenance windows and reboots?
- Who monitors the operating system, services, certificates and backup jobs?
- Who responds to an alert and within which time window?
- Who performs a practical recovery test?
- Who manages the database, container platform and application?
- Who may create and revoke root access?
- Who owns the provider account, configuration and documentation?
- How is absence covered?
- How are systems handed over at the end of the contract?
If a task has no clear person or role, it has not actually been assigned.
Adding management to an existing Linux server
In many cases, an existing unmanaged server can be transferred into managed operations later. This does not automatically require a provider change. A controlled process consists of:
- Inventory: record systems, services, versions, dependencies and open risks.
- Access handover: establish personal SSH keys, technical accounts and emergency access.
- Stabilisation: address critical patch, backup or security gaps before accepting responsibility.
- Monitoring: connect the host, services, certificates and backup jobs to useful alert paths.
- Service schedule: document maintenance, response, recovery and application boundaries.
- Regular operations: maintain traceable records of changes, incidents and backup status.
The Linux server takeover checklist covers the required information and checks in detail. What does server management cost? explains the pricing factors.
WZ-IT manages existing Linux servers from €149.90 net per month at the standard entry point. The final scope depends on condition, stack, number of servers and required service level. Monitoring-only without operational takeover starts separately from €49.90 net per server and month.
