Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OpenEBS

openebs.io

  • Free plan
  • Linux
  • API
  • Self-hosted
7.4 Club score Visit openebs.io

What OpenEBS is

OpenEBS is open-source Kubernetes storage software for developers and platform SREs running stateful workloads. It turns storage on Kubernetes worker nodes into local or distributed persistent volumes, using Replicated PV Mayastor and local Hostpath, LVM, ZFS or experimental Rawfile engines. Mayastor can synchronously replicate volumes across Kubernetes zones. Kubernetes-native operations support copy-on-write snapshots and clones, while Velero plugins provide backup and restore to AWS S3, GCP Object Storage or MinIO. Volumes expose IOPS, throughput, latency and traffic-pattern metrics for Prometheus and Grafana. OpenEBS operates in userspace rather than relying on Linux kernel-dependent software, and exposes declarative APIs through Kubernetes custom resources. It can be installed with Helm 3.2 or newer. Mayastor disk pools support data-at-rest encryption using user-defined AES-XTS keys, but each DiskPool is limited to one block device and encryption keys cannot be rotated. Stated use cases include self-managed databases, observability stacks, CI/CD, object storage, websites and ML pipelines on Kubernetes.

Who it suits

OpenEBS is aimed at developers and platform SREs deploying stateful workloads on Kubernetes. Its listed use cases include databases, observability, CI/CD and object storage.

Good to know, and what to watch

  • Supports local and distributed Kubernetes persistent volumes.
  • Mayastor can replicate volumes across Kubernetes zones.
  • Provides copy-on-write snapshots and clones.
  • Velero backup targets include AWS S3, GCP and MinIO.
  • Exposes volume metrics for Prometheus and Grafana.
  • Mayastor DiskPools support only one block device.
  • Encryption keys cannot be rotated.
  • OpenEBS kubectl plugin is available for Linux.

OpenEBS open source

Free

Free plan

Getting started

  1. Open the OpenEBS website
  2. Prepare a Kubernetes environment
  3. Install Helm 3.2 or newer
  4. Install the OpenEBS chart
  5. Use the default chart's Hostpath, LVM, ZFS, and Replicated Storage engines
  6. Use Kubernetes custom resources and kubectl operations to manage volumes

Limits to check

The OpenEBS open source plan costs nothing. Replicated PV Mayastor DiskPools are limited to a single block device, encryption keys cannot be rotated, and plaintext communication is the default; the kubectl plugin is available for Linux.

The Club's review

OpenEBS is open-source, Kubernetes-native storage for developers and platform SREs running stateful workloads. It is best suited to teams managing their own Kubernetes clusters and wanting local or replicated persistent volumes controlled through Kubernetes APIs. The main appeal is a broad engine choice at no licence cost, provided you can work within Mayastor’s current storage and encryption constraints.

Overview

OpenEBS implements the Container Native Storage pattern: Kubernetes orchestrates volume services while OpenEBS runs entirely in userspace instead of depending on Linux kernel storage software. Its declarative custom resources fit platform teams that want storage configuration and lifecycle operations managed alongside workloads.

OpenEBS started at MayaData, was donated to the Cloud Native Computing Foundation and remains a CNCF sandbox project. The project describes itself as 100% open source. Helm 3.2 or newer installs it, and the default chart includes Hostpath, LVM, ZFS and Replicated Storage.

Key features

Storage engines and replication

Version 4.6 includes Local PV Hostpath, Local PV LVM, Local PV ZFS, experimental Local PV Rawfile and Replicated PV Mayastor. Local engines are appropriate when a workload should use storage on a Kubernetes worker node. Mayastor adds synchronous volume replication across Kubernetes zones, making it the stronger choice for high availability. The range is useful for mixed clusters, but it puts the design burden on you to select and operate the right engine for each workload.

Mayastor DiskPools currently accept only a single block device. That is a material constraint for storage layouts requiring multiple devices per pool. Mayastor also supports data-at-rest encryption with user-defined AES-XTS keys, but those keys cannot currently be rotated, which is a poor fit for policies requiring regular key changes.

Kubernetes-native data operations

Copy-on-write snapshots and clones are exposed through Kubernetes-native kubectl operations, so stateful application workflows can use familiar cluster controls. Multi-attach is supported. Declarative APIs through Kubernetes custom resources make automation and GitOps-style management practical for teams already standardizing on Kubernetes objects.

