A fixed annual base fee covers the platform. MRUs (Managed Resource Units) scale with what you actually run through it. The more value you get, the more you pay — and not before.
Component 1
An annual platform licence. Fixed. Covers the Cloud Orchestrator deployment, software updates, and support — regardless of how many tenants you onboard or resources you manage.
Component 2
One MRU per manageable item in the portal, per month. Not just the top-level resource — every configurable component attached to it counts too. A VM plus its storage, network, load balancer, backups, and snapshots each count as one MRU. A cluster counts as one MRU, plus one MRU per node. You only pay for what is actively managed.
MRU Definition
The rule is simple: anything the tenant can configure from the portal counts as one MRU. That includes the primary resource and every component attached to it.
A VM with 2 volumes, a network, a load balancer, 1 backup, and 1 snapshot = 7 MRUs
A 5-node cluster = 6 MRUs (1 cluster + 5 nodes). What runs inside the nodes is not metered.
Cloud Orchestrator does not look inside the cluster at containers or workloads. Only what is visible and configurable in the portal counts.
The principle: if the tenant can see it and configure it in the portal, it is an MRU. If it is invisible to the portal — like workloads running inside a cluster — it is not counted. This keeps metering transparent and directly tied to what Cloud Orchestrator actually manages.
Examples
Cloud Service Provider
50 customers, each with 10 VMs. Each VM has 2 storage volumes, a network, and a backup — that's 5 MRUs per VM.
Consumption
2,500 MRUs/month + base fee
As customers attach more volumes or create more snapshots, MRUs grow. As they deprovision resources, MRUs drop immediately.
Bank
12 business units, each with 2 clusters of 5 nodes each. That's 6 MRUs per cluster, 12 per unit.
Consumption
144 MRUs/month + base fee
Grows as teams add nodes or request new clusters. Predictable because infrastructure changes are managed through the portal.
Government Agency
6 agencies, each running 3 clusters (4 nodes each) and 8 VMs with storage and a backup per VM.
Consumption
~390 MRUs/month + base fee
Air-gapped deployment. MRU count is stable once environments are set up — changes only when agencies provision or decommission resources.
FAQ
No. MRUs are counted against actively managed resources visible in the portal. Once a resource — or an attachment like a backup or snapshot — is deprovisioned, it stops counting toward your MRU total the following month.
Per deployment. If you run Cloud Orchestrator in a single data centre, that is one deployment and one base fee. Multi-site deployments are discussed at contract time.
MRU billing is based on actual monthly consumption. If you provision more resources in one month and fewer the next, your bill reflects that. There is no minimum MRU commitment on top of the base fee.
No. The base fee is not per-tenant and not per-user. You can onboard as many tenants and as many users as your infrastructure supports — the only consumption variable is MRUs.
The platform licence, all software updates during the contract period, and access to Stakater support. Onboarding and professional services are included for the initial deployment.
Yes. We run a 90-day pilot scoped to a defined set of tenants and services. The pilot is designed in the complimentary 2-hour design workshop before any contract is signed.
Tell us your infrastructure, your tenant model, and your expected MRU range — we'll come back with a number. No obligation, no sales pressure.
Talk to salesStart with a complimentary 2-hour design workshop. We design your service catalog, tenant model, and 90-day pilot scope — with your team, on your infrastructure.