Skip to Content
Public Cloud

openstack for Modern Infrastructure

OpenStack-Based Public Cloud The open-source cloud standard powering sovereign, community, and alternative public cloud providers around the world.

Reach out for openstack support
openstack
Where it Fits Where it Fits

Enterprises seeking public cloud services from providers outside the US hyperscaler ecosystem, organizations with sovereignty requirements that favor OpenStack-based national or regional cloud providers, and businesses that need API-compatible cloud infrastructure with the ability to move between compatible providers.

Strengths Strengths

OpenStack's open API standards mean workloads built for one OpenStack-based provider are largely portable to another. For enterprises concerned about hyperscaler lock-in, OpenStack-based public clouds offer a credible alternative with genuine workload portability across a global ecosystem of compatible providers.

Watchouts Watchouts

OpenStack-based public clouds vary significantly in capability, reliability, and managed service breadth depending on the provider. The OpenStack brand is not a quality guarantee. Enterprises need to evaluate individual providers on their own merits rather than treating OpenStack compliance as a sufficient selection criterion.

See Other Public Cloud Solutions
Key Concepts to Understand

Key Concepts to Understand

OpenStack is the open-source cloud infrastructure platform that underlies a significant portion of non-hyperscaler public cloud globally, including offerings from Deutsche Telekom (Open Telekom Cloud), OVHcloud's Public Cloud, Citycloud, and numerous national and regional providers. It provides the same fundamental cloud capabilities as the hyperscalers, compute, block storage, object storage, networking, and identity, through standardized APIs. For enterprises, the practical significance is API portability: tools and automation built against OpenStack APIs work across any compliant provider, reducing the re-engineering cost of changing providers or running across multiple simultaneously.

How It Works

How It Works

OpenStack public clouds expose their capabilities through standard REST APIs, including EC2-compatible endpoints on many providers that allow AWS tooling to work with minimal modification. Compute resources (Nova), networking (Neutron), block storage (Cinder), object storage (Swift), and identity (Keystone) are the core services available across most providers. Heat provides orchestration. The Horizon dashboard provides a web interface, though most enterprise usage goes through API or infrastructure-as-code tooling. Terraform's OpenStack provider supports most OpenStack clouds, making it the standard infrastructure-as-code tool for enterprises running on OpenStack-based providers.

Things You Need to Know

Things You Need to Know

The enterprise experience on OpenStack public cloud depends almost entirely on which provider is being used. A well-operated OpenStack public cloud from a major telecommunications company is a fundamentally different experience from a small regional provider running the same software. Enterprises should evaluate providers on their SLA commitments, support quality, compliance certifications, managed service availability, and operational track record rather than on OpenStack compliance alone. The platform creates the possibility of portability; the provider determines the actual quality of the experience.

Key Capabilities

What openstack Brings to the Table

API Portability Across Providers

API Portability Across Providers

Workloads built on OpenStack APIs are portable across any compliant provider, reducing lock-in and enabling multi-provider strategies without re-engineering.

Sovereign and National Cloud Access

Sovereign and National Cloud Access

OpenStack underpins numerous sovereign and national cloud offerings, providing enterprises access to compliant infrastructure from providers in their own regulatory jurisdiction.

Terraform and IaC Compatibility

Terraform and IaC Compatibility

Terraform's OpenStack provider supports most OpenStack-based clouds, enabling consistent infrastructure-as-code practices across providers and environments.

EC2-Compatible API Support

EC2-Compatible API Support

Many OpenStack public clouds offer EC2-compatible endpoints, allowing AWS tooling and automation to work against OpenStack infrastructure with minimal modification.

Assessment

Fit Check By Use Case

Strong Fit

Enterprises Requiring Sovereign or National Cloud Providers

Organizations with requirements to use cloud providers within their national regulatory jurisdiction, or from nationally owned providers, will often find the best available options are OpenStack-based. Examples: German enterprises using Open Telekom Cloud, public sector organizations with national cloud requirements, enterprises in markets where hyperscalers have no regional presence

Strong Fit

Enterprises Reducing Hyperscaler Lock-In

Organizations with a strategic objective to reduce dependency on AWS, Azure, or GCP will find OpenStack-based public clouds the most viable alternative with genuine API compatibility and a global provider ecosystem. Examples: Enterprises diversifying cloud supply chain risk, organizations with procurement policies favoring non-hyperscaler providers

Conditional Fit

Workloads Requiring Multi-Provider Portability

