Use case · Managed service providers
Run networks for many customers
Each customer is its own tenant, with its own sites, roaming clients, administrators and policy. You bring up their sites without travelling to them.
Why it suits an MSP
- One sign-in across your customers' organisations. Create a customer's organisation yourself or be invited into theirs, and move between them from the menu. Each keeps its own sites, people and audit log, which records you joining and switching in. How it works.
- Separate tenants. Every request in the console and API is scoped to one tenant, and automated tests fail the build if a handler bypasses that scoping.
- Remote bring-up. The customer, or anyone on site, installs Ubuntu and pastes one command. There is no appliance to stock or configure in advance.
- Safe change at scale. In each customer's organisation, changes go to one canary site first, a site that a change breaks puts its last good configuration back by itself, and every site reports drift from its intended configuration. For a customer with one or two sites, the roll-back does most of the protecting.
- Maintenance windows. Mark a site as deliberately away for a set time so planned work does not page anyone, and the window ends by itself.
- Hardware you choose. Standardise on any machine that runs Ubuntu 24.04 or 26.04, x86-64 or ARM64.
Partner pricing is by arrangement — talk to us.