Backup, monitoring and integrations

Velero plugins provide volume backup and restore to AWS S3, GCP Object Storage or MinIO. That gives teams a path to object-storage-based disaster recovery without adopting a separate OpenEBS backup system. Volumes expose IOPS, throughput, latency and traffic-pattern metrics for Prometheus and Grafana. Documented integrations include Alert Manager, ELK, Loki, Logstash, OpenShift, EKS, DigitalOcean, Rancher, MicroK8s and KubeSphere.

Security and operations

Replicated PV Mayastor supports TLS for its public REST API. JWT authentication and internal TLS are planned, while plaintext communication is the default; security-conscious operators should account for that posture before deploying it in sensitive environments. The kubectl plugin is available on Linux, even though the storage platform itself is aimed at self-managed Kubernetes environments more broadly.

Pricing

OpenEBS open source — free (Open source · Kubernetes storage). The plan includes Hostpath, LVM, ZFS, Rawfile and Replicated PV Mayastor volume types, snapshots and multi-attach. There are no paid tiers or seat quotas to weigh, making it suitable for teams that can provide their own Kubernetes operations. DataCore offers separate support services led by program managers and engineers with Certified Kubernetes Administrator and Developer qualifications; choose that route when a production deployment needs vendor assistance rather than only community software.

Platforms

OpenEBS is available through an API on Linux and as self-hosted software. Helm installation targets Kubernetes, and the Linux-only kubectl plugin matters to operators who depend on that command-line workflow.

Who it's for

OpenEBS fits platform SREs and developers running self-managed databases, observability stacks, CI/CD systems, object storage, scalable websites or machine-learning pipelines on Kubernetes. It is especially compelling when workloads need a mix of node-local and synchronously replicated volumes, Kubernetes-native snapshots and Velero-based object-storage backups.

Look elsewhere if your design requires multi-device Mayastor DiskPools, routine encryption-key rotation, or a default encrypted control path. Teams unwilling to operate storage engines inside Kubernetes may also prefer a managed or appliance-oriented product.

Pros and cons

  • Pro: Multiple local engines plus replicated Mayastor let teams match storage behavior to different stateful workloads.
  • Pro: Synchronous cross-zone replication supports high-availability volume designs.
  • Pro: Kubernetes-native snapshots, clones, custom resources and metrics integrate storage into existing cluster automation and monitoring.
  • Pro: Velero backup and restore reaches AWS S3, GCP Object Storage and MinIO.
  • Con: Mayastor DiskPools are limited to one block device, restricting some pool layouts.
  • Con: Mayastor encryption keys cannot be rotated, and plaintext communication is the default while JWT and internal TLS remain planned.
  • Con: The experimental Rawfile engine and the breadth of choices add selection and operational complexity.

Alternatives

Choose SeaweedFS instead when you want a freemium system with a free trial, broad desktop and server platform coverage, and a community-support plan for clusters of any size.

LINBIT DRBD is a better fit when Linux block replication and an optional $1,000.00-per-year Starter plan matter more than a portfolio of Kubernetes storage engines.

Pick Obstor for a free Apache 2.0, self-hosted option across API, desktop and server platforms.

Synology Photos suits a Synology NAS photo-management deployment rather than Kubernetes volume orchestration.

Choose XtreemFS when a free, BSD-licensed distributed filesystem for Linux, macOS or Windows is the priority.

Resilio Active Everywhere is for paid, endpoint-based data distribution, with pricing tied to devices or endpoints rather than data volume.

JetStream DR targets paid VM-level recovery with an on-demand monthly subscription.

SIOS Protection Suite is a paid per-server protection product priced by request.

For a wider shortlist, see Storage Replication Software and Software-Defined Storage Software.

Verdict

OpenEBS is a strong choice for Kubernetes operators who want free, open-source storage with local and cross-zone replicated volume options, native snapshots and practical Velero integration. Its userspace architecture and API-driven operation suit teams already comfortable treating storage as part of the cluster. Look elsewhere when Mayastor’s single-device pools, non-rotatable keys or default plaintext communication conflict with your storage design or security requirements.

The verdict

