Every organisation that decides to sell cloud services reaches the same fork. One road is a reseller agreement with a global provider: quick to sign, and described as a partnership. The other is building a platform of your own: yours to keep, and measured in years and in engineering budgets few can raise.
It is the trade the industry offers everyone. You can have a cloud that works, or a cloud that is yours.
Oasis Stack exists because we do not think that trade is necessary. This article explains plainly how it lets a provider launch a cloud, run it and earn from it.
The hard part was never the servers
Telecom operators, data centre operators, MSPs, governments and large enterprises mostly have infrastructure already. Racks, power, networks, virtualisation, and teams who keep it all running. What they lack is the layer that turns infrastructure into something a customer can buy.
That layer is larger than it looks: tenancy and isolation, a self-service portal, a catalogue, provisioning, metering, billing, a marketplace, identity, policy, audit, and the tooling to operate all of it. Built in-house, it takes large engineering teams and long development cycles, and it is never finished, because every part must be kept current and secure for as long as the cloud runs.
That is why cloud ownership stayed with a handful of companies. Infrastructure was never the scarce part.
The infrastructure was never scarce. The layer above it was.
Launch: above what you already own
Oasis Stack runs above infrastructure you already own and publishes it as services. It works with CloudStack, OpenStack, VMware, Kubernetes, bare metal and GPU estates, on x86 and ARM, on-premises or in a colocation facility you choose. There is no lock-in to any infrastructure vendor, and no requirement to replace hardware you have already bought.
Because the platform layer exists, launching becomes a matter of decisions and deployment rather than software development: which customers you serve, which services you offer, how you price them and how your brand appears. From concept to cloud in 90 days is simply what the timeline looks like when nothing has to be built from scratch.
Operate: one brain for the whole lifecycle
Providers who do build a cloud usually end up running a patchwork. One system for infrastructure, another for provisioning, a third for billing, more for monitoring and security. Every seam between them is somewhere an order, an invoice or an incident can go missing.
Oasis Core is the administration module that replaces the patchwork. It holds tenancy and the whole customer lifecycle in one place: onboard, order, provision, operate, bill, grow. Enterprises, public bodies, resellers and business units each run as isolated tenants on shared infrastructure.
Around it sit the tools an operations team needs. The Wellness Dashboard, built on Grafana, Prometheus and Wazuh, shows the health of the platform. The platform is API-first: pre-built connectors for SAP, Stripe and Paymob, and a REST API for the OSS/BSS, ERP, CRM, ITSM, SIEM, CMDB and DCIM systems you already run. And two intelligence layers read the platform’s own signals and records: Amin, the intelligent cloud guardian, helps the operator manage the platform and infrastructure; Noura, the cloud journey companion, guides the operator’s customers. Neither is a chatbot bolted onto a portal.
You also decide how much of it you run. Operate the cloud yourself, or have the Oasis Stack team operate it for you under a support contract, with support in three layers: L1, L2 and L3.
Monetise: a catalogue worth buying
A cloud earns from what customers consume, month after month. That takes a catalogue deep enough that a customer’s second, third and fourth purchase come from you.
- Cloud Foundation — 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 — GPU and AI-ready services, including AI Factory and WorkspaceAI, with PyTorch, TensorFlow, JAX and Triton.
- Digital Transformation — secure application delivery with AppLite (no VPN), legacy workloads run as they are, and virtual desktops.
- CloudSouq — the marketplace, where partners’ software and services sell alongside your own. Your storefront, your brand, your margin.
The commercial model keeps the upside with you. The platform is licensed at a flat fee per deployment, banded by scale. What you charge your customers is yours to set, and yours to keep.
Govern: control you can prove
Governments, banks and health systems do not buy a cloud on trust. They need to see who has access, what changed and which control stopped what.
The Governance, Security & Compliance module, adopted when a programme needs it, handles identity, policy and audit across every service, with VirtueSuite, hardware security modules, bring-your-own keys, a two-person rule and session recording. It is worth being precise about what that achieves. A platform cannot be certified on your behalf; frameworks such as the ISO 27001 family or national cybersecurity controls are assessed against the operator. What the platform does is make the controls enforceable and the evidence automatic.
Sovereignty works the same way. Residency is one question; sovereignty is seven: data, infrastructure, operations, identity, security, governance and technology. Three deployment models — a shared national cloud, a private cloud for one government body, and air-gapped — let the boundary sit wherever the mandate requires.
Federate: bigger than what you build
There is a fair objection to all of this. A cloud you own can only sell what it can run, and your customers will compare you with catalogues built by thousands of engineers.
Federation is the answer. Independently owned Oasis clouds publish and consume services by explicit agreement. Your customers, your data and your operations stay home, and customer data never moves automatically. But your catalogue can include services another cloud runs, and your services can reach customers you would never have met. Federation is a flat participation fee, not a share of your growth.
Own the cloud. Borrow the scale.
Built by an operator
A platform is easier to trust when its maker runs a cloud on it. CloudHost does. YallaCloud, the CloudHost group’s public cloud, runs six Oasis Stack modules in production. The platform was shaped by the same problems its customers face: orders that must become invoices, tenants who must never see each other, and regulators who ask for evidence rather than assurances.
What it is for
Oasis Stack is not an attempt to turn every operator into a hyperscaler. It is a way to stop paying for the assumption that only hyperscalers can own a cloud. Launch on what you own. Operate it as one system. Sell a catalogue bigger than you could build alone. Keep the customer.
Sovereignty should not cost you scale. Neither should ownership.