Co-managed sits between full peace of mind (Fully Managed) and doing everything in-house. With Fully Managed Services, we take it all off your plate. With Co-managed, we align on what your team keeps doing and where you want us to step in. You keep control and knowledge in-house. We add expertise, capacity, and support. No standard package. No vendor lock-in. No “us vs. them.” Just your engineers and our engineers, working together.
Ideal if you:
| Have an internal IT or OT team and want to stay in control. |
| Run specialized systems (like OT/SCADA or custom-built environments). |
| Need extra expertise in networking and security. |
| Want to spend less time on incidents and daily management. |
| Have multiple locations with different levels of IT capacity. |
Most MSPs make you choose: hand everything over, or keep doing everything yourself. In real life, that rarely works.
| Outsourcing everything costs you control, speed, and internal knowledge. Suddenly, nobody can “just fix it” quickly. |
| Keeping everything in-house often means your team is buried in management work, tickets, and incidents. Meanwhile, the projects that actually move the business forward keep getting pushed aside. |
Co-managed is a tailored split of tasks and responsibilities between your team and ours. Together, we decide who does what, per system, per location, and based on what you need.
You keep, for example:
| Business-critical or unique systems and knowledge. |
| Governance, policies, and compliance ownership. |
| Day-to-day tasks you prefer to keep in-house. |
| Network infrastructure and connectivity (for example SD-WAN). |
| Security layers (firewall, ZTNA, segmentation). |
| Monitoring, troubleshooting, and escalation. |
| Major changes and the heavy lifting. |
| 24/7 support, where needed. |
Co-managed only works when it’s designed properly. That’s why we make it very concrete:
| Clear task division Who does what, per system, location, or component. No gray areas. |
| Clear escalation paths What stays with your team, when we step in, and how fast. |
| Shared monitoring, clear ownership The right alerts go to the right people, with agreed actions. |
| Full transparency Documentation, configurations, and access stay clear and transferable. No hidden dependencies. |
| Engineer-to-engineer collaboration No ticket wall when it really matters. Short lines, fast action. |
| Control and speed, without doing everything yourself. |
| Specialized knowledge stays in-house, where it belongs. |
| Less firefighting, faster resolution, and fewer handoffs. |
| No duplicate work. Everyone focuses on what they do best. |
| Scalable support, without immediately hiring extra FTE. |
| Costs that make sense. You don’t pay for expertise you already have. |
Co-managed is not a package. To give you a clear picture, here are a few ways we often set it up in practice. Don’t see your situation here? No problem. We design the split together, based on your organization.
| 1 |
By component
Your team keeps (W)LAN and endpoints in-house, while we manage cloud infrastructure and the firewall and security layer. Everyone plays to their strengths, without overlap. |
| 2 |
By location
Not every site needs the same level of support. Headquarters can stay self-sufficient, with our backup, while a warehouse or smaller branch gets full support. That way, support matches local IT capacity. |
| 3 |
By role or support level
Your team handles daily operations and regular changes. We act as expert backup for escalations, complex changes, and the moments you need extra capacity. For example migrations, weekends, or 24/7 follow-up. |
| 4 |
By critical system
Specialized domains and custom environments stay with your team, because that’s where the knowledge is. Think OT/SCADA in production. Your OT team keeps ownership, while we manage the network and security infrastructure around it. For example segmentation, secure remote access, monitoring, and when needed the OT/IT security layer. |
How do we approach this? We start with a quick introduction. Then we define the task split and agreements together. After that, we set everything up so we can start smoothly and keep improving.
Co-managed takes more than good intentions. It takes craftsmanship, structure, and transparency. That’s exactly what we’re good at:
| Transparency by default Full documentation, visibility into configurations, and clear agreements. No vendor lock-in. |
| Short lines, fast action Direct contact and clear escalation, so issues don’t linger. |
| Security-first approach Access and changes aligned with policy: MFA, least privilege, and logging. |
| Proactive and predictable Not just fixing, improving. Reviews, reporting, and optimization. |
| A collaboration that keeps up If your team or environment changes, we align on what’s needed, within the agreements. |
Is co-managed a standard service package?
No. We agree together on what your team does and what we do. The task split is clearly documented and can differ by site, by system, or by layer (LAN vs. security/SD-WAN).
|
Do we keep full access to documentation and configurations? |
What if our team mainly wants backup, not full takeover? |
How does escalation work during incidents? And what are the response times? |
Does this work with compliance requirements? |
What’s the difference between Fully Managed, Co-managed, and Reactive Managed? |
What happens if our internal team changes (absence, growth, new colleagues)? |
Which environments do you support (cloud/on-prem/hybrid, OT/IT)? |
