Distributed cloud estate
Bring infrastructure from multiple locations and providers into one operational model, without a single hardware vendor or provider stack.
One operating model.Wherever your infrastructure runs.
Deploy Commander on physical or virtual Ubuntu servers across datacentres, hosting providers, public clouds and edge locations. One consistent platform foundation, regardless of who owns the hardware.
DatacentreHosted bare metalPublic cloudPrivate cloudEdge
Commander
Distributed estate
Operational
Datacentre
Public cloud
Edge
One operating model
Same enrolment, platform services and lifecycle across every location.
Multi-provider
Consistent ops
Tenant isolation
Every site
How Commander is deployed
Different infrastructure should not mean different operations.
Commander runs on the server itself, on any supported Ubuntu host. Physical servers, virtual machines, hosted bare metal, public-cloud instances and edge nodes all enrol into the same operating model.
Host
Ubuntu (physical or virtual)
Platform
Commander
Interface
Northbound APIs
Control
OpsMgr or automation
What becomes consistent
Multi-cloud, hybrid and edge from one foundation.
Commander standardises the platform layer so operators can run distributed estates without relearning tooling at every location.
Commander standardises
- Server enrolment and inventory
- Platform configuration and lifecycle
- Kubernetes and tenant isolation
- Networking, ingress and storage
- Health visibility and automation APIs
Isolated tenant environments
Common isolation primitives across cloud, hybrid and edge deployments, with tenant and policy boundaries defined by the operator.
Repeatable platform stack
Kubernetes, networking, ingress and persistent storage through the same foundation wherever Commander is installed.
OpsMgr or your automation
Use OpsMgr as the governed human interface or integrate Commander APIs into existing service-delivery tooling.
Where Commander fits
Platform foundation, not the customer offer.
illapa supplies the repeatable technology foundation. The cloud operator applies architecture, policies, service levels and day-to-day expertise their customers need.
- illapa builds and evolves the platform capabilities.
- The operator defines the customer service and its service levels.
- Customers receive one coherent experience, not a collection of tools.
Your locations
Infrastructure
Platform
Commander
Your offer
Cloud service
Distributed estate patterns
Practical ways operators deploy Commander.
These are estate shapes we see in the field, not a fixed service catalogue. Commander gives you a consistent foundation; you define the customer offer above it.
Core plus edge
Core datacentre plus regional edge locations.
Operate central capacity and distributed sites through the same enrolment, platform services and lifecycle model.
Hybrid burst
Private infrastructure plus public-cloud burst capacity.
Keep steady-state workloads close while extending the same operating model to provider-hosted capacity when demand spikes.
Multi-hosting
Multiple hosting providers under one service model.
Standardise operations across different hosting partners instead of rebuilding tooling for each relationship.
Sovereign jurisdictions
Sovereign infrastructure in different jurisdictions.
Deploy governed platform foundations in locations chosen for data residency, compliance or national cloud programmes.
Open-source foundation
Built on open foundations.
Commander integrates proven open-source infrastructure into a coherent, operable cloud platform. You retain an open technology base; Commander provides the integration, automation and operating model around it.
- Ubuntu hosts with lightweight Kubernetes and dedicated tenant control planes
- Consistent networking, ingress and persistent storage across the estate
- Fully removable: hosts remain standard Linux servers without proprietary lock-in
A supported operating platform, not a kit of parts.
Operational control
Built by illapa.Operated by you.
A strong cloud service needs both a capable platform and an accountable operator. This division keeps product engineering, customer operations and service ownership clear.
illapa · platform capabilityCloud operator · customer operations
01
Responsibility area
Backup & disaster recovery
Platform protection capabilities, shaped into an operator-owned recovery service.
illapa · Platform provider
Commander provides replication, snapshots, backup policies and multi-site recovery capabilities, with APIs for third-party backup platforms where you already operate.
Cloud operator · Service delivery
The cloud operator defines the customer backup service: retention periods, frequency, off-site replication, recovery objectives (RPO/RTO) and restore procedures. The operator also runs, monitors and validates customer backups and disaster recovery plans.
1 of 9
Planning & adoption
Questions cloud operators ask before getting started.
From deployment fit and tenant isolation to support, migration and exit. Exact technical requirements are confirmed privately during discovery.
Platform fit questions
Platform fit
Who is Commander designed for?
Organisations that operate Ubuntu infrastructure across datacentres, hosting providers, public clouds or edge locations and want a consistent platform foundation for governed cloud services. That includes infrastructure providers, MSPs, enterprise and public-sector IT teams, and sovereign cloud operators.
Two layers
Commander is the foundation. OpsMgr is how you run the business.
Deploy a common platform across your estate, then provision, govern and bill customer services through OpsMgr.
Start with the operating model
Let's shape the right cloud foundation for your infrastructure.
Tell us where your capacity runs, who it serves and how you want to operate across locations. We'll show you where Commander fits.
Talk to the illapa team