
A corporate IT team at capacity
Password resets and device requests consume the people you hired for projects. We take first-line support through our IT service desk.

Co-managed IT is a model in which an outside provider runs defined parts of your IT operation, such as the service desk, security or servers, while your in-house IT team keeps the rest and sets the direction. Arke Technologies delivers it from Johannesburg under one service-level agreement that records who owns what.
Co-managed IT sits between running everything yourself and handing everything over. Your IT team stays in place and keeps its decision rights: architecture, budget, priorities and the relationship with the business. We take the parts you agree to hand us, run them to a written SLA and report on them monthly.
Because accountability is shared, it has to be written down. Every system and every type of ticket has one owner, your team or ours, and the escalation path between the two is agreed before the first ticket arrives. If you would rather we carried the whole operation, see IT outsourcing.
Co-managed IT is part of our managed IT services, delivered by the same team on the same tooling, for enterprise IT departments, public-sector IT units, and schools, universities and TVET colleges across South Africa.


Password resets and device requests consume the people you hired for projects. We take first-line support through our IT service desk.

Microsoft 365 hardening, Microsoft Sentinel SIEM, Entra ID governance, Linux server administration and POPIA compliance management are ongoing work for our team across client organisations in South Africa. See cybersecurity services.
A Microsoft 365 migration or a Windows Server upgrade goes better when someone else keeps the lights on. We take one; your team takes the other.

Departments, public entities and municipalities often run large estates with small teams. We add capacity within PFMA or MFMA procurement and reporting disciplines. More on public-sector IT.

Small IT teams, many accounts and devices, and a peak every term. We add support for Google Workspace for Education, Microsoft 365 Education and learner devices. More on IT for education.
Cover while a post is vacant or a colleague is away. Out-of-hours and weekend cover is available by agreement and set in your SLA.

The three models differ mainly in who does the daily work and who answers for it.
| In-house only | Co-managed IT | Fully managed IT | |
|---|---|---|---|
| Day-to-day support | Your team | Split by an agreed matrix | Arke |
| Strategy, budget and priorities | Your team | Your team, with our advice | Agreed with you; we run it |
| Specialist depth | Whatever you employ | Added where you need it | Provided |
| Cover for leave and peaks | Limited by headcount | Shared | Provided |
| Documentation | Yours | Shared, and owned by you | Written by us, owned by you |
| Cost basis | Salaries, tools and training | Per user per month for the scope we carry | Per user per month for the whole estate |
| Best fit | Large teams with every skill in-house | Capable teams that need capacity or depth | Organisations without an IT team, or choosing not to run one |
For the wider trade-off, read managed IT vs in-house IT.
01.
Our service desk handles calls, requests and routine fixes, and escalates to your team for your applications and infrastructure.
02.
Your team stays the face of IT, and we handle servers, networks, security and cloud behind it.
03.
Security, Microsoft 365 or Google Workspace administration, backup and disaster recovery, or device management.
04.
A migration or upgrade programme, delivered alongside your team's daily work.
Each model ends in a responsibility matrix recording who is responsible, accountable, consulted and informed for every system and ticket type. Both teams sign it, and it is revised whenever the scope changes.
01.
We meet your IT team and document the estate, your tools, ticket volumes and where the pressure is.
02.
Security baselines, configuration standards, monitoring thresholds and documentation requirements, so both teams work to one standard.
03.
Ownership, escalation in both directions, and the change process.
04.
Scope, response and resolution targets, exclusions, on-site policy, price per seat and term. Incidents are prioritised from P1 (a critical outage) to P4 (a low-impact request), with targets matched to the business impact of downtime and agreed with you.
05.
Monitoring installed, access granted per named person, runbooks written, tickets taken over on an agreed date.
06.
With your IT lead, against the SLA.
Our monitoring and remote-access tooling is our own. Monitoring checks each computer every 15 minutes and logs faults as tickets; remote support runs on our own platform, built on open-source RustDesk and hosted on our Johannesburg servers; riskier automated repairs need a recorded human approval. How tickets pass between our team and yours is set at onboarding, so that no ticket has two owners or none.
Two teams with administrator rights is a security question before it is a support one.
R180–R400
published managed IT rates per user per month (matnet.co.za, September 2026)
R21,054
average monthly pay for one Johannesburg IT support technician (Indeed, September 2026)
Co-managed IT is priced on the same basis as our fully managed service: per user (seat) per month for the scope we carry, set after an assessment and billed monthly in advance by debit order. Work outside the SLA is quoted per project, and managed IT pricing explains how we build a quote. The price depends on:
which layers we carry: first line, second and third line, one discipline or a project;
the users, devices and servers in scope;
the hours of cover;
specialist work such as security monitoring or cloud administration;
reporting and audit-evidence needs.
Last reviewed: September 2026.
The risks in co-managed IT sit at the seams between the two teams, so that is where we put the controls.
| Risk | How we control it |
|---|---|
| Blurred accountability: each team assumes the other has it | A signed responsibility matrix; every system and ticket type has one owner |
| Duplicate or clashing tools | Tools agreed at onboarding, with one route for tickets between the teams |
| Access sprawl | Named accounts, role-based rights, logged sessions and a monthly access review |
| Knowledge held by one team | Shared runbooks and documentation, owned by you |
| Changes that collide | One change-control process for both teams |
| An arrangement that no longer fits | Scope reviewed at the monthly service review and adjusted by agreement |
Co-managed IT should make your team stronger, not dependent. Your data, credentials and documentation stay yours throughout, and the runbooks we write are handed over as we go, not at the end.
If your needs grow, the agreement can widen into fully managed IT; if you build the capability in-house, we hand the work back with the documentation to run it. For strategy and budgeting support alongside your IT lead, see IT consulting and virtual CIO.

Co-managed IT support is a shared model in which an external provider runs agreed parts of IT support, such as the service desk or server management, alongside your in-house IT team. At Arke, a signed responsibility matrix and one SLA set who owns each system and ticket type, and a monthly review reports on both.
"Co-managed" means managed jointly. In IT, your own staff and a managed service provider share the running of your systems, each owning defined tasks. It sits between outsourcing, where the provider runs everything, and in-house IT. You will also see it written "comanaged"; the meaning is the same.
No. Co-managed IT adds capacity and specialist depth to your IT team; it does not replace it. Your team keeps strategy, budget and priorities, and we take the work you agree to hand over. If you later outsource fully or bring everything back in-house, the documentation is yours.
We split responsibilities in a responsibility matrix agreed during onboarding, naming the owner of every system and ticket type, the escalation path in both directions and the change process. Common splits: we run first line and you run the rest, or you keep the service desk and we take servers, networks, security and cloud.
Co-managed IT is priced per user per month for the scope we carry, set after an assessment and billed monthly in advance by debit order; project work is quoted separately. For context, published South African rates for fully managed IT run from about R180 to R400 per user per month (matnet.co.za, September 2026).
Yes. Schools, TVET colleges, universities and municipalities often have capable but small IT teams covering large estates. Co-managed IT adds support at peaks, such as the start of a school term or the financial year-end, and depth in security and cloud, with documentation that supports POPIA and PFMA or MFMA reporting.
Tell us where your team is stretched, and we will propose a split, an SLA and a monthly fee in writing.