OpenEBS provides multiple storage engines and Kubernetes-native operations for stateful workloads. Consider the DiskPool and key-rotation limits when evaluating Mayastor encryption and storage design.

Questions people ask

Is OpenEBS free and open source?

Yes. The OpenEBS open source plan costs nothing, and the homepage describes the project as 100% open source.

Which volume types are available?

OpenEBS provides Hostpath, LVM, ZFS, Rawfile, and Replicated PV Mayastor volumes. Rawfile is listed as experimental.

How can OpenEBS back up volumes?

OpenEBS Velero plugins provide backup and restore, with AWS S3, GCP Object Storage, and MinIO as targets.

Does OpenEBS support encryption?

Mayastor disk pools support data-at-rest encryption using user-defined AES-XTS keys.

Which monitoring tools integrate with OpenEBS?

Volumes expose metrics for Prometheus and Grafana. Documented integrations also include Alert Manager, ELK, Loki, and Logstash.

How is OpenEBS installed?

It can be installed with Helm 3.2 or newer. The default chart installs Local PV Hostpath, Local PV LVM, Local PV ZFS, and Replicated Storage.

What the maker publishes

API
OpenEBS exposes declarative APIs through Kubernetes custom resources. source
Architecture
OpenEBS operates exclusively in userspace, avoiding Linux kernel-dependent software. source
Audience and use cases
OpenEBS is used for self-managed databases, observability stacks, CI/CD, object storage and scalable websites or ML pipelines on Kubernetes. source
Backup
OpenEBS backup and restore works with Velero through OpenEBS Velero plugins and can target AWS S3, GCP Object Storage, or MinIO. source
Backup integrations
OpenEBS volume backup and restore works with Velero and object-storage targets including AWS S3, GCP Object Storage and MinIO. source
Container-native storage
OpenEBS is an open-source implementation of the Container Native Storage pattern and uses Kubernetes to orchestrate volume services. source
Current limitation
Replicated PV Mayastor DiskPools are limited to a single block device and data-encryption keys cannot be rotated. source
Encryption
OpenEBS supports data-at-rest encryption for Mayastor disk pools using user-defined AES-XTS keys. source
Governance
OpenEBS was originally built by MayaData, donated to the Cloud Native Computing Foundation, and is a CNCF sandbox project. source
Installation
OpenEBS can be installed with Helm 3.2 or newer, and the default chart installs Local PV Hostpath, Local PV LVM, Local PV ZFS, and Replicated Storage. source
Installation
OpenEBS can be installed with Helm, and the default chart installs Local PV Hostpath, Local PV LVM, Local PV ZFS and Replicated Storage. source
Integrations
OpenEBS documents integrations with Prometheus, Grafana, Alert Manager, ELK, Loki, Logstash, Velero, OpenShift, EKS, DigitalOcean, Rancher, MicroK8s, and KubeSphere. source
Observability
OpenEBS volumes expose metrics such as IOPS, throughput, latency, and traffic patterns for Prometheus and Grafana monitoring. source
Observability
OpenEBS volumes expose IOPS, throughput, latency and data-pattern metrics for Prometheus and Grafana monitoring. source
Open source
The OpenEBS homepage describes the project as 100% open source. source
Platform limitation
The OpenEBS kubectl plugin is available for Linux. source
Purpose
OpenEBS helps developers and platform SREs deploy Kubernetes stateful workloads requiring fast, reliable container-native storage. source
Purpose
OpenEBS provides local or distributed persistent volumes for Kubernetes stateful workloads. source
Replication
Replicated Storage can synchronously replicate volumes across Kubernetes zones for high availability. source
Replication
Replicated Storage can synchronously replicate volumes across Kubernetes zones for high availability. source
Security
Replicated PV Mayastor supports TLS for its public REST API, while JWT authentication and internal TLS are listed as planned; plaintext communication is the default. source
Security
Replicated PV Mayastor REST API TLS is available but security features are opt-in and plaintext communication remains the default. source
Snapshots and clones
OpenEBS provides copy-on-write snapshots and clones using Kubernetes-native kubectl operations. source
Snapshots and clones
Replicated Storage supports instantaneous copy-on-write snapshots and clones managed with standard kubectl commands. source

Checked against the maker's pages on 2 Oct 2026.