Straight answers.

Oasis Stack is a cloud platform that runs above the infrastructure you already own and turns it into a cloud you can run as a business: a self-service portal, a catalogue, multi-tenancy, metering and billing, governance and a marketplace. It is a CloudHost initiative, and CloudHost runs its own public cloud, YallaCloud, on six Oasis Stack modules in production.

None of the three. A hypervisor virtualises servers and a cloud management platform orchestrates them. Oasis Stack sits above both and adds what turns infrastructure into a cloud business: tenancy, the customer lifecycle from order to invoice, governance, a marketplace and federation. And it is not a public cloud: it runs on infrastructure you own or choose, under your brand.

It runs above what you already have and publishes it as services: CloudStack, OpenStack, VMware, Kubernetes, bare metal and GPU, on x86 or ARM hardware, in your own data centre or a colocation facility you choose. There is no forklift migration and no lock-in to any infrastructure vendor.

Seven modules, adopted as you need them. Oasis Core runs tenancy and the customer lifecycle. Cloud Foundation provides compute, storage, networking, Kubernetes, managed PostgreSQL, MySQL, MariaDB, MongoDB and Microsoft SQL Server, and backup and disaster recovery across tiers 0 to 3. Infrastructure for AI adds GPU and AI-ready services, including AI Factory and WorkspaceAI. Governance, Security & Compliance, adopted when needed, covers identity, policy and audit. Digital Transformation brings AppLite, secure application delivery without a VPN, legacy applications as they are, and virtual desktops. CloudSouq is the marketplace.

Amin is the intelligent cloud guardian: it helps the operator manage the platform and the infrastructure beneath it. Noura is the cloud journey companion for your customers, from infrastructure to outcomes. Neither is a chatbot bolted onto a portal — both read the platform’s own signals and records.

You do. Your customers see your brand, your prices and your invoices. What you charge them stays entirely yours: the platform does not take a share of it.

Not to any infrastructure vendor. The platform runs above the hardware and hypervisors you choose, so you can change or add infrastructure underneath without re-platforming.

Yes. From VMware, ESXi and vCenter stay; Oasis Stack replaces the tier above them — vCloud Director and Aria — and moving storage from vSAN to Ceph is optional. From Red Hat, RHEL inside guest virtual machines stays; Oasis Stack replaces OpenShift and the management platform above it.

Not unless you decide it should. Data, backups and replicas stay where your residency policy says, and the platform enforces that policy. Only financial and contractual transactions cross the Oasis Federation Core; workloads and data do not, and customer data never moves automatically.

No platform can be certified on your behalf. A certificate attaches to an organisation, its scope and its operating practices. What Oasis Stack does is make controls enforceable and produce the evidence continuously, so each partner’s assessment of its deployment rests on records rather than screenshots. CloudHost holds ISO certificates, available on request.

You can. Keys can be held in your own hardware security modules, and bring-your-own keys is supported. Privileged operations can require a second person, and privileged sessions are recorded.

Yes. Oasis Sovereign Cloud deploys in three ways: a shared national cloud for many government bodies, a private cloud for a single government body, and an air-gapped deployment for isolated bodies and classified environments. The platform and the catalogue are the same in every one; an air-gapped deployment runs fully locally, with no federation and no link to the admin centre, and licences, updates and patches are carried in by Oasis Stack team members.

Our GCC compliance guide lists the frameworks buyers in the UAE, Saudi Arabia and Bahrain most often answer to — data protection laws, national cybersecurity controls, cloud standards and sector rules such as SAMA’s and the CBB’s — with links to the official sources, and what a platform can and cannot do for each.

Federation lets independently owned Oasis clouds publish services to the federation and consume each other’s, brokered by the Oasis Federation Core, so your catalogue can be bigger than what you run yourself. Your customers, data and operations stay home. It is a choice, not a requirement: a cloud runs fully on its own and connects when it decides to.

A flat participation fee — not a share of your growth, and not a cut of what you earn. A federated purchase is invoiced through CloudHost: the delivering partner invoices CloudHost, and CloudHost invoices the requesting partner.

The platform is licensed at a flat fee per deployment, banded by scale, for the modules you adopt. Federation is a flat participation fee. There is no per-core licensing and no revenue share.

Because a quote depends on what we learn in the first conversations — the scale of the deployment, the modules you adopt and how it will be operated. Every quote follows an assessment, so it reflects your estate rather than a list.

A cloud can launch on Oasis Stack 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.

Yes. You can run the platform yourself, have the Oasis Stack team operate it for you under a support contract, or split the work. Support is organised in three layers — L1, L2 and L3 — and you decide which of them CloudHost covers. Whoever runs it, the customers, the pricing and the margin stay yours.

YallaCloud, the CloudHost group’s public cloud, runs six Oasis Stack modules in production and is federated across multiple locations. The African Healthcare Cloud is a delivered industry cloud built on the same foundation.

Oasis Stack is a CloudHost initiative. Across the CloudHost group: 100+ customers, 40+ engineers and operators and 10+ years of running cloud — group figures, not Oasis Stack metrics. Leadership and the wider group are on the CloudHost website.

In the Middle East. CloudHost built Oasis Stack in the UAE, and the Middle East and Gulf is where we operate and are held to account.