Discuss what outsourcing means for your platform with a SUE engineer .
Managed Services at SUE · Managed Linux · Managed Kubernetes
Outsourcing IT management is especially worthwhile if you need 24/7 availability, lack specialized knowledge, or want to free up your own team to focus on improvement. First, choose a management model (full-service, co-managed, or per platform); calculate the true cost of doing it yourself; set out the terms in an SLA with measurable response times; and agree in advance on how you’ll maintain control and how you can transition back to in-house management.
Outsourcing pays off if you need 24/7 availability, lack specialized knowledge, or want to free up your team. → Section 2
First, choose a management model: fully managed, co-managed, or per platform. → Section 3
Calculate the cost of doing it yourself. For 24/7 coverage in a single area of expertise, you'll need five to six people. → Section 4
Document it and plan your exit. Measurable response times, ownership of the configuration, and an exit plan. → Section 6
With “ Managed Services ,” an external provider takes over the management of (part of) your IT at a fixed price and with fixed quality agreements. This includes monitoring, patching, backups, security, and troubleshooting. The difference from hiring temporary staff: the provider is responsible for the results and therefore delivers more than just hours of work.
Outsourcing is less cost-effective if your management is closely intertwined with specific business processes that require a great deal of internal knowledge, or if your team is large enough and that knowledge is widely distributed.
There are 168 hours in a week. A full-time employee works about 36 to 40 of those hours, excluding vacation, sick leave, and training. To have one person available for every hour of the week, you therefore need more than four FTEs. In practice, you plan for five to six people per area of expertise, so that no one is on call every week and expertise isn’t concentrated in a single person.
Add to that: on-call and shift differential pay, training and certification, monitoring and logging tools, and the time it takes to recruit. Compare that amount to the monthly fee charged by a partner for the same level of service.
Please note: Availability depends on the entire platform, including applications, the network, and vendors. A partner can only guarantee what it manages. Agree on whether scheduled maintenance counts toward availability.
A management contract only works if both parties have the same understanding of the scope and response times. Therefore, establish in advance what will happen in the event of an incident, during periods of growth, and when switching to another provider.
The scope: which systems, which tasks, and what is explicitly excluded.
Response times and resolution times by priority, and the service window.
How availability is measured and reported.
What happens if the targets aren't met.
Who owns the configuration, code, documentation, and data?
Access: Who is allowed to do what, and how is that logged?
Security agreements: patch deadlines, incident reporting, data processing agreement.
Reporting and Consultation Structure.
Pricing model and how growth or decline is factored in.
Term, notice period, and an exit plan.
NIS2 is the European directive on cybersecurity. In the Netherlands, the Cybersecurity Act (Cbw)—which implements NIS2—has been in effect since August 15, 2026. Two points are important to consider when outsourcing:
This is not legal advice. Have your legal counsel or compliance officer review how this applies to your organization.
A proposal shows what a management partner promises. You won’t know how they actually work until the first incident occurs. That’s why you should assess this in advance, through discussions and by checking references.
Knowledge of your platform. Ask about experience and certifications related to the technology you use, such as Linux, Kubernetes, or a specific cloud platform.
Our own people. Who handles an incident at night: an engineer that’s familiar with your platform, or a first-line service desk?
References. Ask for clients of a similar size and with a similar platform, and give them a call.
Transparency. Do you have access to monitoring, tickets, and configuration?
Procedure. Is the configuration documented as code, so you don't have to rely on what's in someone's head?
Security and certification, such as ISO 27001.
Culture and scale. Are you a good fit, and are you an important client to your partner?
Common mistakes: not allowing enough time for the handover, documentation that doesn’t match reality, failing to make arrangements with the departing party, and forgetting which tasks were handled “automatically” by someone else.
Anyone who outsources management remains responsible for the decisions and the budget. This requires someone who can oversee the partner and keep the expertise about your platform in-house.
Designate an owner within your organization to oversee the contract and the relationship.
Hold regular meetings— for example, monthly meetings to discuss incidents, changes, and improvements, and quarterly meetings to discuss strategy.
Focus on measurable results: availability, number of incidents, turnaround times, and costs.
Keep in-house expertise on architecture and design choices, even if you fully outsource management.
Make sure the configuration and documentation belong to you and are stored in a repository that you have access to.
With staff secondment, you hire people whom you manage; you pay by the hour. With Managed Services , the partner is responsible for the results—as set forth in an SLA—at a fixed price. Staff secondment provides more direct control, Managed Services while offers greater continuity, since management does not depend on a single person.
A model in which your own team and a partner manage operations together, with a fixed division of responsibilities. Often, your own team handles the work during the day, while the partner takes care of nights, weekends, and specialized topics.
Typically one to three years, with a notice period of several months. A longer term may result in a lower price, but be sure to consider the option to adjust the scope and service level during the term.
That depends on the contract. Common remedies include service credits (a discount on the invoice) and a corrective action plan. If performance standards are repeatedly not met, there should be a right to terminate the contract. More important than the penalty is ensuring that the underlying cause is resolved permanently.
Because there may come a time when you want or need to switch partners. Make sure to establish in advance that the configuration, code, documentation, and data belong to you, how the handover will take place, and what support the partner will provide during the process. That way, you can leave without disrupting operations.
Discuss what outsourcing means for your platform with a SUE engineer .
Managed Services at SUE · Managed Linux · Managed Kubernetes
Discuss what outsourcing means for your platform with a SUE engineer .
Managed Services at SUE · Managed Linux · Managed Kubernetes
* required