Canonical OpenStack

Overview

Canonical OpenStack is an open-source platform for delivering self-service cloud infrastructure from an organization’s own data center. It is aimed at teams running private, hybrid or specialized clouds that need control of hardware and operations. The central trade-off is clear: the software license is free, while the physical infrastructure and operational expertise remain your responsibility.

Key features

Based on upstream OpenStack code, the platform provides on-demand computing through a self-service catalog, giving internal teams a public-cloud-style experience on infrastructure they control. That is a strong fit for organizations with data-residency, sovereignty or customization requirements, but it is a substantial platform rather than a lightweight developer tool.

Automation runs from bare-metal provisioning through application operations. MAAS handles physical-machine automation and Juju coordinates services across the stack, making repeatable deployments practical for dedicated infrastructure teams. The architecture uses Kubernetes, OCI images and snaps; Canonical says this decouples OpenStack from the underlying Ubuntu operating system, which can make the cloud layer easier to standardize independently.

Canonical Ceph is included by default and supports up to 128 TB of data per node. That gives a built-in storage foundation for large deployments instead of requiring a separate storage product. An expandable Kubernetes layer, integrated observability, Landscape system management and MAAS extend the core IaaS capabilities. The on-demand Kubernetes service is currently in beta, so it should not be the deciding production dependency for a risk-averse team.

Security-conscious organizations can receive up to 15 years of security maintenance for artifacts used in Canonical OpenStack. CIS and DISA-STIG hardening profiles, along with claimed conformity for telco, federal and financial-services use cases, make the platform more relevant where controls and long support horizons matter. Canonical can also design, build, test and validate a cloud, rather than leaving every deployment decision to the customer.

Pricing

The Canonical OpenStack plan costs free. There is no hidden license or subscription cost, but commercial support and consulting are separate purchases. The free plan therefore suits organizations able to operate an open-source cloud themselves and budget for hardware, deployment work and ongoing administration.

Commercial support includes 24/7 phone and ticket coverage with a stated one-hour response time for Severity 1 issues. That option is more appropriate for production environments where downtime, compliance obligations or limited in-house expertise justify a paid service relationship. The free software does not remove those operational costs.

Platforms

Canonical OpenStack is delivered through an API and web interfaces on Linux, with a self-hosted deployment model. Its hybrid cloud coverage lets organizations combine controlled in-house infrastructure with other environments while retaining their own operating model. Getting started still requires real hardware: Canonical’s learning tutorial uses one dedicated physical machine with at least four amd64 cores, 16 GiB of RAM, 100 GiB of SSD storage and Ubuntu Desktop 24.04 LTS.

Who it's for

This is a strong choice for infrastructure teams building private or hybrid clouds, sovereign or regional public-cloud services, edge infrastructure, telco NFVI, or HPC and AI/ML environments. It also fits organizations that value upstream open-source code, long security maintenance and formal hardening profiles.

It is a poor fit for a small team seeking a hosted service with no hardware administration, or for buyers who need a mature, non-beta on-demand Kubernetes offering as a core requirement. The physical-machine setup and breadth of the stack demand platform-engineering capacity.

Pros and cons

Pros

• Free open-source core: the plan has no license or subscription charge and uses upstream OpenStack code.
• Broad automation: MAAS and Juju cover provisioning through application operations.
• Integrated storage: Ceph is included by default, with support for up to 128 TB per node.
• Long-term governance: up to 15 years of security maintenance and CIS/DISA-STIG profiles support regulated deployments.
• Optional implementation help: Canonical can design, build, test and validate the cloud, with 24/7 support available.

Cons

• Hardware responsibility: deployment starts with dedicated physical capacity and Linux administration.
• Operational complexity: the full-stack scope is better suited to experienced infrastructure teams than casual adopters.
• Kubernetes beta: on-demand Kubernetes is not yet a settled production feature.
• Paid services are separate: support and consulting are not included in the free plan.

Alternatives

Cloudforet is a free, open-source self-hosted platform if you want a broader multicloud management option across Linux, macOS and Windows rather than this OpenStack-centered stack.

Pulumi is the better starting point for infrastructure-as-code workflows: its free plan supports one user, unlimited projects, stacks, environments, updates and history, plus up to 500 workflow minutes.

Terraform suits teams wanting a managed infrastructure workflow with a free tier capped at 500 managed resources and one concurrent remote run.

Cloudify offers a no-time-limit community plan, provided you can supply Docker or a VM and access to a cloud provider.

Juju is the narrower free, open-source orchestration choice when you need Canonical’s orchestration engine without adopting the complete OpenStack cloud.

Apache CloudStack is another free, open-source IaaS option for Linux, self-hosted and web deployments.

Cloud 66 is better for smaller deployment workloads: its free plan covers one server, one static site and five deployments per 24 hours.

Cycloid is a paid platform with a free SaaS tier for up to five users and one workspace, including blueprints, forms, orchestration, RBAC, SSO and MFA.

See more options in Cloud Management Software.

Verdict

Choose Canonical OpenStack if you have the people and hardware to operate a self-hosted cloud and need open-source control, deep automation, integrated Ceph storage and long security maintenance. Look elsewhere if you want a turnkey hosted service, a smaller operational footprint or production-ready on-demand Kubernetes today.