Ecosystem · Technology Alliances

Integrate once.
Reach every Oasis cloud.

Infrastructure and software vendors, integrated into the platform. A technology alliance is wired into the catalogue, metering and billing — so an operator can sell your product, a customer can order it, and neither has to run an integration project first.

Become a partner Ecosystem overview
One integrationEvery operatorMetered and billed
Integrated, not listed
A logo on a slide reaches nobody. A catalogue item reaches every customer of every operator.
Certified once
The integration is validated against the platform, not rebuilt per deployment.
Sold by operators
Each operator sells your product in its own market, under its own brand and relationship.
Paid through the platform
Consumption is metered and settled by the same engine as first-party services.
The problem it solves

One integration instead of one per operator.

A vendor selling into regional cloud providers normally repeats the same work for every one of them: a connector, a pricing model, a billing arrangement, a support path. Oasis Stack makes that a single piece of work, because every operator runs the same platform.

What it runs on
Without the platform
A bespoke integration, commercial agreement and support path per operator, each with its own roadmap.
With an alliance
One certified integration, published to every operator that wants to carry it.
For the operator
A service they can add to the catalogue without engineering effort of their own.
For the customer
Something they can order, run and pay for in one place, alongside everything else.
Categories

Where alliances fit.

Nine categories across the cloud services and governance layers. If your product belongs in one of them, it can become a catalogue item.

Compute
Storage
Networking
Security
Backup & DR
Identity
Observability
Databases
AI Infrastructure
Ordered from the catalogue
Your product appears where the customer already orders compute and storage, with pricing attached.
Provisioned automatically
The platform calls your integration; no ticket, no manual step between order and running.
Governed like everything else
Identity, policy and approvals apply before your service is provisioned.
Metered and invoiced
Usage flows into the operator’s billing run and settles back to you.
How an alliance works

From a product to a catalogue item.

Four steps, done once, with the platform team alongside.

1
Fit
We agree where your product sits in the layers and what a customer would order.
2
Integrate
The connector is built against the platform APIs and validated end to end.
3
Certify
The integration is validated and made available to operators running Oasis Stack.
4
Publish
Operators add it to their catalogue, sell it in their market, and settlement follows usage.
What an alliance looks like

A catalogue item, not a logo.

A certified alliance service as an operator’s customer sees it: in the catalogue, with pricing, quotas and provisioning behind it.

What it takes

What we ask, and what you get.

An alliance is an engineering commitment on both sides. Stated before anything is signed.

You bring a product with an API
Something that can be provisioned, measured and supported programmatically.
We bring the integration surface
Catalogue, tenancy, metering, billing and governance, already built.
You bring support and a roadmap
A support path operators can escalate to, and notice when the product changes.
We bring the operators
Every cloud running Oasis Stack is a potential route to market for the same integration.
You keep your commercial model
Your pricing and your terms; the platform settles consumption against them.
We keep the customer relationship local
The operator owns its customer. You reach them through the operator, not around them.
Open. Modular. Intelligent. Limitless.

Integrate once. Reach the region.

A conversation about where your product fits in the layers and what a certified integration would involve.

Become a partner Talk to us