Ænix Public Cloud Platform — for everyone who sells cloud

Open-source Cozystack (a CNCF project we create and maintain) Ænix Platform, the supported commercial distribution Aenix builds, operates and migrates it.

Aenix Public Cloud Platform is a turnkey, Kubernetes-native cloud platform for organizations that sell cloud capacity to someone else — hosting providers, MSPs and regional clouds at one end, telcos, national operators and banks running a commercial cloud at the other. It is the productized, supported distribution of Cozystack (Apache 2.0, a CNCF project created and maintained by Aenix), adding the commercial surfaces a cloud business needs: full billing back-end and front-end, WHMCS integration, a white-label customer portal, payment processing, automatic tenant lock and suspension, and service-creation wizards for VMs, Kubernetes clusters, managed databases, S3 storage and GPU workloads. It runs multi-region and multi-hypervisor, so it extends an existing VMware or OpenStack estate rather than forcing a rip-and-replace. From $1,250/month; national multi-region programmes are quoted per RFP.
Aenix Public Cloud Platform console

Quick facts

  • What it is Turnkey, supported cloud-in-a-box for anyone selling cloud — built on Cozystack, with billing, payments and a white-label portal included.
  • License Apache 2.0 core (no per-CPU / per-core licensing)
  • Status Cozystack is a CNCF project (Sandbox since 2025-02-28; Incubating expected late summer 2026)
  • Who it is for Hosting providers, MSPs, regional clouds and data centres at the small end; telcos, national operators and banks running a commercial cloud at the large end.
  • Replaces OpenStack, VMware Cloud Director, Virtuozzo, OpenNebula, Virtualizor / SolusVM-class panels, and in-house hosting panels.
  • Architecture Kubernetes-native: KubeVirt (VMs and containers on one API), Cilium (eBPF) networking, LINSTOR/DRBD replicated block storage, SeaweedFS object storage, Tenant CRD multi-tenancy, Cozystack Dashboard, VictoriaMetrics and VictoriaLogs.
  • Engagement From $1,250/month at provider scale — weeks to live via the productized installer. Multi-region operator builds are quoted per RFP: 3-6 month pilot, then 9-18 months.

A modern alternative to OpenStack for everyone who sells cloud — from a regional hoster with forty nodes to a national operator with several data centres. Turnkey cloud-in-a-box: hosting panel, billing, customer portal, payments, support. Install, plug in users, start operating.

The live demo is the actual customer frontend — Cozystack Dashboard, running in your browser on demo data. No signup, no cluster.

One platform, two ends of the same scale

A regional hoster with forty nodes and a national operator with several data centres are in the same business: you sell capacity to someone who is not you, so you need billing, a customer-facing portal, tenant isolation you can defend under audit, and payments that reconcile. That is one product, not two. The difference is how much of it is switched on.

Provider scaleNational / operator scale
WhoHosting providers, MSPs, regional clouds, data centresTelcos, national operators, banks running a commercial cloud, large public clouds
RegionsOne or a few sitesMulti-region control plane; workload placement and policy across regions
BillingWHMCS-integrated, Stripe and regional processorsFull billing back-end plus your own front-end, custom payment integrations
Existing estateMigrate off itFederate with it — one control plane over VMware, OpenNebula and OpenShift while you migrate
OnboardingProductized installer, weeks to live3-6 month pilot, then 9-18 months to full multi-region
Bought asPublished price list, from $1,250 / month per 10 nodesMulti-year programme, quoted per RFP

The technology underneath is identical, which is the point: a provider that grows into the right-hand column does not replatform. It turns on multi-region and keeps its portal, its billing and its tenants.

What’s included

Full billing — back-end and front-end

Usage metering, invoicing, payment processing. Stripe, regional payment providers and B2B invoicing. Not API hooks you finish yourself — an actual production billing surface, with multi-currency and multi-jurisdiction support at operator scale, and pre-paid balance, post-paid invoicing, channel-partner billing and reseller margin handling.

WHMCS integration

A production-ready module with billing templates for the panel you already run. Two integration modes: WHMCS as the customer-facing front, or Cozystack Dashboard as the front with WHMCS as the billing back-end. Full usage data tracked and stored behind a documented API. More on the WHMCS integration →

Hosting panel and customer portal