OpenStack's API standards enable multi-provider portability in principle, but the practical portability depends on which specific services and features are used. Workloads that stay within core OpenStack services port more easily than those using provider-specific extensions. Prerequisites: API compatibility assessment for specific workload requirements, provider feature comparison, portability testing

Conditional Fit

Enterprises Evaluating OpenStack as Primary Cloud Platform

OpenStack public cloud can serve as a primary platform for the right workload profile, but requires honest assessment of the chosen provider's managed service breadth and operational quality against enterprise requirements. Prerequisites: Provider evaluation against specific workload requirements, SLA and support assessment, compliance certification verification

Poor Fit

Enterprises Requiring Hyperscaler-Level Managed Service Breadth

No OpenStack public cloud provider currently matches the managed service depth of AWS, Azure, or GCP. Enterprises with workloads that depend on a broad range of cloud-native managed services will find OpenStack-based alternatives limiting. Examples: Enterprises dependent on managed ML platforms, advanced analytics services, or extensive cloud-native service ecosystems

Poor Fit

Enterprises Prioritizing Provider Stability and Global Support**

The OpenStack public cloud provider landscape includes providers of varying scale and stability. Enterprises that need the financial stability, global support infrastructure, and track record of a hyperscaler will find OpenStack-based alternatives a riskier choice. Examples: Enterprises with zero tolerance for provider instability, organizations requiring global 24/7 enterprise support at hyperscaler scale

Our Practice

How Crafty Penguins Works with OpenStack Public Cloud

OpenStack public cloud comes up in our enterprise work in the context of sovereignty requirements, hyperscaler diversification strategies, and occasionally in environments where a specific national or regional provider is the mandated or preferred choice. We help enterprises navigate the OpenStack provider landscape, which requires evaluating individual providers on their merits rather than treating OpenStack compliance as a sufficient selection criterion. For enterprises moving workloads to OpenStack public cloud, we help with architecture design, API compatibility assessment, and the Terraform and tooling setup that makes OpenStack environments manageable at enterprise scale. We also help enterprises design multi-provider strategies that use OpenStack's portability advantages deliberately rather than accidentally.

How Crafty Penguins Works with OpenStack Public Cloud
The Crafty Penguins Way

Our Proven Process

Practical Onboarding

We start with your real environment, versions, drivers, and recovery goals, so the plan fits production, not a slide deck.

Deep-Dive Assessment

Our engineers audit configurations, workloads, and failure modes to surface risks before they become outages.

Hands-On Implementation

We build, tune, and harden in your environment with runbooks, monitoring, and rollback plans baked in from day one.

Ongoing Optimization

Continuous monitoring, patch management, and capacity planning keep performance steady as your workloads evolve.

Questions

FAQ

What is the difference between public OpenStack cloud and private OpenStack cloud?
Private OpenStack cloud is infrastructure you deploy and operate yourself, giving you complete control but requiring significant operational expertise. Public OpenStack cloud is infrastructure operated by a third-party provider that you consume as a service, like any other public cloud. The underlying software is the same; the operational model is fundamentally different.
Which public cloud providers run OpenStack?
Prominent OpenStack-based public cloud providers include OVHcloud (Public Cloud), Deutsche Telekom's Open Telekom Cloud, Infomaniak, Citycloud, and numerous national and regional providers globally. The provider landscape varies significantly by region. The OpenStack Foundation maintains a marketplace of certified providers.
How portable are workloads between OpenStack providers?
Workloads that use core OpenStack services (Nova, Neutron, Cinder, Swift) and avoid provider-specific extensions port relatively well between compliant providers. The portability is highest for infrastructure-level resources and decreases as workloads use more provider-specific managed services or extensions. Terraform with the OpenStack provider is the most reliable way to maintain portability in practice.
How does OpenStack public cloud compliance compare to the hyperscalers?
Compliance certifications vary by provider. Major OpenStack public cloud providers hold ISO 27001, SOC 2, and in some cases sector-specific certifications relevant to their primary markets. The certification portfolio is typically more focused on the provider's regional market requirements than the hyperscalers' global portfolios. Enterprises should verify specific certifications against their workload requirements with the individual provider.
What should enterprises evaluate when choosing an OpenStack public cloud provider?
The most important evaluation criteria are operational track record and reliability, SLA commitments and remedies, compliance certifications relevant to the workload, managed service availability beyond core compute and storage, support quality and availability, financial stability of the provider, and data center location relative to sovereignty requirements. OpenStack compliance is a necessary but not sufficient criterion.
Get Started

Ready to Have Us on Your Team?

Let's discuss how we can help support, grow, and optimize your Linux infrastructure, done right the first time.