Start with a conversation.
Leave with a plan.
Oasis Stack is not bought from a web page. A cloud you will own for years starts with a conversation about what you want to build, an assessment of what you already run, and a design your board can review before anything ships.
Six stages. Something in your hands after each.
Every stage ends with a deliverable you keep, so each decision is made on evidence rather than a pitch.
-
01
Talk
A conversation about your ambition: the cloud you want to own, the market and the rules you operate under.
You holdA shared view of the model that fits — Oasis Federated, Sovereign, Enterprise or Edge Cloud. -
02
Assess
Your estate and your obligations, mapped to a cloud model and a first wave. For operators, a market analysis, an infrastructure review and a financial case; for sovereign programmes, your mandate mapped against the seven layers.
You holdAn assessment of what you run today — for operators, an opportunity and ROI report. -
03
Design
Platform sizing, the reference architecture, the bill of materials and the commercial plan, so engineering, sales and finance work from one plan. The boundary, the deployment model and the governance policies are agreed before anything is built.
You holdAn architecture and business blueprint, and a quote that reflects your estate rather than a list. -
04
Deploy
Oasis Stack deployed on your infrastructure, integrated, hardened and validated — and connected to the federation if you choose.
You holdA production cloud platform. -
05
Enable
Technical training, sales enablement and operational readiness: teams trained, processes documented, ready to launch.
You holdTrained teams, runbooks and playbooks. -
06
Operate
Run it yourself, have the Oasis Stack team operate it under a support contract, or split the work by layer — L1 with your teams, L2 and L3 with the Oasis Stack team — and take on more as your team is ready.
You holdAn operating model you chose, and a platform your team can grow into.
A cloud launches in 90 days, because the platform layer — tenancy, the customer lifecycle, billing, governance and the marketplace — already exists. The work is decisions, deployment and launch, not software development.
Customers, pricing, billing and the relationship stay yours in every model, whoever runs the platform.
The same software whether you run it or CloudHost does, so moving work between your team and ours never means re-platforming.
Pick the step that matches where you are.
The first step is a conversation.
Tell us what you are building. We will tell you which model fits and what an assessment would cover.