Pure to Acquire Portworx |

Today marks a significant milestone in expanding our platform vision—for data to be agile, dynamic, and delivered in the cloud-like as-a-service model. I’m pleased to announce that Pure has entered into a definitive agreement to acquire Portworx, the Kubernetes Data Services Platform that enterprises trust to run mission-critical container-based applications.

Portworx is the market-leading Kubernetes Data Services Platform most used by Global 2000 companies, including Carrefour, Comcast, GE Digital, Kroger, Lufthansa, and T-Mobile.

Murli Thirumale, CEO and co-founder of Portworx, and I talk about our joint mission.

Digital businesses of tomorrow are building on the cloud-native stack. Kubernetes and containers are essential elements of this stack, and it’s time there was finally a data-services platform purpose-built for this new world. The combination of Pure and Portworx provides the most complete data-services platform for building, automating, protecting, and securing all applications—both traditional and now, cloud-native. We are focused on meeting the needs of cloud-native developers and DevOps teams how and where they run—on any cloud, any infrastructure, any storage—and supporting them at every stage of the cloud-native journey.

To the Team

I’m thrilled to welcome the Portworx team to Pure. I know our shared values of customer obsession and innovation will power the next phase of growth and customer impact that we will achieve together.

Please join us in this shared vision.

The Portworx team, led by CEO Murli Thirumale and co-founders Goutham Rao and Vinod Jayaraman, will form a new Cloud Native Business Unit inside Pure focused on driving the premier data-services experience for Kubernetes-based applications. Let me give you a window into why we’re so excited to bring Portworx into Pure, what it means for our collective customers, and where we’re going from here.

Kubernetes + Containers: The Multidimensional Shift

Containers aren’t just changing how infrastructure design, they’re changing how we write and package applications, fundamental to the application architecture itself. They’re also changing how we design for the cloud, making it possible to build applications to be hybrid and multicloud by design from the beginning.

Add onto this a parallel innovation—Kubernetes—which is rapidly becoming the de facto orchestration engine for modern cloud native applications. In fact, we believe Kubernetes will expand beyond containers to be the orchestration engine for the full stack of tomorrow’s application infrastructure.

So, if there’s a revolution on three fronts—application architecture, infrastructure design, and multicloud architecture—it seems a bit silly to think that today’s storage and data-management solutions will be capable of evolving to match the true power of containers and Kubernetes. Never has there been a better opportunity for a purpose-built solution.

Lessons Learned in Container (Storage) Evolution

We saw these trends early at Pure. We began investing years ago to build industry-leading platform support for containers and Kubernetes, first by investing in a FlexVolume driver, then through the CSI spec.

But as we dug deeper into these use cases in active use, we found that appliance-based storage wasn’t a perfect fit for many of the ways that customers wanted to use containers.

Most Kubernetes projects start small. A developer is asked to start exploring Kubernetes and containers and they do so with whatever infrastructure is available: in a lab or on some cloud instances. And before you know it, you have more containers—and complexity—than you ever imagined/predicted.
Many cloud-native applications are born and built in the cloud, and may never come on-prem. If a migration is going to happen, it’s between cloud Kubernetes services to become multicloud.
The Kubernetes religion is software-centric. For many, the first instinct is to look for a software solution that runs on bare metal infrastructure. This not only supports the agility that containers require but makes it easier to have a consistent architecture between on-prem bare metal and cloud compute/storage instances.

In all these situations, hardware-based storage solutions are either impossible to use, inconvenient to use, or just don’t align with the goals of the Kubernetes project. You want something more software-centric, cloud agile, and purpose-built for Kubernetes… or you may just not want to wait for IT to respond with infrastructure when you have to move fast.

Along this journey, we started to notice something interesting. Several of the largest Pure container customers were running a software-defined storage layer from a company called Portworx on top of Pure arrays. Companies like T-Mobile and Charter Communications were doing this at very large scale, using this architecture to deliver persistent storage to their mission-critical stateful applications. Something interesting is going on here indeed.

Enter Portworx: The Purpose-built Kubernetes Data Services Platform

I won’t attempt to tell the Portworx team’s founding story, they do it better in their companion posts. Suffice it to say that Portworx was founded to take advantage of the container transition and create the perfect purpose-built data services platform for Kubernetes. Several key design decisions that permeate the product.

