Oasis Stack Oasis Stack A CloudHost Initiative
EN
Talk to us

Oasis Multi-Cloud

Your cloud doesn't end at your data centre.

Oasis Multi-Cloud connects private cloud, sovereign infrastructure and public-cloud environments through one operating model. Choose where workloads run; keep the operating context consistent.

Explore Multi-Cloud View multi-cloud architecture
  • One operating
    model
  • Freedom
    of choice
  • Governed
    and secure
  • Optimised for
    business outcomes

Same operating model.
More possibilities.

The challenge

More clouds shouldn't mean more complexity.

Applications run across private infrastructure, sovereign clouds, hyperscalers, edge locations and AI environments. Every additional cloud brings another portal, identity model, resource structure, billing model, policy system and operations process.

  • PortalsOne per cloud
  • IdentitiesSeparate models
  • BillingMultiple models
  • PoliciesInconsistent
  • OperationsSiloed
  • VisibilityLimited
Multi-CloudConnectNormaliseGovernOperate

One operating context across every cloud.

OutcomeUse multiple clouds without multiplying operational complexity.

Our approach

Your cloud remains the foundation.

Multi-cloud should extend your cloud, not replace it. Start with infrastructure you control and extend when the workload needs it. Connecting a public cloud moves nothing by itself, and there is no lock-in to any infrastructure vendor.

Not the same as federation: federation connects independently owned Oasis clouds by agreement; Multi-Cloud brings public-cloud capacity into your own platform.

How federation works

Your infrastructure

  • Cloud Foundation
  • Your data centres
  • Sovereign regions
  • AI infrastructure

Oasis Multi-Cloud

  • Discover
  • Govern
  • Orchestrate
  • Operate
  • Optimise

External clouds

  • AWS
  • Microsoft Azure
  • Google Cloud
  • Partner clouds and more

One hierarchy

Location changes. Context doesn't.

Every resource, in your data centre or a public cloud, stays associated with the same Organisation → Estate → Unit → Resources structure.

  1. OrganisationWho owns it?
    • Corporate identity
    • Global policies
    • Administrators
    • Commercial boundaries
  2. EstateWhich environment?
    • Security posture
    • Location policies
    • Service entitlements
    • Access boundaries
  3. UnitWhich workload?
    • User access
    • Application policies
    • Resource quotas
    • Environment controls
  4. ResourcesWhere does it run?
    • VMs and storage
    • Databases
    • Kubernetes
    • GPU and applications

Real-world example

One unit. Multiple clouds.

A unit represents the workload even when its resources span several clouds. Cloud boundaries should not become operational boundaries.

Organisation · Estate · UnitAcme Corporation · Production · Digital Commerce
Oasis Stack

Application servers

  • UAE · private
Oasis Stack

Database and sensitive customer data

  • UAE · private
AWS

CDN and object services

  • Frankfurt
Microsoft Azure

Analytics

  • Europe
Google Cloud

AI services

  • Global

OutcomeEverything stays connected to the same business context. Example shown.

Key capabilities

One layer across your cloud landscape.

What the module provides. Exact services depend on each connected provider and integration.

  1. 01

    Cloud Connections

    Controlled integrations that hold provider relationships, credentials, accounts and regions.

  2. 02

    Resource Discovery

    External resources placed in context: not i-0873…, but Acme → Production → Digital Commerce.

  3. 03

    Unified Service Catalogue

    Approved private and external services in one experience, without learning every portal.

  4. 04

    Multi-Cloud Governance

    Which clouds, regions, estates and units may use external services, and with what approval.

  5. 05

    Cost & Consumption

    From provider bills to workload economics: who consumed what, for which unit.

  6. 06

    Unified Operations

    State, location, ownership, health and events, as context above the clouds.

Consume capabilities, not portals

Choices without complexity.

Users select the service; Oasis Stack presents the approved destination. Consumption is then understood by estate and unit, where integration and metering data support it.

Unified service catalogue

  • GENERAL COMPUTEOasis Stack private cloud · Dubai · Standard
  • BURST COMPUTEPublic cloud · multiple regions · elastic
  • GPU COMPUTEOasis Stack AI · sovereign · dedicated
  • MANAGED AIExternal cloud · API-based · consumption

Example catalogue.

From provider bills to workload economics

Consumption by providerExample

Private cloud
AWS
Azure

The same consumption by unitExample

SAP
Digital Commerce
AI Development

Who consumed it, in which estate and unit, for which workload. Illustrative, no amounts implied.

Workload placement

Choose the right cloud for the workload.

Placement should be a decision, not a default: based on data location, performance, cost, compliance, capacity and the services a workload needs, not on platform dependency.

