Provider APIs
Connect
Link a cloud provider through its API. Map contracts, regions and services into OpsMgr at the right level of your hierarchy.
Platform
Integrations
One control plane.Many infrastructure sources.
OpsMgr connects to provider APIs so external capacity enters the same catalogue, approval, pricing and billing path as the rest of your service. Customers see one branded console.
How integrations fit
Provider capacity in. Branded services out.
Integrations are not a separate product. They are how provider capacity enters the same catalogue, approval, pricing and billing path as the rest of your OpsMgr service.
OpsMgr catalogue
Govern
Curate what tenants can request, route approvals, apply pricing and expose everything under your brand.
OpsMgr APIs
Automate
Integrate provisioning, billing and service data into existing orchestration and service management without forcing operators into a single UI.
Strategic technology partnership
Available now
IONOS Cloud
Built on IONOS Cloud
OpsMgr sits on IONOS Cloud as the branded control plane. IONOS remains the infrastructure. Operators connect capacity, curate the catalogue, and bill under their own brand. Tenants never leave the white-label portal.
illapa and IONOS Cloud work as a strategic technology partnership. IONOS supplies the infrastructure. OpsMgr supplies multi-tenant control, pricing and billing.
Connect
- Link IONOS clouds at distributor, partner or account level
- Store and rotate API access tokens securely in the hierarchy
- Map contracts, datacentres and regions into OpsMgr
- Scope privileges per cloud and role
Compute and Kubernetes
Provision and manage virtual machines, dedicated cubes, GPU capacity, templates and Kubernetes clusters from the branded console.
- Servers, cubes and GPU instances
- Templates and service plans
- Kubernetes clusters and node pools
- Console access and lifecycle actions
Network and security
Network resources provisioned through the same approval and audit path as compute.
- LANs, firewall rules and security groups
- NAT gateways and load balancers
- IP blocks and cross-connects
- Flow logs where enabled
Storage and data services
Persistent and object storage consumed as catalogue items, not ad-hoc tickets.
- Block volumes and snapshots
- Object storage buckets and regions
- Backup units
- Restore and lifecycle from OpsMgr
Marketplace catalogue
Import, categorise and approve marketplace images for self-service deployment.
- Image import from IONOS account libraries
- Categories and display metadata
- Approved images in the tenant catalogue
- Deploy through standard request flows
Usage and billing
Provider consumption feeds the same commercial model as the rest of your OpsMgr estate.
- Usage and utilisation reporting
- Invoice and traffic data from IONOS billing APIs
- Managed Consumption Value for OpsMgr pricing
- Roll-up through distributor and partner hierarchy
Identity alignment
Optional IONOS user and group provisioning aligned to OpsMgr roles.
- Create IONOS users from OpsMgr workflows
- Group and privilege mapping
- Consistent with tenant isolation policy
What tenants experience
Tenants browse your catalogue, request create or change, and receive approvals under your brand. IONOS infrastructure sits behind that experience; operators retain margin, policy and the customer relationship.
What's next
Built for more than one provider
Additional cloud and hosting APIs will follow the same pattern: connect at the operator layer, curate what tenants can request, and route consumption through Managed Consumption Value or your Enterprise licence.
We do not publish a provider roadmap on the website. If you operate a cloud or hosting platform and want it in OpsMgr, get in touch.
Talk to us about integrating with OpsMgrSee it in your context
Walk through OpsMgr on IONOS Cloud.
Tell us which providers you operate today. We will show how they map into OpsMgr without fragmenting your customer experience.