The four parts of the platform
RobustLink
Fleet health in real time, and the tools to act from the same place. Monitor and roll out signed firmware, applications and configuration, or open a remote CLI when precision is needed.
RobustVPN
A private overlay network that rides on any SIM or fixed line. Gateways get fixed private IPs, so you can reach a single device — or a small subnet behind it — as if you were on site.
Operations Console
The estate-level view leaders ask for and the tools engineers actually use. Map every site, read rolling 30-day trends, enforce data caps, and triage with checks, logs and packet capture.
Wi-Fi Portal Manager
For sites offering guest or contractor Wi-Fi: a branded captive portal, fair-use limits, and optional DNS filtering.
What it actually does
Zero-touch provisioning
Register a device to your account before it ships. It pulls its own configuration on power-up, so whoever installs it does not have to be a network engineer.
Real-time insights and alerts
Custom dashboards across the estate, with alerting before a quiet problem turns into an outage.
OTA updates and configuration control
Firmware, applications and config pushed over the air — staged and verified across the fleet rather than device by device.
Remote access
Reach a device's web interface or command line through RobustVPN, without anyone standing in front of the cabinet.
APIs and App Center
Open APIs to push device and connectivity data into the systems your team already works in, plus an App Center for extending what runs on the device.
Two ways to run it
The same platform either way. The difference is where it runs.
RCMS Cloud
The hosted instance, running on Microsoft Azure. Nothing to stand up: accounts, devices and dashboards are there from day one. This is what most deployments use.
RCMS Stack
The same platform deployed inside your own environment — on-premises or in your private cloud — where data residency, network isolation or procurement policy rules out a shared SaaS instance.
From shipped box to managed fleet
The point of zero-touch provisioning is that steps one and two happen without an engineer on site. Everything after that happens without one too.
Pre-register
Devices are registered to your account before they ship, so nothing needs configuring by hand in the field.
Power up on site
The device calls home, pulls its configuration and joins the fleet. Whoever installs it does not need to be a network engineer.
Monitor
Health, connectivity and data usage roll up into dashboards, with alerting before a problem becomes an outage.
Update
Signed firmware and application updates go out across the fleet, staged and verified rather than one device at a time.
Reach in when needed
Secure remote access to the device itself for diagnosis, so a site visit is the last resort rather than the first.
Who it is built for
Operations leaders
The estate-level view: where every site is, how it is trending, and what is costing money in data.
Network engineers
Remote CLI, logs and packet capture — the tools you would use on site, from wherever you are.
Developers and integrators
APIs and the App Center, for pushing device data into your own systems rather than logging into someone else's dashboard.
Distributors and MSPs
Multi-tenant management through the Distributor Console, for running several customers' fleets side by side.