ARIA for MikroTik MSPs: one operator across many customers
A managed service provider looks after networks that belong to other people. Every customer has its own devices, its own history and its own tolerance for a change at the wrong hour. The hard parts are keeping those customers apart, and showing afterwards exactly what was done.
Customers kept apart
Every operator sees only the customers and devices granted to them. Access is scoped per user, an administrator grants and withdraws it, and a session can be ended from the admin side. A technician working a ticket for one customer does not see another customer's fleet.
A record the customer can read
Every confirmed write is logged with a tamper-evident record. Before the device is touched, a commit entry is stored. After the write, a reveal entry closes it, and a hash ties the two together so an auditor can check one against the other. If the first entry cannot be stored, the device write does not happen.
The audit log has an export. When a customer asks what changed on Tuesday, the answer comes from the record and not from memory.
Diagnosis in plain language
ARIA turns a ticket into checks, runs them on the live device and explains the result in operational language you can paste into the ticket. Reads need no approval. A health baseline of ping, path and speed gives every customer ticket the same starting point, whoever picks it up.
ARIA also carries a built-in knowledge base of RouterOS practice. A technician new to a customer's setup can ask how a rule works and get an answer without touching the device, and a configuration nobody on the team wrote can be pasted in and explained line by line.
Changes wait for a person
When a fix is needed, ARIA proposes it, as a vetted template where one fits, with the values filled in. Free-form writes are possible too, inside the permitted namespaces; a template-only mode exists but is optional and off by default. Either way, nothing runs yet. The engineer sees the exact change, the device and the customer, and approves it or not. The approval is single use and expires if nobody acts on it.
Limits sit in code. Free-form writes stay inside 16 permitted namespaces and 10 are never writable. A session is capped at 15 writes, and a classifier validated on more than 1,600 real commands decides what counts as a write. The model can ask. Only code decides.
Priced for a team
ARIA costs per user per month: Base at EUR 49, Pro at EUR 99 and Pro Max at EUR 199. Live writes need Pro or Pro Max, so a junior technician can diagnose on Base while the engineers who approve changes use Pro. The price follows the people using it.
If you resell or advise
Integrators and resellers who run MikroTik networks for customers can tell us so in the demo request. We will talk about how ARIA fits your service, on your own network and your own tickets.
Bring one of your customer networks and we will walk it through. See it live