Built inside a working MSP.
Octotor wasn't designed in a product workshop. It was built by the owner of a managed-services provider, for that provider's own daily work.
The origin
Every support case starts the same way, and it isn't with the fix.
A user calls. Or a workstation, a server, a switch needs attention. Before anyone touches the actual problem, the same preliminary steps run — every case, every time.
First, get the picture. Which means logging into one unrelated system after another. The machine itself for disk space, uptime, online state, IP address. Active Directory for the user and the computer object. The switch for port state and link speed. Microsoft 365 for the license and the mailbox size. Four systems, four consoles, four sets of credentials — none of which knows the others exist. All of it before the case has actually begun.
Then, act. Run something against the remote machine: ping an internal address from it, ping an external one, read the event log, restart it.
And behind both, the question a technical lead can't dodge: how do I let help-desk staff deliver fast, high-quality service — without handing every one of them full admin rights on every target in every customer's environment?
The tools we tried each solved a slice. An RMM here, a monitoring stack there, a spreadsheet of switch ports that nobody kept current. Each wanted our credentials in someone else's cloud, priced by formulas that punished doing the job thoroughly, and none of them answered the questions that actually cost the hours — which port is this machine on, whose license expired, what changed on that server last night.
So we built the answer to our own workflow.
What that answer looks like
- One place instead of five logins. Everything Octotor gathers is unified per asset — the machine, the directory object, the switch port, the cloud license — one or two clicks away in a single UI. See how Octotor turns this into one page →
- Actions without the keys. Permissions define exactly which actions a help-desk user or group may run. They execute scripts requiring domain-admin rights without ever seeing an admin credential. See how one script runs three ways →
- A live database, not a chase. Inventory used to live in spreadsheets and notebooks, permanently behind reality — because disk space, a Wi-Fi address, uptime and an M365 license all change while you're writing them down. Octotor keeps pace on its own. Click any asset: current state, history per attribute, every change. Trigger automatic actions on a change, or ask the built-in AI to look something up.
- Everything on the record. Not only what changed on an asset, but every action taken on it — whether a scheduled task fired it or a help-desk user ran it — with its output, all reviewable afterwards.
The name
An octopus has eight arms and a brain in each one — reach and independent intelligence in the same animal. Fold that into the three words it works among — monitor, administrator, operator — and you get Octotor. Eight arms, one VM.
The company
Octotor is built by Caprior, an IT services company based in Israel — the MSP the product grew out of. It's the tool we run our own work with.
Founded and led by Lior Szabo, who has spent 28 years running client infrastructure: networks, servers, endpoints, cloud, backup and recovery. Octotor began as an internal tool for that work. It's a product now because the problem it solves isn't ours alone.
Commercial enquiries: licensing@octotor.com · Security disclosures: security@octotor.com