Oasis Stack Oasis Stack A CloudHost Initiative
EN
Talk to us
Architecture · Integrations

What it connects to.

Infrastructure sits underneath the platform. Payments, finance, CRM, identity and carrier systems sit beside it, and a helpdesk is built in. Oasis Stack is API-first, so it works with the systems a cloud business already runs instead of replacing them.

Talk to an architect What it runs on
REST APIPre-built: SAP, Stripe, PaymobHelpdesk built in
A white platform block with a payment terminal, a ledger, document stacks, a service desk and a rack unit plugged into it by glowing cables
The systems beside the platform

Each system keeps its role.

The platform hands each one the orders, usage, invoices and records it needs, through its APIs.

Payments
Pre-built connectors for Stripe and Paymob, collecting what the platform invoices.
ERP and finance
A pre-built connector for SAP; other finance systems through the REST API.
Helpdesk
Built into the platform: support cases tied to the service and the tenant.
CRM
Your CRM through the REST API, alongside the platform’s own mini CRM.
Identity
Through VirtueSuite: LDAP, SAML, and single sign-on with Microsoft Entra and Google Workspace. Local and national identity providers are integrated per region at setup.
OSS/BSS
Carrier operations and telecom billing stacks, through the REST API.
DCIM
Power, cooling and capacity tooling, through the REST API.
SIEM and CMDB
Security events forwarded to your SIEM through Oditr and Observa; configuration records through the REST API.

The SAP, Stripe and Paymob connectors are pre-built, validated and functional. Other systems connect through the REST API.

API-first

Every console action is also an API call.

The platform’s API is REST, with Terraform, a command-line tool and SDKs. Whatever a person can do in a portal, another system can do through the same API, under the same rules.

Portals and APIs from one source
The customer, partner, operations and administration portals, and the APIs behind them, are delivered and managed by Oasis Core.
Driven from outside
Service desks, pipelines and billing systems can drive the platform directly.
The records worth carrying
Orders, subscriptions, usage and invoices from the commercial module are what connectors move into finance and sales systems.
Governed like everything else
Alliance and marketplace services are provisioned through the same catalogue, policy and metering path as first-party services.
Integration alliances

Integrate once. Available to every Oasis cloud.

A system integrates once with Oasis Stack, and every partner cloud can switch it on.

1
Fit
Where the system connects, and what a partner needs from it, is agreed.
2
Build
The connector is built against the platform APIs and validated end to end.
3
Certify
The integration is validated and made available to partners running Oasis Stack.
4
Switch on
Partners switch it on for their cloud; their customers never see the plumbing.
Become an integration alliance
Integrate once. Reach every Oasis cloud.

Bring us the systems you run.

We will map where each one connects, and what the platform hands it.

Talk to an architect What it runs on