Service Plans
Managed IaaS has no tiers to choose between. There is one consumption-based plan: you pay for the infrastructure you actually run, measured and billed against each onboarded project.
How the plan works
Pay as you go
No fixed bundle and no upfront commitment. Consumption is metered as you provision, resize, and release resources, so the bill follows the shape of your workload.
Billed per onboarded project
The OpenStack project is the billing boundary. Each onboarded project is metered separately, so multiple teams or environments never share a single undifferentiated invoice.
What gets metered
The resources you provision through the OpenStack components — compute, block and object storage, networking, load balancing, and backup targets.
What counts as an onboarded project
An onboarded project is a tenant that UNICC has created and configured for your team. It is the unit that carries your quotas, your role assignments, and your network and storage boundaries — and therefore the unit that consumption is attributed to.
Because the project is the billing boundary, it is also a useful separation boundary. Teams commonly onboard more than one:
- Per environment — separate production from development and test, so non-production spend is visible on its own and quotas cannot be borrowed across the boundary.
- Per application or team — attribute spend to the group that owns the workload, without building a chargeback layer of your own.
Quotas are set per project at onboarding and can be revised as your requirements change. They act as a ceiling on what a project can consume, which is the main control available for keeping pay-as-you-go spend predictable.
Operating model
UNIQCloud Managed IaaS services are currently operated by UNICC teams.