What it runs on.
Oasis Stack is installed above infrastructure that is already running and publishes it as services. This page covers the technologies beneath it, how each one is published, and what Oasis Stack builds versus what it integrates.
The technologies beneath the platform.
Your infrastructure is deployed first. Each technology is connected once and becomes orderable, governable and billable — not merely visible in a dashboard.
What Oasis Stack itself is built with.
The platform is built on open technologies your team can inspect and support.
From a technology to a service.
A technology is published when a customer can order it, an operator can govern it and finance can invoice it, without anyone touching the underlying console.
What the platform needs from your estate.
An integration is not a connector dropped on top. These have to be true before a technology can be published as a service.
Every part, and where it comes from.
The platform layer is built by Oasis Stack, with CloudHost products integrated into it. Underneath and beside it, the platform runs on and connects to technology your team may already know, including more than 15 open-source tools across the modules, the stack and the integrations. The ones that shape the architecture are listed here.
Every integration listed is validated and functional. Supported versions are confirmed for your deployment during design.
Related parts of the architecture.
Bring us your estate and your systems.
We will map what you run today against the catalogue it could become, and where each system connects.