Kavros pushes a configuration change to every MikroTik you own — with a diff you read before it lands, a rollback that fires by itself, and proof from each site that the service came back.
Self-hosted. Runs on your hardware, credentials never leave your network.
| Name | Model | RouterOS | Uptime | |
|---|---|---|---|---|
| border-tll-01 | CCR2004-16G | 7.20 | 171d | |
| core-tll-02 | CCR1009-7G | 7.22.2 | 84d | |
| pop-tbs-01 | RB5009UPr+S+ | 7.19 | — | |
| pop-mil-04 | hAP ac² | 7.23.3 | 12d | |
| pop-rix-07 | hEX S | 7.22.2 | 6d |
The problem
You paste it into the first WinBox window and hope. Somewhere around the twelfth you have lost track of which ones took it, and the only way to find out is to open them one at a time.
That is how a Friday afternoon turns into an outage. It is also why most fleets still run a RouterOS from two years ago — the upgrade is a night of manual work with no way back.
Before it lands
No abstraction, no summary. The diff is the exact command list Kavros will send, and automatic checks refuse the whole batch if it would cut management access.
After it lands
Kavros probes the services your subscribers actually use, from each POP, and separates reachable from reachable but leaving through the wrong uplink — the failure nobody else reports, and the one that costs you the support call.
| Site | YouTube | Banking | Speedtest | ||
|---|---|---|---|---|---|
| Tallinn, EE | |||||
| Tbilisi, GE | |||||
| Milan, IT | |||||
| Rome, IT | |||||
| Riga, LV |
What Kavros does
Everything else in the product exists to make these three trustworthy.
Real RouterOS commands, blocking checks that refuse a dangerous batch outright, and a confirmation with a countdown before anything is sent.
Risky changes are armed before they are applied. If you do not confirm within the window, the router restores itself. Nothing to undo by hand at two in the morning.
Waves, automatic pause when the error rate climbs, failures grouped by cause, and a button that retries only what actually failed.
And the rest of it
Free for good. You pay only when Kavros starts changing the network for you.
How it is sold
Billed per site, not per device — growing your network does not quietly grow your bill. Runs on your own hardware, so credentials and configs never leave your premises.