Authorization policies are evaluated on each request and deny by default, so a missing rule blocks access instead of granting it.
Technical reference: Policy Engine · Deny by Default

Users pick a service from the catalog. XaasIO Hyperscaler Platform coordinates identity, policy, provisioning, metering and cost reporting behind the scenes.
Console and Catalog | A familiar cloud console with a service catalog, guided create flows, resource lists and search, built with the design system behind the most widely used cloud console. Technical reference: Service Catalog · Console Home |
Accounts, Identity and Policy | Organize customers and teams into accounts and projects with roles, quotas, and policies. Integrate enterprise single sign-on. Technical reference: XaasIO IAM · SSO · RBAC · Policy Engine · Quotas |
Metering, Billing and FinOps | Record usage per account and project, then turn it into invoices for customers or showback reports for internal teams. Technical reference: Usage Metering · Rating · Invoicing · Showback |
APIs and Automation | Use the same services through the REST API, the command line and infrastructure as code, so platform teams can automate what users do in the console. Technical reference: REST API · xhpctl · OpenTofu/Terraform |
XaasIO Hyperscaler Platform is the single integrated platform for the XaasIO portfolio. Each platform keeps its own engine and lifecycle. The console, identity, catalog, metering and billing are shared, and every platform follows the same release calendar.
Platforms and modules are optional and appear in the console as they are added to a deployment. Billing and FinOps in the console are delivered by the XaasIO BSS and FinOps Platform.
Meter every resource from creation to deletion, per account and project, across compute, storage, network, Kubernetes, databases, and AI services.
Technical reference: Metering Events · Usage Records
Define prices per resource, per unit of time or per unit of usage, with flat or tiered rates and overrides for individual customers.
Technical reference: Rate Cards · Pricing Rules · Customer Overrides
Offer prepaid balances or postpaid terms with credit limits, and notify customers about low balances and new invoices.
Technical reference: Balances · Credit Limits · Notifications
Issue invoices automatically at the end of each billing cycle, with tax rules, a base currency and your own branding.
Technical reference: Invoice Runs · Tax Rules · Branded Templates
Collect through payment gateways or bank transfer, retry failed payments, send reminders, and suspend or resume services by policy.
Technical reference: Payment Gateways · Reminders · Suspension Rules
Log every charge, payment and adjustment, export to accounting systems, and drive the whole flow through the API.
Technical reference: Audit Trail · CSV and PDF Export · REST API
Billing capabilities depend on the payment gateways, tax rules and integrations selected for each deployment.
Private cloud has costs even when nobody sends an invoice. XaasIO Hyperscaler Platform allocates them, so teams see what they use and finance sees where the money goes.
Allocate costs by account, project, team, environment, and label, down to individual resources and Kubernetes workloads.
Technical reference: Usage Records · Labels · Kubernetes Cost Allocation
Set your own unit rates for CPU, GPU, memory, storage and network, so internal prices reflect your real cost of ownership.
Technical reference: Custom Pricing · Unit Rates
Publish showback reports to each team every month, or charge back to cost centers when finance requires it.
Technical reference: Showback · Chargeback · Scheduled Reports
Track month-to-date spend, top consumers and trends in the console, and export cost data to finance and BI tools.
Technical reference: Cost Dashboards · Data Expor
Showback reports cost without invoicing. Chargeback can be enabled when finance requires it.
Every request is scoped to an account and project, and isolation is enforced in the platform data layer as well as in the console.
Technical reference: Account Scoping · Row-Level Isolation
Protect sensitive platform data with keys that are separated per account and held in a key management service inside your boundary.
Technical reference: Key Management Service · Per-Account Key Namespaces
Authorization policies are evaluated on each request and deny by default, so a missing rule blocks access instead of granting it.
Technical reference: Policy Engine · Deny by Default
Services share the same API conventions and error format, so automation written for one service carries over to the next.
Technical reference: REST API · xhpctl · Unified Error Contract
Advanced capabilities depend on the platforms, identity provider and architecture selected for each deployment.
XaasIO designs, deploys, validates and supports XaasIO Hyperscaler Platform and the platforms behind it as one production service rather than an unsupported collection of portals, billing tools and scripts.
Console, identity, catalog, metering, billing and each connected platform are tested as a complete solution.
The platform follows a documented release, patching and upgrade policy, in step with the platforms it integrates.
Customer records, usage data, invoices and keys stay inside your boundary, with local repositories, identity and controlled update procedures.
Choose customer-operated, co-managed, fully managed or dedicated SRE Pod operations.
Built for cloud service providers and MSPs, enterprise private cloud, and sovereign and regulated cloud environments.
Separately scoped support for assessment, migration, integration and managed operations – available for:
Every supported XaasIO Hyperscaler Platform release includes an upstream SBOM and XaasIO release SBOM, covering components, container images, dependencies, licenses, vulnerabilities, provenance, and signed artifacts. SPDX or CycloneDX outputs support SOC 2-aligned controls and audit evidence.
Existing customers, plans and price lists are reviewed for migration
SPDX and CycloneDX outputs are available for every supported release
XaasIO Hyperscaler Platform is a cloud console, catalog, tenancy, metering, and billing layer that gives customers and internal teams a hyperscaler-style experience on infrastructure you own. It is the single integrated platform for the XaasIO portfolio, so compute, storage, Kubernetes, databases, observability, and AI services are delivered through one console.
Users sign in to a familiar console, choose services from a catalog, create resources on their own within quotas and policies, automate through APIs and infrastructure as code, and see what they consume and what it costs. The difference is that the cloud runs in your data centers, under your control.
The console is built with Cloudscape, the open-source design system, licensed under Apache 2.0, that AWS created for its own console. XaasIO Hyperscaler Platform is not an AWS product and is not affiliated with AWS. Applications use XaasIO and upstream APIs, such as OpenStack, Kubernetes and S3-compatible storage, rather than AWS service APIs.
Service providers that want to build an alternative cloud under their own brand, with multi-tenancy and automated billing, and enterprises that want a hyperscaler-style, self-service experience on-premises, with FinOps and showback instead of invoices.
The platform meters resource usage per account and project, rates it against your pricing plans, issues invoices at the end of each billing cycle and collects through payment gateways or bank transfer. Prepaid and postpaid models, credit limits, reminders and suspension rules are set by policy.
Showback reports what each team or project consumed and what it cost, without moving money. Chargeback goes one step further and charges that cost to a cost center. XaasIO Hyperscaler Platform supports showback by default and chargeback when finance requires it.
All platforms and modules in the XaasIO lifecycle framework, including XaasIO Compute, Virtualization, Kubernetes, SDS, RDS, MLT, AI Lake and AI Factory. Each one appears in the console when it is added to a deployment.
No. XaasIO platforms can run on their own, and XaasIO RDS and XaasIO MLT include the Hyperscaler console for their own service. The platform is required when several platforms are delivered through one console with shared tenancy, metering and billing.
Yes. The platform can be designed with local repositories, identity and controlled update procedures, so customer records, usage data, invoices and keys stay inside the approved security boundary.
The platform follows the XaasIO release calendar, with new series in June and December. The release record for each series identifies which capabilities are generally available and which are in preview. It can be customer-operated, co-managed, fully managed by XaasIO or run by a dedicated SRE Pod.
Planning a cloud for government, financial services, pharmaceuticals, healthcare, energy, transport, industry, service-provider operations, or private AI? Work with XaasIO to define the architecture, security boundary, and operating model your environment requires.
We use cookies and similar technologies to improve your experience on our website.