This article is based on reporting originally published at devops.com in November 2019.
A Company Shaped by Acquisitions
For much of the Linux era, SUSE occupied a prominent position as one of the two dominant forces driving enterprise Linux adoption, sitting alongside Red Hat. What followed, however, was one of the more convoluted ownership histories in enterprise IT.
After relocating its headquarters from Germany to Oakland, California, SUSE was sold to Novell. Novell was subsequently acquired by Attachmate. Three years later, Attachmate was acquired by Micro Focus. Under Micro Focus, SUSE absorbed OpenStack distributions and the Cloud Foundry platform-as-a-service (PaaS) assets from Hewlett Packard Enterprise (HPE).
In 2018, SUSE was spun out of Micro Focus, returning to independent status and relocating its headquarters back to Germany. In 2019, Melissa Di Donato — previously Chief Operating Officer at SAP — was appointed CEO. Shortly after, SUSE announced it would discontinue its OpenStack distribution to concentrate resources on cloud-native technologies, specifically the opportunities emerging from the rapid adoption of Kubernetes.
The Cloud-Native Pivot: Kubernetes at the Core
SUSE’s strategic repositioning centered on Kubernetes deployed on its own Linux operating system. This combination served as the foundation for two key offerings:
- Container-as-a-Service (CaaS): The SUSE CaaS Platform, built directly on Kubernetes and SUSE Linux.
- Platform-as-a-Service (PaaS): A Cloud Foundry deployment running on top of Kubernetes, giving development teams a higher-level application platform.
Brent Schroeder, Global CTO at SUSE, described the strategy as a response to the increasing complexity and heterogeneity of modern IT environments. As more workloads migrate to public cloud infrastructure, organisations need a consistent substrate — one that works equally well on virtual machines, bare-metal servers, and across cloud providers.
“Virtual machines, bare-metal and the cloud will be a huge catalyst.”
Brent Schroeder, Global CTO, SUSE
Schroeder’s point reflects a broader industry reality: Kubernetes has become the de facto orchestration layer for containerised workloads, and vendors that build platforms on top of it inherit the flexibility and portability Kubernetes provides. Whether an organisation deploys on a private data centre or a hyperscaler, a Kubernetes-based foundation allows them to standardise tooling, processes, and automation.
DevOps as a Strategic Driver
Schroeder identified DevOps adoption as a primary catalyst for the transitions SUSE was positioning itself to support. Enterprises are not only asking how to build and ship software faster — they are equally concerned with how to secure and govern those pipelines at scale.
A concrete example of this focus was visible in the SUSE CaaS Platform 4 release, which added support for Cilium, an open-source project that uses eBPF (extended Berkeley Packet Filter) to enforce network security policies between containerised application services. Cilium’s inclusion reflected growing demand from enterprise teams for fine-grained, identity-aware network security within Kubernetes clusters — a requirement that mature DevSecOps practices surface quickly.
Key DevOps capabilities that SUSE’s platform strategy addressed at that time included:
- Faster application delivery: Kubernetes-native CI/CD pipelines enabled by the CaaS platform.
- Hybrid cloud portability: Consistent runtime environments across on-premises and public cloud deployments.
- Container network security: Cilium integration for policy enforcement between microservices.
- Developer self-service: PaaS capabilities via Cloud Foundry on Kubernetes, abstracting infrastructure complexity from application teams.
The Competitive Landscape: Red Hat and the CaaS/PaaS Convergence
SUSE was not alone in this strategic direction. Red Hat had been the first major vendor to build a PaaS environment on top of Kubernetes — OpenShift — and had been actively working to eliminate the distinction between CaaS and PaaS through a unified platform experience. IBM’s 2019 acquisition of Red Hat added significant resources and an enterprise sales infrastructure to the OpenShift effort, anchoring IBM’s hybrid cloud strategy on the platform.
The IBM-Red Hat acquisition, however, created a dynamic that potentially benefited SUSE. Organisations that had evaluated or adopted Red Hat OpenShift now found themselves working with an IBM-owned entity — a shift that some enterprise buyers viewed with uncertainty. For SUSE, an independent vendor with a focused Kubernetes portfolio, this created a natural opening to position itself as an alternative without the enterprise-conglomerate overhead.
What This Means for DevOps Teams
SUSE’s trajectory in 2019 illustrated a pattern that recurs throughout enterprise software: vendor consolidation in the infrastructure layer creates both risk and opportunity for engineering teams. Practically, DevOps practitioners evaluating container platforms should account for:
- Vendor independence and long-term viability: A platform tied to a single corporate parent carries different risks than one backed by an independent or widely distributed ecosystem.
- Upstream Kubernetes alignment: Platforms built closer to upstream Kubernetes reduce lock-in and ease migration between providers.
- Security posture: Built-in network policy enforcement (such as Cilium) should be a baseline expectation, not an afterthought.
- Hybrid and multi-cloud flexibility: The ability to run consistently across bare-metal, VM, and public cloud targets is increasingly a hard requirement for platform selection.
Looking Ahead
As of the time of this reporting (late 2019), SUSE’s ultimate path — whether an IPO, further acquisition, or continued independent operation — remained open. What was clear was the company’s intent to compete seriously in the cloud-native space by anchoring its portfolio on Linux, Kubernetes, and container platforms designed for enterprise DevOps workflows.
For DevOps and platform engineering teams, the broader lesson from SUSE’s journey is that the enterprise infrastructure landscape is rarely static. Evaluating platforms requires not just assessing today’s capabilities, but also understanding the corporate and ecosystem context that will determine whether a platform is maintained, evolved, or eventually discontinued.