Helix AI NMS+
One platform for both halves of an ISP: the network operations that keep the service up, and the business operations that get it paid for. Purpose-built for MikroTik RouterOS, and mobile-money-native because that is how our market actually pays.
Pre-GA In production on 100+ RouterOS devices serving paying subscribers today.
Heads up. NMS+ is pre-GA and already carries real traffic, which is an uncomfortable combination and we would rather you heard it from us. A bad change affects real customers' internet service. The hardware-validation gate has never been signed — there is no dedicated lab and no canary cohort — so every device-facing acceptance criterion in the delivery programme is currently unvalidated. Anyone evaluating this platform should ask for the gap register, and we will hand it over.
The fleet, from one place.
Most MikroTik estates are administered one Winbox window at a time. NMS+ is the alternative: a multi-tenant controller that reaches every device, including the ones with no public IP.
Device orchestration
Reach and manage RouterOS v6 and v7 devices across sites and tenants, including devices behind carrier-grade NAT with no reachable address of their own.
Telemetry
Time-series collection into a purpose-built store, so device and link history is queryable rather than a graph that resets when you close the window.
Provisioning
Bring a device onto the network with its configuration applied, rather than typing it in and hoping the next engineer types the same thing.
Fleet maintenance
Firmware and configuration work across many devices as a planned operation with a record, instead of an evening and a spreadsheet.
The half of an ISP that nobody demos.
Network management products stop at the router. An ISP does not. NMS+ carries billing and collections, CRM, IP address management, ticketing, and a self-service surface subscribers can actually use — in the same system that knows which device serves them.
- Billing and collections, mobile-money-native
- Customer records tied to the service, not to a spreadsheet row
- IP address management that reflects what is actually deployed
- Ticketing where the subscriber and the device are the same record
- Subscriber self-service
Two vantage points, one verdict.
NMS+ measures from inside the network. Helix Internet Monitor measures from the subscriber's own computer. Where they agree, the argument is over. Where they disagree, the shape of the disagreement narrows the fault domain by itself.
The two systems exchange data over a published contract, and the direction is fixed: NMS+ is always the client. Subscriber telemetry is pulled per service and time-bounded, never bulk-exported into an ISP-operated store — because the moment a copy lives elsewhere, the subscriber's revocation stops being something the code enforces.
What is not settled yet.
The platform's own documentation is written as a defect register rather than a brochure, and that is deliberate. The short version:
- Pre-GA. Live production usage is not the same as a general- availability product, and we do not present it as one.
- The hardware validation gate is unsigned — no dedicated lab, no canary cohort — so device-facing acceptance criteria are unvalidated.
- Capability claims on this page describe what the platform does, not when any particular capability reaches your deployment.
Ask for the gap register before you commit to anything. It is a real document and we will send it.
See it against your own estate.
Tell us how many devices you run, which RouterOS versions, and how you bill today.