Skip to main content
010 447 2445Contact
Arke Technologies home
Arke Technologies home
A row of support agents in headsets at a long desk beside tall office windows.

Co-managed IT: more capacity and depth for your IT team

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.

What co-managed IT means

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.

A team lead leans in to go through a printed report with an analyst at her desk in an open-plan office.

When co-managed IT makes sense

  • Projects on top of daily operations

    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.

  • Public-sector IT units

    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.

  • Leave, vacancies and out-of-hours

    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.

A service-desk analyst in a headset works through a ticket on a laptop while a colleague looks on.

Co-managed IT compared with fully managed and in-house IT

The three models differ mainly in who does the daily work and who answers for it.

In-house onlyCo-managed ITFully managed IT
Day-to-day supportYour teamSplit by an agreed matrixArke
Strategy, budget and prioritiesYour teamYour team, with our adviceAgreed with you; we run it
Specialist depthWhatever you employAdded where you need itProvided
Cover for leave and peaksLimited by headcountSharedProvided
DocumentationYoursShared, and owned by youWritten by us, owned by you
Cost basisSalaries, tools and trainingPer user per month for the scope we carryPer user per month for the whole estate
Best fitLarge teams with every skill in-houseCapable teams that need capacity or depthOrganisations without an IT team, or choosing not to run one

For the wider trade-off, read managed IT vs in-house IT.

Four common ways to split the work

  1. We run first line; you run the rest

    Our service desk handles calls, requests and routine fixes, and escalates to your team for your applications and infrastructure.

  2. You keep the service desk; we take second and third line

    Your team stays the face of IT, and we handle servers, networks, security and cloud behind it.

  3. We own one discipline end to end

    Security, Microsoft 365 or Google Workspace administration, backup and disaster recovery, or device management.

  4. We add project capacity

    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.

How we deliver co-managed IT services

  1. Discovery

    We meet your IT team and document the estate, your tools, ticket volumes and where the pressure is.

  2. Baseline

    Security baselines, configuration standards, monitoring thresholds and documentation requirements, so both teams work to one standard.

  3. Responsibility matrix

    Ownership, escalation in both directions, and the change process.

  4. SLA

    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.

  5. Onboarding

    Monitoring installed, access granted per named person, runbooks written, tickets taken over on an agreed date.

  6. Monthly service review

    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.

Governance and reporting

  • A named service lead who works with your IT lead.
  • A monthly service review and report: tickets by owner, SLA performance, security, patching, backups and open risks.
  • ITIL-aligned practice for incident, request, problem and change management. Background: ITIL and IT service management
  • One change-control process for both teams, so changes do not collide.
  • Escalation paths and runbooks, documented, kept current and owned by you.
  • Evidence for oversight. King IV Principle 12 makes the governing body responsible for technology and information governance; the monthly report gives boards, councils and school governing bodies something concrete to oversee.

Compliance and control of shared access

Two teams with administrator rights is a security question before it is a support one.

  • Named access only. Each person has their own account and only the rights their role needs, reviewed at the monthly service review.
  • Logged remote sessions. Every session is approved and logged, and everyone with access to your systems is bound by confidentiality and our security controls.
  • POPIA. Access controls and audit logging protect personal information; our Information Officer is designated under PAIA and POPIA.
  • Public-sector rules. Audit-ready documentation under the PFMA and the MFMA.
  • Recognised frameworks. Controls aligned with ISO/IEC 27001, the NIST Cybersecurity Framework and CIS Controls.

Procurement fit

  • Level 1 B-BBEE contributor (sworn affidavit available on request), which gives buyers 135% procurement recognition.
  • Arke Technologies (Pty) Ltd, registration number 2017/386810/07, VAT number 4750287957.
  • Company documents, a bank confirmation letter, our CSD supplier number and SARS tax compliance status are available on request.
  • Standard bidding documents (SBD forms) completed when a bid requires them.
  • Buy through a proposal and SLA, a purchase order, or a response to your tender. Supplier-onboarding details are on our company facts page.

What co-managed IT costs

  • 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.

Risks of co-managed IT, and how we control them

The risks in co-managed IT sit at the seams between the two teams, so that is where we put the controls.

RiskHow we control it
Blurred accountability: each team assumes the other has itA signed responsibility matrix; every system and ticket type has one owner
Duplicate or clashing toolsTools agreed at onboarding, with one route for tickets between the teams
Access sprawlNamed accounts, role-based rights, logged sessions and a monthly access review
Knowledge held by one teamShared runbooks and documentation, owned by you
Changes that collideOne change-control process for both teams
An arrangement that no longer fitsScope reviewed at the monthly service review and adjusted by agreement

Continuity: scale up, scale down or bring it back in-house

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.

Two service-desk colleagues in headsets follow a call at a window desk, one taking notes on a clipboard.

Frequently asked questions

What is co-managed IT support? Show answer

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.

What does "co-managed" mean? Show answer

"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.

Will co-managed IT replace our IT staff? Show answer

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.

How do you split responsibilities with our IT team? Show answer

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.

How is co-managed IT priced? Show answer

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).

Can schools and municipalities use co-managed IT? Show answer

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.

Strengthen your IT team without replacing it

Tell us where your team is stretched, and we will propose a split, an SLA and a monthly fee in writing.