100 customers. One tool. No more tool sprawl.
octoja is built as an RMM for service providers — not as a tool for a single in-house IT department with a tenant mode bolted on. Tenants, permissions, alerts and reports are multi-tenant from the ground up.
- A new customer device is monitored, equipped and documented within minutes
- Alerts land in your ticketing system — and close there again
- Customer reports go out automatically, in your branding
checks ready out of the box
connected ticketing and PSA systems
device types, including agentless
dedicated instance instead of a shared database
Sound familiar?
Five of these are normal in the service provider business. None of them has to stay that way.
Every onboarding starts from scratch, because every customer is set up differently.
A faulty Windows update takes out half your customer base in a single morning.
The monthly report costs every engineer half a day of manual work.
Engineers can see customer data that is none of their business.
The on-call phone rings 40 times overnight about the same problem.
Monday, 07:40. One dashboard instead of ten browser tabs: 340 devices across 28 customers. Three open alerts — a Veeam job failed twice in a row, a UPS on battery, a certificate expiring in nine days.
The Veeam failure raised itself as a ticket in your PSA long ago, complete with device, customer and check history. The UPS alert went out by phone call to the on-call engineer overnight because it occurred outside service hours — exactly once, not 40 times.
By 08:15 the new workstation at customer C is ready. The agent was installed via token, and the configuration package assigned monitoring, baseline software and security settings automatically. Nobody worked through a checklist to make it happen.
What makes the difference day to day
The longest feature list does not win — what saves hours every week does.
Onboarding as a rule, not a checklist
Configuration packages distribute checks, software and automations automatically — by operating system, role, site or tag. 15 templates are included as a starting point.
Patches in rings, not all at once
Test group first, then the wider estate — promotion only once a defined success rate is met. Known problem updates are excluded automatically.
Permissions that end where the task ends
First the tenant, then the device, then the action. The access overview answers the question at any time: who can see this device — and why?
Time tracking where the work happens
The timer runs inside the remote support window and is tied to the case. What gets invoiced is no longer reconstructed from memory.
Including the things that have no agent
Switches, firewalls, printers, UPS units, NAS and ESXi — monitored via SNMP v3 from a neighbouring device.
Your name on the product
Product name, colours, logo, sign-in page and your own domain — right through to the agent on the endpoint and the customer PDF.
And that is not all
- Your own Chocolatey feed for your packages
- Software kiosk for end-customer self-service
- 30 ready-made automation templates
- MCP server for AI assistants with graduated permissions
- 476 documented API routes
- Wallboard for the service desk
Six points that regularly tip the balance in a sales conversation — and are better seen than read about.
Get trial accessThe alert lands where your team already works.
An alert is only worth something once it reaches the right person at the right time — and closes itself again when the problem has gone.
Ticketing systems & PSA
Alerts raise a ticket where your team already works — and close it again on all-clear. Customer records can be imported.
- DocBee
- TANSS
- TOPdesk
- c-entron Service-Board
- HaloPSA
- Autotask
- Jira Service Management
- Freshservice
- Inserve
- Odoo Helpdesk
- Codemeta
Alerting
Separate service hours per channel. Into the ticketing system during the day, by phone call to the on-call engineer at night — alerts outside those hours are held back, not discarded.
- Microsoft Teams
- Signierte Webhooks
- SMS
- Sprachanruf
- App-Push
- Internes Ticket
Documentation & ITAM
The device estate is mirrored into your existing documentation rather than creating a second register.
- Hudu
- IT Glue
- woasi
- Jira Assets
Antivirus, EDR & vulnerabilities
Protection status and vulnerabilities come together in the same view as the rest of the estate — regardless of whose security software the customer runs.
- Microsoft Defender
- Bitdefender GravityZone
- SentinelOne
- CrowdStrike Falcon
- Sophos
- ESET
- G DATA
- Securepoint Antivirus Pro
- ThreatDown (Malwarebytes)
- Lywand Schwachstellenaudit
Backup — monitored across vendors
Firewalls & appliances
Hardware, storage and network without an agent
Server workloads
Would something else suit you better?
See your own estate in it
We set up an instance, you roll the agent out to a few real customer devices — and judge it against your working day rather than a demo.