A branded admin dashboard for the operator, plus a customer-facing console (Cozystack Dashboard, customized to your brand) with self-service registration, profiles, team management and support ticketing.

Service-creation wizards

Guided flows for VMs, Kubernetes clusters, managed databases (PostgreSQL, MariaDB, Valkey, Kafka, ClickHouse, RabbitMQ, NATS), S3-compatible object storage and GPU workloads. No YAML required from end customers.

Tenant lock and suspension

Tenant lifecycle controls built in — automatic suspension of overdue accounts, resource blocking, lock for security review. No engineering ticket to suspend a non-paying tenant.

Multi-hypervisor control plane

One control plane that orchestrates native KubeVirt VMs and integrates with existing VMware, OpenStack, OpenNebula and OpenShift infrastructure. Storage-class compatibility with shared SAN, S3-compatible and on-premise block storage; network integration with existing fabrics over BGP, OVN and Cilium.

Multi-region

Native multi-region orchestration: workload placement, identity, network and storage policy enforced across regions. The Tenant CRD scopes naturally to a region or across several.

Service catalogue beyond VMs

Managed PostgreSQL (CloudNativePG), MariaDB, Valkey, Kafka, ClickHouse, RabbitMQ, NATS, MongoDB, OpenSearch and Qdrant; S3 storage (SeaweedFS); HTTP cache; VPN service; GPU workloads.

Migration tooling and expertise

Modules and runbooks for migration from VMware, OpenStack, Virtuozzo and OpenNebula, including Forklift-based VM migration, which ships in the Ænix platform (upstream Cozystack self-service import is still in review, so a self-run Cozystack cluster deploys Forklift alongside it). Ænix delivers migration with experience from production engagements. Migration guides →

Enterprise support

24/7 support with a named technical account manager on higher tiers. Entry tier from $1,250/month.

Why providers choose this over OpenStack

DimensionOpenStackÆnix Public Cloud Platform
Time to production6+ months typicalWeeks
Operations team size8-15+ engineers3-7 engineers
Service catalogueDIY beyond core compute / storage / networkBuilt-in: Kubernetes, databases, S3, GPU, cache, VPN
Customer-facing portalDIYCozystack Dashboard, branded, included
BillingDIY integrationWHMCS-native, Stripe and regional providers
Multi-tenancyProject model — limitedTenant CRD with quotas, RBAC and observability per tenant
Migration from VMwareHeavy liftForklift-based tooling plus Ænix delivery
Vendor supportCommunity plus add-onsÆnix enterprise support from $1,250/month
Upgrade cadenceManual, riskyGitOps-managed, low-risk

And versus the VPS control panels

Most small and mid-size providers are not running OpenStack at all. They run Virtualizor, SolusVM, Proxmox with a billing bolt-on, or a panel written in-house. Those tools do one job well: sell and provision VPS.

DimensionVirtualizor / SolusVM classÆnix Public Cloud Platform
Product catalogueVPS, and variations on VPSVMs plus managed Kubernetes, PostgreSQL, MariaDB, ClickHouse, Kafka, RabbitMQ, Valkey, S3, GPU
Where the margin isReselling capacity, competing on price per vCPUManaged services on the same hardware, priced per service
Tenancy modelAn account owning VMsTenant CRD — quotas, RBAC, network isolation, per-tenant observability and billing
Kubernetes for customersNot offered, or a separate product to operateNative, with a managed control plane per tenant
UpgradesPanel upgrade and hypervisor upgrade, both manualOne GitOps-managed platform version
Lock-inProprietary panel, per-VM licenceApache 2.0 core; you can drop the commercial layer and stay on plain Cozystack

The honest read: if VPS resale is your whole business and the margin satisfies you, a panel is cheaper and simpler — keep it. This platform pays for itself when you want to sell managed services, databases, Kubernetes and GPU without building each one yourself.

Combine it with the other platforms

The three Ænix platforms are the same engine with different surfaces switched on, so they compose rather than compete. Nothing here is a separate installation.

  • AI Platform — multi-tenant GPU scheduling, fractional GPU sharing, model serving, vector databases. Providers sell this as GPU-as-a-Service on the hardware they already have.
  • Private Cloud Platform — DORA / NIS2 architecture, customer-controlled keys, audit-ready logging. Relevant when you are a regulated entity yourself, or when you run internal workloads next to the ones you sell.

