illapa OpsMgr
The branded control plane for distributors, MSPs, and operators: catalogue, policy, approvals, and billing under your name.
Dashboard
Monitor your operations
Clouds
1
Total clouds
Datacenters
1
Total DCs
Servers
2
Total servers
Volumes
3
Total volumes
Ready to deploy?
Create a server from your catalogue with one click.
Let's DeployRecent activity
Created Datacenter
Demo · London · Sep 7 15:12
Created Cloud
DEMO · Sep 7 15:11
White-label
Partners keep the brand, the pricing, the billing, and the invoice. OpsMgr is the control plane underneath, not the name on the door.
Preview
Your logo
Sign in to your Cloud Admin Area
By clicking Login, you are agreeing to our Terms of Use.
v0.0.0
Three-level tenancy
Policy and catalogue defaults flow down. Brand, customers, and margin stay where they create value.
01 · Channel layer
A channel layer that can brand, price, and onboard partners without owning the estate.
Distributors run a branded channel without taking on infrastructure ownership. They set margin, onboard partners, and keep a separate price book from the partners below them.
Catalogue
Templates, service plans, marketplace images, compute, GPU, and Kubernetes become items in your catalogue, not one-off tickets.
Publish once, request again
Catalogue templates
Repeatable environments operators can publish once and tenants can request again.
Web stack · Ubuntu
2 vCPU · 4 GB
PublishedDev sandbox
4 vCPU · 8 GB
PublishedData pipeline
8 vCPU · 32 GB
DraftNetworking, storage, and billing follow the same catalogue model. Integrated cloud services arrive through direct provider integrations.
Governed self-service
Tenants request from your catalogue. Policy decides what runs. Every step stays visible to the operator.
Requests move through the roles you define before capacity is created.
Spend envelopes sit on the tenant, not in a spreadsheet after the fact.
Hourly and monthly figures appear before deploy, on the same request.
Who asked, who approved, and what changed remain visible to the operator.
Commercial engine
The same hierarchy that governs access also carries margin, usage, and billing, without a separate finance stack.
Commercial control
Commercial
Set cost, sell rate, and margin per SKU. Different books for distributors, partners, and end customers without exposing upstream rates.
Currency
A percentage buffer applied when converting costs into your tenant currency. Covers exchange-rate movement and conversion discrepancies without manual price adjustments.
GBP → EUR conversion
Buffer applied after FX conversion
Billing
Generate client invoices from measured usage. Each layer bills the organisation below it in the tree.
INV-1042
£4,820
INV-1041
£1,240
Visibility
See what was consumed, where, and by whom. Usage rolls up through the hierarchy for showback, chargeback, and reconciliation.
Capacity
Allocate licensed capacity down the tree instead of tracking it outside the platform.
Windows Server
42 / 100
SQL Standard
8 / 25
Support
Enter a tenant or sub-tenant view to troubleshoot without sharing passwords or losing the audit trail.
Viewing as Acme Ltd
Actions logged under your operator ID
Security and access
Security
Require a second factor for operator and tenant accounts. TOTP apps, backup codes, and enforced policies sit alongside your branded login.
Authenticator app
482 193
Access
Define who can request, approve, bill, or administer at each layer. Separation of duties without a separate identity product.
Operator admin
Tenant user
How you present it
Option A
White-label OpsMgr is the Cloud Admin Area your distributors, partners, and clients log into.
Option B
API-led orchestration for operators who want their own front door. This is not a public developer portal. It is how you instruct the same control plane from software you already run.
Two layers
OpsMgr is how people provision, govern, and bill. Commander is what makes Ubuntu you already run cloud-capable. You need both to operate a cloud. You do not need a third product.