The cloud CloudHost runs, on the platform it built.
YallaCloud is the CloudHost group’s public cloud. It runs on Oasis Stack in production: the same portals, catalogue, billing, operations and governance any operator would run.
Run a public cloud as a business, not as an estate.
CloudHost already operated infrastructure. What a public cloud needs on top of it is the part most platforms leave to integration projects: a customer portal, a catalogue with pricing, quoting and subscriptions, metering and invoicing, an operations console, a marketplace, and governance that produces its own evidence.
Oasis Stack was built to be that layer. YallaCloud is where it runs first, under CloudHost’s own operators, before it is offered to any other cloud.
Six modules and both intelligences, in production.
YallaCloud is not a pilot beside the platform: its customer-facing, commercial and operational surfaces are the platform’s own modules. It runs all six, from the storefront customers buy from to the GPU capacity and modernisation services they order through it.
From order to invoice, without a hand-off.
Four screens, one lifecycle. These are sample screens; the real YallaCloud screenshots replace them.
YallaCloud, as its customers see it.
The platform film and the live screens, once captured from production.
What the operator gets.
Outcomes described the way CloudHost’s own team runs YallaCloud. Customer results and quotations are published with permission.
CloudHost group figures across all of its cloud operations. They describe the company behind Oasis Stack and YallaCloud.
The same platform, whichever cloud you are building.
YallaCloud exercises the whole stack. Each cloud model uses the same modules with a different owner, boundary and market.
The cloud CloudHost runs on the platform it built — two pages to share internally.
See it running before you build.
A walkthrough of YallaCloud on Oasis Stack, with the portal, operations and billing your cloud would run.