A telco selling a sovereign cloud product while running its own regulated internal estate takes both, on one platform, under one operations team.

Who buys it

BuyerTypical engagement
Hosting provider, MSP, regional cloudProductized installer, live in weeks, from the price list
Data centre adding cloud servicesMigration from VMware or Virtuozzo, then service catalogue expansion
Large public-cloud operatorNew cloud product launch or multi-region scale-up
Tier-1 bank operating a commercial cloudDORA-aligned, sovereign, multi-region
Large telco or national operatorCustomer-facing sovereign cloud product, often regional plus edge
Ready to scope your build? Book a call →

Production customers

Regional hosting providers running Ænix Platform include GoHost.kz, HDReady, Beby Cloud, HiKube, UseTech, Cloupard, Cloudsy, delivering multi-tenant cloud products across the EU, DACH, Central Asia and other regions.

Bank and telco deployments are NDA-protected until mid-2027. One commercial public cloud built on this platform is written up in detail: a Swiss provider running three data centres with synchronous cross-DC replication and GPU in production.

Engagement structure

  • Discovery call (30 minutes, free) — confirm fit
  • Platform Readiness Assessment (5-10 days, fixed price) — current-state and target architecture, migration roadmap, risk register
  • Pilot (3-6 months, operator scale) — one region, one tenant cohort, one product line
  • Full build — weeks at provider scale via the productized installer; 9-18 months for multi-region production with customer onboarding workflows and operations training
  • Managed operations (optional) — Ænix runs the control plane under SLA

Platform Readiness Assessment →

How to start

Tell us your scale, your current stack and what you sell today, and we will set up a focused call with an Ænix engineer to confirm fit.

Prefer a shorter first step? Book a discovery call instead.

Frequently asked questions

How is this different from running open-source Cozystack ourselves?

Cozystack is the engine, and it stops where the cloud business begins. Public Cloud Platform adds the operator surface: billing back-end and front-end, payment integrations, WHMCS modules, a brandable customer portal, service-creation wizards, tenant lock and suspension, a productized installer, multi-region control plane, enterprise SLA and dedicated support. Building those yourself is years of engineering, and none of it differentiates you from another provider.

How is it different from Ænix Private Cloud Platform?

Who consumes the capacity. Public Cloud Platform is for operators selling cloud to customers who are not them, so it carries billing, payments, resale and customer-facing portals. Private Cloud Platform is for organizations running cloud for their own business units, so it carries DORA / NIS2 architecture, customer-controlled keys and audit-ready logging instead. Same Cozystack foundation, same APIs — you can run both, and organizations that sell cloud and also run regulated internal workloads frequently do.

Can it coexist with our existing VMware or OpenStack estate?

Yes, and that is the normal path. The platform is multi-hypervisor: it orchestrates native KubeVirt VMs while integrating with existing VMware, OpenStack, OpenNebula and OpenShift footprints, so you consolidate one cohort at a time instead of running a big-bang migration. Ænix ships Forklift-based migration tooling in the platform and has done cohort-based VMware exits in production. Upstream Cozystack self-service VM import is still in review, so a self-run cluster deploys Forklift alongside it.

Do we need our own 24/7 operations team?

Not necessarily. Both customer-operated and Aenix-managed operating models are supported, and the hybrid one — you own the data plane, Aenix operates the control plane under SLA — is common in regulated deployments. At provider scale a typical team is three to seven engineers, against eight to fifteen for a comparable OpenStack estate.

What does the multi-region pattern look like?

Two to N+1 regions with tenant-scoped policy enforcement, customer-selectable region placement, and identity, network and storage policy federated at the platform layer. A provider that grows into multi-region does not replatform — it switches multi-region on and keeps its portal, its billing and its tenants.

Can we add GPU or developer self-service later?

Yes. AI and GPU capability and the developer self-service layer are ordinary tenant workloads on the same platform, so adding either is a configuration decision rather than a second procurement. Providers commonly start with VMs and managed databases and switch on GPU-as-a-Service once demand appears.

Ready to talk?

Book a 30-minute discovery call — no commitment. We confirm fit, the right platform, and the next steps.