Remote access with approvals and session logs
Built on open-source RustDesk, with a management layer we own. Devices sit in groups, sessions need approval, and every session is logged. Read more about Hesper remote access.
Hesper: managed service provider software for MSPs and IT teams
Hesper is managed service provider software from Arke Technologies in Johannesburg: one IT operations management platform for approved remote access, monitoring every 15 minutes, standard automated repairs and SLA-tied ticketing. Built first for our own managed service, it serves MSPs and in-house IT teams and launches in November 2026.
What Hesper is
Hesper is the IT operations platform from Arke Technologies (Pty) Ltd, the Johannesburg technology company serving organisations across South Africa. It is managed service provider software, but it is not only for managed service providers (MSPs). In-house IT teams at companies, public bodies, schools and universities do the same daily work of watching devices, fixing faults and recording what was done.
IT operations management is that daily work, run as a discipline: knowing the state of every computer and server, raising a record when something breaks, fixing it within an agreed time, and being able to show afterwards who touched which system and why. Hesper brings four jobs at the core of it (monitoring, remote access, standard repairs and SLA-tied ticketing) into one managed services platform, so the record of a fault, the fix and the person who approved it sit in one place.
Hesper is in development, with early access until its launch in November 2026. We own it outright, as we own AtlasOS, our operating system for professional services firms (visit the AtlasOS site (opens atlaspractice.app)). Both sit on our platforms page.
Four capabilities in one managed services platform
Monitoring every 15 minutes
Each computer is checked every 15 minutes, and a fault is raised as a ticket automatically, so the first sign of trouble does not depend on a user noticing it and picking up the phone. Read more about Hesper monitoring, automation and ticketing.
Standard automated repairs
A library of standard repairs fixes common faults the same way every time. The riskier repairs run only after a person has approved them, and that approval is recorded.
Ticketing tied to SLA clocks
Every ticket carries the clock of the service-level agreement it falls under, so each piece of work is measured against the target agreed for it.
Who Hesper is for
Managed service providers
MSP management software has to serve a portfolio of clients, each with its own agreement. Device groups let a provider organise each client's devices separately, and each ticket runs on the clock of the SLA it belongs to.
In-house IT teams in mid-sized and large organisations
An internal team still owes the business an agreed service. Hesper gives it the same monitoring, approvals and records that an outside provider would be held to.
Public-sector IT units
Departments, municipalities and state-owned entities answer to auditors and to PFMA or MFMA reporting disciplines. Approved, logged remote sessions and recorded repair approvals give those reviews a trail to test.
Schools, universities and TVET colleges
A small IT team looking after many learner, lecturer and staff devices needs faults to raise themselves and routine fixes to run without a site visit.
Governance, security and POPIA
A remote-access tool can reach every device an organisation owns, so auditors ask about its controls before its features. Hesper follows the governance we apply to all our work:
- No silent access. Remote sessions need approval and are logged, so an organisation can show who connected to which device, and when.
- People decide the risky changes. Riskier automated repairs cannot run until a person approves them, and the approval is kept on record.
- Evidence for the board. King IV Principle 12 asks governing bodies to govern technology and information. Session logs, approvals and ticket histories are the evidence that oversight rests on.
- POPIA. Devices hold personal information. Controlled, logged access supports the security safeguards POPIA requires. In our own managed service, the remote-access platform runs on our own servers in Johannesburg.
- Open foundations. The remote-access layer is built on open-source RustDesk, so its core code is open to inspection. The management layer around it is ours.
- Recognised frameworks. Approval before access and a log of every session are the access-control and audit-logging disciplines that the CIS Controls and ISO/IEC 27001, frameworks we work to, ask organisations to demonstrate.
Why we built Hesper
We run our own managed IT service on our own tooling, and our remote-access platform runs on our own servers in Johannesburg. Hesper is that tooling: built first for our own service, and now in development so that other MSPs and IT teams can run on it too.
Owning the platform means we decide where data sits, how approvals work and what gets logged, instead of inheriting those choices from someone else's product. Its first users are our own technicians, working to client SLAs, so it is shaped by real tickets rather than a wish list. Our managed IT services and IT service desk run on this approach, and the service desk works to ITIL-aligned incident, request, problem and change practice; our guide to ITIL and IT service management explains those terms.