WorkloadRequirements
Data locationWhere must data reside?
PerformanceWhat does it require?
CostWhich consumption model?
ComplianceWhich controls apply?
CapacityWhere is it available?
ServiceSpecialised capability?

Policy-aware placement

Turn cloud placement into a governed workflow.

The request is checked against policy first; the user or the workflow then chooses between approved destinations. This is why Multi-Cloud is more than a dashboard.

Deploy application environment

Requirements

  • Region: Middle East
  • Data classification: Confidential
  • GPU: No
  • High availability: Required
  • Internet facing: Yes
Example request.

Oasis Stack policy

Data location ✓Approved providers ✓Service availability ✓Estate entitlement ✓Security controls ✓

Approved destinations

Private cloud · Dubai✓ Approved
Sovereign cloud · Riyadh✓ Approved
Public cloud · Frankfurt✕ Data-location policy

Operating patterns

Extend capacity, AI and resilience by choice.

Supported operating patterns, not automatic cloud bursting. Exact replication and recovery depend on the underlying technologies and integrations.

Extend capacity when you need it

Normal demand
Peak · private
Peak · external
Back to normal
  • Peak workloads and temporary projects
  • Development environments and geographic expansion

Keep sensitive AI close

  1. Training Unit · Oasis Stack AI, private datasets, dedicated GPUs
  2. AI Services Unit · external AI APIs
  3. Inference Unit · sovereign infrastructure, local data

Same AI estate, same context. Example.

Resilience beyond one boundary

  1. Primary · Oasis Stack private cloud
  2. Replication and protection
  3. Secondary · Oasis Stack region, partner cloud or external cloud

Recovery to a public cloud through Acronis Cloud and Commvault.

Operators and consumers

Start with the service, not the portal.

Users shouldn't begin by asking "Should I log into AWS, Azure or the private-cloud portal?" They should begin with "What service does my workload need?"

For the operatorControl the cloud landscape.
  • Connect providers and manage credentials
  • Define approved regions
  • Publish services
  • Set policies and control entitlements
  • Monitor resources
  • Track consumption

Connected landscapeExample

PrivateDubai, Riyadh
AWSApproved regions
AzureAnalytics only
Air-gappedIsolated estates
For the consumerChoose what you need.
  1. Select estate
  2. Select unit
  3. Choose service
  4. Oasis Stack shows approved options
  5. Choose location or provider, where permitted
  6. Deploy
Deploy burst compute
EstateProduction
UnitDigital Commerce
DestinationApproved options
Deploy

Private-first

Own the foundation. Extend by choice.

Many multi-cloud platforms assume public cloud is the centre. Oasis Stack starts with your infrastructure, and multi-cloud is optional: an estate can join external connectivity or stay completely isolated.

YOUR INFRASTRUCTUREThe foundation
runs
YOUR OASIS STACK CLOUDThe operating environment
extended by
OASIS MULTI-CLOUDThe extension layer
to
EXTERNAL CLOUDSAdditional capabilities
  • Private cloudOperate infrastructure you control
  • Sovereign cloudDefined jurisdiction and governance
  • Federated cloudServices across Oasis environments
  • Public cloudHyperscaler services when required
  • AI cloudSpecialised accelerated capabilities
  • Air-gapped cloudSelected estates fully disconnected

Connected across Oasis Stack

Multi-cloud is an extension of the platform.

Oasis Multi-Cloud connects external environments without breaking the Oasis Stack operating model.

Build. Run. Accelerate. Control. Multi-Cloud is where you extend.

Oasis Multi-Cloud
Oasis CoreEstates, catalogue, lifecycleCloud FoundationPrivate-cloud servicesInfrastructure for AIPrivate and external AIGovernancePolicy across boundariesDigital TransformationApplications across cloudsCloudSouqApproved external servicesFederationOther Oasis clouds

Intelligence across the platformAmin across your cloud landscape for operators; Noura for customers

Adopting this module

What connecting a cloud involves.

Each of these is agreed with you before deployment, and the walkthrough we show uses your selected services and integrations.

Talk to us
  1. Integration scopeConfirm provider APIs, supported services and the credentials the connection uses.
  2. Policy coverageDecide which clouds, regions, estates and units may use external services, and what needs approval.
  3. Provider dependenciesDocument what stays provider-specific and how the platform behaves when a connection is unavailable.

The outcome

Multiple clouds become one operating context.

  • Keep your foundationOperate private and sovereign infrastructure as the core of your cloud.
  • Extend by choiceConnect external clouds when workloads need capacity, locations or services.
  • Keep context consistentOrganisation → Estate → Unit → Resources wherever a resource runs.
  • Reduce cloud dependencyChoose infrastructure by workload while keeping your own operating model.

Oasis StackA CloudHost Initiative

Your cloud.
Extended.

Talk to us Platform overview