Rookvs
Longhorn
Longhorn: Far simpler to operate if you only need replicated block volumes and can live with the capacity overhead
Rook
Kubernetes operator that deploys and manages Ceph storage clusters
As of 1 September 2026, Rook is free to use. A graduated CNCF operator that runs Ceph inside Kubernetes, giving block, file and object storage from one cluster. Softwr lists it under Cloud. Rook is made by Cloud Native Computing Foundation, available on Linux, Kubernetes.
Overview
What Rook does
Rook is a Kubernetes operator for storage, and in practice that means Ceph. It deploys Ceph monitors, managers, object storage daemons and gateways as Kubernetes workloads, handles upgrades and failure recovery, and exposes block volumes through CSI, shared filesystems through CephFS and S3-compatible object storage through the RADOS gateway. It is a graduated project at the Cloud Native Computing Foundation, which is the highest maturity level the foundation awards. What distinguishes it is breadth. Most Kubernetes storage projects do block volumes. Rook gives you block, shared filesystem and S3 object storage from one underlying cluster, with erasure coding so capacity overhead is far lower than full replication. For an organisation that would otherwise buy separate systems for each, that consolidation is the commercial argument. The trade-off is the support and skills question, and it should be answered before adoption rather than after. Rook has no vendor. Ceph expertise is a specialist discipline, and a Ceph cluster in a degraded state does not recover itself. Commercial backing is available indirectly: IBM sells Red Hat OpenShift Data Foundation, which is Rook and Ceph packaged and supported, and several consultancies offer Ceph support contracts. Running it unsupported is viable only for teams that genuinely have or intend to build Ceph competence in house.
What people use it for
- An on-premises Kubernetes platform needing block, shared filesystem and S3 storage without buying three products
- A team that already runs Ceph and wants its lifecycle managed declaratively inside Kubernetes
- A large cluster where three-way replication overhead is unaffordable and erasure coding is required
- An organisation building a private cloud that cannot use managed cloud storage services for residency reasons
Related searches
The honest half
Where it falls short
Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about Rook.
- Rook automates Ceph but does not abstract it, so an incident still demands Ceph expertise, and organisations without it end up hiring consultants at exactly the wrong moment.
- There is no vendor and no SLA; the realistic commercial support routes are IBM Red Hat OpenShift Data Foundation or an independent Ceph consultancy, both of which change the cost picture entirely.
- Ceph is resource hungry, needing substantial memory and dedicated disks per OSD, so the hardware cost of a properly sized cluster is often underestimated.
- Recovery and rebalancing after a disk or node failure generates heavy background input and output that can degrade application performance for hours, which surprises teams sizing for steady state.
- Minimum viable clusters require several nodes with several disks each, so it is impractical at small scale and the entry hardware cost exceeds simpler alternatives.
Cross-shopped
What people choose instead of Rook
Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.
- RookvsCeph
Ceph: The underlying storage system itself, if you would rather run it outside Kubernetes
- RookvsCloudian
Cloudian: Commercial S3-compatible object storage with vendor support, when the object use case dominates
Pricing
What Rook costs
Taken from the vendor's own pricing page. Prices move, so check before you buy.
Rook
Free
- Apache 2.0 licensed, no licence fee
- Graduated CNCF project
- Community support via GitHub and Slack only
- Commercial support available indirectly via IBM Red Hat OpenShift Data Foundation or third-party Ceph consultancies
Capabilities
Features
Ceph operator
Deploys and manages Ceph monitors, managers, OSDs and gateways as Kubernetes resources
Block, file and object
RBD block volumes, CephFS shared filesystems and S3-compatible object storage from one cluster
Erasure coding
Space-efficient data protection rather than full replica copies
CSI driver
Standard Kubernetes storage interface for dynamic provisioning, snapshots and cloning
Automated upgrades
Rolling Ceph version upgrades orchestrated by the operator
Multi-cluster mirroring
RBD and CephFS mirroring between clusters for disaster recovery
Answered, with sources
Questions people ask
Each answer names the page it came from, so you can check it rather than take our word for it.
Who supports it in production?
Nobody by default. IBM sells Red Hat OpenShift Data Foundation, which is supported Rook and Ceph, and independent consultancies sell Ceph support. Decide this before deployment.
Does it need Ceph knowledge?
Yes. Rook handles deployment and routine operations, but troubleshooting a degraded cluster is a Ceph skill and there is no way around it.
Can it replace an object storage appliance?
Functionally yes, through the RADOS gateway, but you take on the operations that an appliance vendor would otherwise carry.
Keep looking
Where to go from Rook
- Rook alternativesEvery product people weigh against it
- Rook pricingPlans, floors and what the tiers exclude
- Rook badgesWhich rules it meets, and the figure behind each
- All Cloud softwareThe full category
- Best Cloud softwareThe shortlist, and how it was cut
Best Cloud software for
Compare Rook with
- OpenEBS
- Qovery
- Coolify
- Portworx
- Vultr
- Dokku
- Scaleway
- SST
- AWS (Amazon Web Services)
- Neon
- Wasabi
- Podman
- Azure Functions
- Deno Deploy
- Hetzner Cloud
- Infracost
- Lambda
- Linode
Other Cloud software
Deployment platform that provisions and operates Kubernetes inside your own cloud account
Pricing on request12 researched notesOpen source self-hosted platform that deploys applications and databases to servers you already own
Free, then $5/mo12 researched notesKubernetes-native storage and data services, priced by the node hour
From $0.33/node hour11 researched notesSingle-server platform that accepts a git push and runs Heroku buildpacks on Docker
Open source12 researched notesCloud cost estimates in pull requests, with governance in the paid tier
Free, then $250/mo12 researched notes
Softwr does not host reviews and shows no star rating for Rook, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.
More on Rook
Rook alternatives
What people switch to, and what they give up
Rook pricing
Every tier, and where the cost actually lands
Compare Rook
Put it head to head with anything we hold
Rook badge
Its rating, and an embed for your own site
Best Cloud software alternatives
Open source distributed block storage for Kubernetes, incubating at the CNCF
Open source, no licence feeDeployment platform that provisions and operates Kubernetes inside your own cloud account
quoteCloud cost estimates in pull requests, with governance in the paid tier
Free open source tool, then per month by run volume
Free self-hosted platform built on Docker Swarm with a dashboard and automatic certificates
Open source, no licence feeOpen source self-hosted platform that deploys applications and databases to servers you already own
Open source, no licence fee