Pricing

A flat fee, banded by scale.
Not a share of your growth.

The platform is licensed at a flat fee per deployment, banded by scale, for the modules you adopt, and federation is a flat participation fee. What you charge your own customers stays entirely yours — we do not take a percentage of it, and we do not price by the core.

Get a quote See what you would operate
Flat fee, banded by scaleFlat participation feeNo per-core licensing
Not per core
Add capacity inside your band and the fee does not move. A refresh is a hardware decision, not a licensing one.
Not a revenue share
Federation is a flat participation fee, never a percentage of what you earn.
Not consumption billing
You are not billed for the usage you are busy monetising.
Adopt what you need
Modules priced for the ones you actually run.
The question

Most platforms are priced to grow with you. That is the problem.

Per-core licensing grows with your hardware. Consumption billing grows with your customers. Marketplace revenue share grows with your success. All three are the same arrangement wearing different clothes: the better your cloud does, the more of it belongs to someone else. Sovereignty that ends at the invoice is not sovereignty.

How it is priced

Four parts, and two of them are yours.

The commercial model in full. There is no fifth line item and no percentage hidden in one of these.

1 · Platform fee
A flat fee per deployment for the modules you adopt, banded by the scale of the estate. Not per core, not per socket, not per virtual machine.
2 · Federation participation fee
A flat participation fee to connect to other Oasis clouds. It does not scale with the revenue federation brings you.
3 · What you charge
Entirely yours. Your catalogue, your prices, your margins, your invoice to your customer. We take no share of them. CloudHost sits in the invoice chain only for a federated purchase: the delivering partner invoices CloudHost, and CloudHost invoices you.
4 · Partner margins
Set by you and settled automatically by the commercial module, on the terms you agree with your own partners.
How a band works

A staircase, not a slope.

Banded does not mean unlimited, and we would rather explain the difference than let you find it in a renewal.

One fee per deployment
The fee is set for the deployment and the modules in it, against the band your estate sits in. It is not multiplied by anything you add inside that band.
Growth inside a band is free
Hosts, sockets, virtual machines, tenants and customers can all grow without the platform fee moving. This is where the difference with per-core licensing actually lands.
Crossing a band is a step
At some scale you move up a band and the fee steps. The bands are agreed at the outset, so you can see the step coming and plan a business case around it.

Why this is not a technicality. Per-core licensing is a slope: every core you add is a purchase, so cost tracks your estate continuously and your margin thins as you grow. Banding is a staircase: you grow into headroom you have already paid for, and step deliberately when you outgrow it. The difference is not that one is cheaper on a given day — it is that one of them is predictable enough to build a business plan on.

See what your current licence does as you grow
What decides your number

Four variables, all of them knowable up front.

We quote per deployment because these genuinely differ — not to keep the number vague until you are committed.

Which modules you adopt
Oasis Core is the foundation. Cloud Foundation, AI, Governance, Digital Transformation and CloudSouq are taken as you need them.
The scale of the estate
Sized on the infrastructure the platform sits above, agreed once, not metered continuously.
The deployment model
A federated operator cloud, a sovereign or air-gapped cloud, an enterprise cloud and an edge deployment are different pieces of work and are priced as such. Deployment architectures
Support and managed services
Run it yourself with Amin, or have it operated for you. That choice changes the number and nothing else does.
Why not the alternatives

The three models we chose not to use.

Each of these is normal in this market. Each of them makes your growth someone else’s revenue.

Elsewhere
Per-core licensing
The model that made virtualisation expensive: every core you add is a licence you buy, so a hardware refresh becomes a budget negotiation.
Elsewhere
Consumption billing
You are charged for the usage you are trying to monetise, and your margin thins exactly as your cloud succeeds.
Only with Oasis Stack
A banded fee you can plan against
The platform costs what your band costs. The customers, the pricing, the margins and the upside of every one of them stay with you.
How to get a number

Three steps to a figure you can take to a board.

No trial tier and no self-serve checkout — but no drawn-out discovery either. The variables above are what we ask about.

1
Talk
What you are building, the estate it sits on, and the market or mandate behind it.
2
Assess
Which modules, what scale, which deployment model, and who operates it.
3
Quote
A flat fee per deployment, banded by scale, and, if you are federating, a flat participation fee — with the assumptions written down.
Your customers. Your pricing. Your margins.

Get a number you can plan against.

A conversation about the four variables above, and a quote with its assumptions stated.

Get a quote See the partner programme