100% software: This enables Portworx to deliver container data services in a consistent manner, no matter what infrastructure you choose. It also enables Portworx to scale up to the largest enterprise container deployments, scale down to the smallest 5G edge site, and support everything in between.
Simple, declarative, and Kubernetes-native: Cloud native developers simply don’t want to have to understand infrastructure. The perfect infrastructure is one that is invisible, and “just works” as an extension of Kubernetes. Define declarative storage classes and go. This was the design principle of Portworx and it’s what makes Kubernetes admins and developers love Portworx.
Infrastructure-agnostic: The whole point of Kubernetes is to package applications to be portable, so it’s key that Portworx is similarly infrastructure-agnostic. This means any cloud, any Kubernetes distribution, and any underlying storage infrastructure: in cloud or on-prem (or ideally both), virtualized, bare metal, or as-a-service.
Enterprise-class: This one is critical. As Kubernetes matures and customers evolve from stateless to stateful applications, Kubernetes and cloud native applications need to be as reliable as the traditional application infrastructure that predates them. You can’t step backward in reliability to move forward in architecture. This is a real struggle today. Enterprises want all the capabilities that they’ve been used to in traditional platforms:
- Failure protection against drives, nodes, racks, and sites
- Backup and recovery of complete applications
- Synchronous and asynchronous disaster recovery between AZs and regions
- Rich role-based access controls (RBAC) for multi-tenancy clusters
- Consistent encryption and security that goes wherever your application does

Portworx was designed to bring enterprise-class resiliency to the Kubernetes world—but in a way that didn’t destroy its benefits along the way.

The result of these efforts—now six years in—is the most mature, capable, and complete platform for delivering Kubernetes data services.

Not Just an SDS Layer—a Data Services Platform

There are several options for software-defined storage under Kubernetes. The most obvious is probably the open source tool CEPH, now also packaged as RedHat OpenShift OCS. The problem is that containerized applications need more than just software-defined persistent volumes. Persistent Kubernetes applications need a whole suite of enterprise-class data services delivered with Kubernetes agility. That’s exactly what Portworx delivers.

PX-Store: The software-defined storage layer can turn any commodity storage (SSDs, HDDs, and cloud storage) or enterprise arrays (Pure FlashArray, NetApp, EMC, etc) into reliable data services under complete control of Kubernetes. PX-Store gives everyone—developers, applications, and infrastructure teams—a consistent, policy/service-class/API view into data services.
PX-Backup: Kubernetes applications are distributed and complex. Protecting a Kubernetes-based application means not only backing up the application itself, but also all the cluster artifacts, configuration, controllers, and other metadata. PX-Backup is designed to work with PX-Store, but doesn’t require it, and can backup any native-cloud storage on AWS, Google, or Azure.
PX-Migrate: Cluster migration is a daily occurrence for Kubernetes admins whether an application is being moved between clouds, deployed into the prod cluster, or just because of cluster maintenance. PX-Migrate simplifies such migrations, enabling seamless movement of applications between heterogeneous Kubernetes clusters.
PX-Secure: As enterprises adopt hybrid-cloud and shared Kubernetes clusters, PX-Secure delivers robust, consistent encryption and rich RBACs, simplifying the ability to exert compliance and security controls on Kubernetes-based applications.
PX-Autopilot: As infrastructure itself—especially in the cloud—becomes more agile, intelligent auto-scaling has the potential to deliver dramatic efficiency gains. PX-Autopilot watches your clusters and makes smart decisions when necessary to keep your clusters available: auto-growing storage resources on a just-in-time basis, for example.

**What We Will—and More Importantly Won’t—Do**

We will:

Run Portworx as a separate product line within Pure with a heavy dose of autonomy
Increase investment in Portworx engineering to accelerate its roadmap
Continue to support heterogeneous infrastructure at every layer—including running on any cloud, bare metal, or storage-array footprint (even Pure’s competitors!)
Introduce Portworx into Pure’s global sales channel, helping expand the Portworx global footprint
Leverage Pure’s global-support organization to scale Portworx support
Continue investment in the open-source community around Kubernetes, making frequent code and architecture contributions as both Pure and Portworx have done with CSI, stork, and libopenstorage
Integrate Portworx with Pure Service Orchestrator to build the industry’s most complete Kubernetes data-services platform
Keep both companies orange—in color and culture!

We won’t:

Force Portworx customers to deploy on Pure hardware solutions. Open means open!
Sacrifice Portworx’s roadmap to invest in Pure integration. We plan to integrate where prudent, but support the Portworx plan to continue building out the data-services platform. (And we want that to go faster.)
Destroy Portworx support. Portworx customers love Portworx support and Pure is renowned for world-class support as well. We’ll make this a great joint experience.