One console per client doesn't scale
Ten clients, ten dashboards, ten logins. Your engineers spend the day context-switching instead of operating.
A realm per client, access scoped to it, every change attributed — and per-machine pricing that scales with your book of business.
Ten clients, ten dashboards, ten logins. Your engineers spend the day context-switching instead of operating.
When a client asks, the answer can't be a shrug. You need per-change attribution you can hand over.
Clients want to know where their packages, logs and credentials live — and "a vendor's cloud" is the wrong answer.
Organize each client as a realm, with cells per environment or site. Scope a member — your engineer or the client's own team — to a single realm or cell with one of four roles. The whole book of business sits behind one console, and every rollout and config change carries who-changed-what.
A real capture of the running product. Live data, no mockups.
Four roles — principal, lead, engineer, observer — scoped down to a single realm or cell
Route alerts by severity or event — email, Slack, Telegram, webhook, PagerDuty
Packages, logs and credentials live on a vault you control — not a vendor's cloud
Per-machine pricing: larger fleets always get the better unit price
Every point above is a shipped capability, on every plan — see the full list.
MSP contracts live and die on accountability. Every action on a client's machines is attributed and scoped — so the answer to “who touched our fleet?” is an export, not an email thread.
Per-change attribution across every client realm, exportable to CSV
Scoped access proves separation: your engineer sees one client, not all of them
Data location has a one-line answer: packages, logs and credentials on hardware you control
Onboard your first client in minutes. The first 5 machines are free, no card required.