What every engagement includes
The billing model in one table — what counts, what doesn't, and what the contract guarantees.
We charge for the work the product does: every Windows device that successfully completes a migration. No seat fees. No tenant fees. No consumption metering on operator activity.
Volume-banded pricing that lands below the cost of doing it manually, and well below the cost of doing it wrong. A real quote takes about a week — we cost it against your tenant pair and fleet size.
We'll publish list prices when our first production engagements complete. For now, pricing is set after we see your fleet — no spreadsheet trickery, no anchor-high quotes.
Two-week white-glove setup: tenant pair certification, mapping rules, dry-run wave on a pilot device, runbook handoff.
A dedicated single-tenant deployment in your own Azure region — your tenancy, your data residency. Available outside UK South on request.
99.9% availability with a credit schedule and priority incident response.
The billing model in one table — what counts, what doesn't, and what the contract guarantees.
| Operator console seats | Unlimited — billing is by migrated device, not by user. |
|---|---|
| Billable unit | One device that completes its migration successfully. Quarantine, abandoned, and never-started devices are not counted. |
| Failed devices | Recoverable failures are retried automatically; terminal failures route to quarantine. You are not billed for devices that did not migrate successfully. |
| Minimums | No per-month minimum on the pilot tier. Production tenants have a per-engagement minimum that scales with fleet size. |
| Service-level agreement | Standard 99.5% on the multi-tenant tier; 99.9% with the dedicated-region add-on. SLA credits per the contract. |
| Hosting model | Multi-tenant SaaS — no self-hosting in 2026. Enterprise customers can request a dedicated single-tenant deployment in your own Azure region. |
A 30-minute call with our fleet team. We'll quote you in five business days.