OpenShift ODF: Object Storage Ledger 2026 Scorecard

Part of the Object Storage Ledger (edition 2026-10-16). How the scores work: methodology.

Snapshot

Type: product
Owner: Red Hat, Inc. (IBM subsidiary). The ODF and Ceph development teams moved to the IBM Storage business with a 2023-01-01 target; ODF is still sold, documented and supported under the Red Hat name
Engine: Ceph RGW (Red Hat Ceph Storage build, run by the Rook operator) and NooBaa for the Multicloud Object Gateway (MCG)
Licence: Subscription: OpenShift Platform Plus, OpenShift Data Foundation Essentials or Advanced; metric and edition differences are in a subscription guide that could not be read; upstream Rook, Ceph and NooBaa are open source; no free tier
Latest release: 4.22 (GA 2026-07-09); 4.21 (2026-03-09); 4.20 (2025-11-18)
Support lifecycle: Aligned with OpenShift: 4.22 full support to 2027-02-11, maintenance to 2027-12-31, EUS to 2028-06-30; 4.21 full support ends 2026-10-09 with no EUS; EUS on even-numbered releases only
Next milestone: Server-side encryption for RGW (S3) is a developer preview in 4.22; no date published for 4.23
Object lock: RGW buckets carry Ceph Object Lock (governance and compliance in the engine); ODF pages read do not document lock modes. MCG buckets gain object lock with NooBaa 5.22.0 (2026-07-15, release list); which ODF release ships it is not confirmed. No Veeam, Commvault or Rubrik validation for ODF found
Tier: Commercial software
Archetype: Dependable builder, OpenShift-bound
Evidence grade: B. The ODF documentation index and the 4.20 and 4.22 release notes were read from docs.redhat.com. GA dates, the support lifecycle and the subscription names follow the Virtualization Storage Ledger's reading of the Red Hat lifecycle table; the lifecycle article itself did not render for this pass. Object features of the Ceph and NooBaa engines are inferred from the engine dossiers, because ODF release notes do not say which engine versions they carry. Steps for 2020 to 2022 are held at the first documented state (grade C).

Scope of the scores: ODF runs only on Red Hat OpenShift: its object service serves OpenShift clusters and the applications around them, and cannot be installed on its own. Durability and immutability are scored on the RGW path, multicloud placement and tiering on the Multicloud Object Gateway. Deployment freedom is capped by the OpenShift requirement.

Scorecard

Dimension	Score	Direction
Capability today	68.1 / 100	higher is better
Momentum since end of 2022	+11.0 points (2020 to 2022: +0.0)	higher is better
Credibility	16.0 / 25	higher is better
Commercial risk	13.5 / 25	lower is better
Technical lock-in	12.0 / 25	lower is better
Integrator fit	14.0 / 20	higher is better
AI leverage	4.0 / 20	higher is better
Ledger Index	58.2 / 100	balanced weights; see the methodology

Capability by domain, 2015 to today

Scores 0 to 5 against fixed anchors; total is weighted to 100.

Domain (weight)	2015	2019	2022	Today
S3 API fidelity (15)	n/a	n/a	3.5	4
Immutability and compliance (12)	n/a	n/a	2.5	3
Durability and resilience (12)	n/a	n/a	3.5	4.5
Performance and scale (12)	n/a	n/a	3	3.5
Deployment freedom (10)	n/a	n/a	2	2.5
Security and multi-tenancy (10)	n/a	n/a	2.5	3.5
Operations (10)	n/a	n/a	3	3.5
Protocols beyond S3 (7)	n/a	n/a	2.5	2.5
Lifecycle and tiering (7)	n/a	n/a	2.5	3
Ecosystem and openness (5)	n/a	n/a	3	3
Total / 100	n/a	n/a	57.1	68.1

Year by year: 2020: 57.1 · 2021: 57.1 · 2022: 57.1 · 2023: 58.3 · 2024: 58.3 · 2025: 61.5 · 2026: 68.1

What moved the score

Year	Domain	Change	Points	Trigger
2023	Durability and resilience	3.5 → 4	+1.2	4.14: Regional DR GA and Metro-DR for OpenShift workloads
2025	Operations	3 → 3.5	+1.0	4.18: faster upgrades and the MCG object browser; 4.20 folds mcg-cli into odf-cli and adds bucket-level replication metrics; no fleet manager of its own
2025	Performance and scale	3 → 3.5	+1.2	4.18 and 4.19: multiple device classes and automatic storage scaling for dynamic devices; no S3 over RDMA and no independent benchmark found
2025	Security and multi-tenancy	2.5 → 3	+1.0	4.18: KMS key rotation and in-transit encryption after deployment; 4.20 (2025-11-18): automated key rotation
2026	Deployment freedom	2 → 2.5	+1.0	4.21 (2026-03-09): Arm GA; 4.22: Two Nodes Fencing support; still requires OpenShift
2026	Durability and resilience	4 → 4.5	+1.2	4.22 (2026-07-09): erasure coding in internal mode GA for RGW after a developer preview from 4.16; Regional DR for erasure-coded pools
2026	Immutability and compliance	2.5 → 3	+1.2	NooBaa 5.22.0 (2026-07-15) adds object lock to the MCG engine, ODF release not confirmed (half step); no Cohasset assessment or backup vendor validation for ODF found
2026	Lifecycle and tiering	2.5 → 3	+0.7	NooBaa 5.20 and 5.21 add noncurrent-version lifecycle rules and Glacier parallel recall to the MCG engine, ODF release not confirmed; OBC bucket quotas in 4.22
2026	S3 API fidelity	3.5 → 4	+1.5	4.22 (2026-07-09): RGW STS through the CephObjectStore resource, OBC bucket quotas and S3 Vectors; no published S3 compatibility matrix for ODF found
2026	Security and multi-tenancy	3 → 3.5	+1.0	4.22 (2026-07-09): RGW STS through CephObjectStore and OBC bucket quotas; RGW server-side encryption still a developer preview; whether the 2026-08-19 CephX fixes reached a 4.2x z-stream is not confirmed

Direction, 2023 to 2026

Each release item carries one theme and one driver (V vision, C customer need, M market window, U upstream, P portfolio).

Date	Item	Theme	Driver
2023-01	ODF development moves to IBM Storage; product stays Red Hat branded	Packaging	P
2023-11	4.14: Regional DR GA; Metro-DR on IBM Z and Power; Multus GA	Durability	C
2024-07	4.16: RGW erasure coding in internal mode as a developer preview	Durability	C
2024-07	4.16: weekly cluster-wide key rotation	Security	C
2025-03	4.18: faster upgrades, MCG object browser, KMS key rotation	Operations	C
2025-07	4.19: multiple device classes and automatic storage scaling	Performance	C
2025-11	4.20: automated key rotation, MCG object browser public access limit, Multus with IPv6	Security	C
2025-11	4.20: mcg-cli folded into odf-cli; bucket-level replication metrics for MCG	Operations	C
2025-11	4.20: Arm as a technology preview	Deployment	V
2026-03	4.21: Arm GA, Health Overview and scoring	Deployment	C
2026-03	4.21: OpenShift Lightspeed knowledge integration through BYOK (technology preview)	AI	V
2026-07	4.22: erasure coding in internal mode GA for RGW, RBD and CephFS	Durability	C
2026-07	4.22: RGW STS through CephObjectStore, OBC bucket quotas, MCG replication target alert	S3 API	C
2026-07	4.22: S3 Vectors support	AI	V
2026-07	4.22: server-side encryption for RGW as a developer preview	Security	C
2026-07	4.22: Two Nodes Fencing support	Deployment	C
2026-10	Subscription guide revised (PDF dated 2026-10-06); content not readable	Licensing	P

Centre of gravity: Durability (3), Security (3), Deployment (3)
Blind spots (no items): Immutability, Protocols, Lifecycle, Ecosystem
Driver mix: Vision 18%, Customer need 71%, Market window 0%, Upstream 0%, Portfolio 12%
Idea-to-need index: 0.20 (0 = demand-pulled, 1 = thesis-pushed)

Credibility: 16.0 / 25

Criterion	Score	Basis
Cadence	4.5	Three releases a year aligned to OpenShift minors, each with a published lifecycle row: 4.18 (2025-03-11), 4.19 (2025-07-28), 4.20 (2025-11-18), 4.21 (2026-03-09), 4.22 (2026-07-09)
Roadmap transparency	2.5	Release notes label technology and developer previews; no public roadmap; lifecycle and subscription detail behind a login or a PDF
Say-do	3.5	Most previews checked reached feature status within four to eight months; RGW erasure coding took about 24 months from 4.16 to 4.22
Velocity	3	Object items are few per release: erasure coding for RGW in 4.22, STS and OBC quotas, S3 Vectors; most release items are DR, security and operations
Lifecycle stability	2.5	About seven months of full support on odd releases (4.21 ends 2026-10-09), EUS on even releases only, upgrades set by the OpenShift calendar

Commercial risk: 13.5 / 25 (lower is better)

Criterion	Score	Basis
Price and licence volatility	2.5	No public price; the product page and the lifecycle page disagree on whether stand-alone editions exist; the subscription guide was revised on 2026-10-06 with unknown content
Purchase constraints	3.5	Requires an OpenShift subscription; sold in Platform Plus or the Essentials and Advanced editions; no free edition
Channel and access	2.5	Red Hat direct and partners; images and patches need a subscription
Owner stability	2	IBM-owned vendor; development moved to IBM Storage in 2023 while the brand stayed with Red Hat
Cost of staying supported	3	Three upgrades a year to stay in full support, or EUS on even releases at extra cost

Technical lock-in: 12.0 / 25 (lower is better)

Criterion	Score	Basis
Formats	2.5	RGW objects striped into RADOS; MCG data in backing stores managed by NooBaa
Export path	1	S3 reads from RGW and MCG; MCG namespace buckets keep data in the cloud or file backend
Stack coupling	4	OpenShift required; external mode requires a Red Hat Ceph Storage cluster
Hardware / cloud coupling	1.5	Bare metal, vSphere, public clouds, Power, Z and Arm, always under OpenShift
Skills and tooling coupling	3	OpenShift plus Ceph skills; odf-cli and operator CRDs

Integrator fit: 14.0 / 20

Criterion	Score	Basis
Partner programme openness	3	Red Hat Partner Connect; terms not read for this edition
Multi-tenancy and self-service	3.5	Object bucket claims give OpenShift projects self-service buckets; OBC quotas since 4.22; no storage-level metering
API and infrastructure-as-code	4	Everything is a Kubernetes CRD (StorageCluster, CephObjectStore, ObjectBucketClaim), GitOps-ready
Skills and certification	3.5	Red Hat training and exams cover OpenShift storage; the current course list was not verified

AI leverage: 4.0 / 20

How the product uses AI, scored per year like capability. Only GA counts.

Criterion	2019	2022	Today	Latest step
AI workload support	n/a	1	1.5	2026: 4.22 (2026-07-09): S3 Vectors support
AI platform stack	n/a	0	0	2020: None
AI-assisted operations	n/a	0	0.5	2026: 4.21: OpenShift Lightspeed knowledge integration through BYOK, technology preview
Agent openness	n/a	2	2	2020: Kubernetes API and CRDs that agents can drive with standard tooling; no MCP server found

Year by year: 2020: 3 · 2021: 3 · 2022: 3 · 2023: 3 · 2024: 3 · 2025: 3 · 2026: 4

AI say-do, 2023 to 2026: 2 AI items announced; 1 GA, 1 still preview, 0 pending, 0 dropped. S3 Vectors shipped as a feature in 4.22; the Lightspeed integration has been a technology preview since 4.21.

ODF's AI so far is S3 Vectors on the object gateway and a preview link to OpenShift Lightspeed; neither changes how the storage is run. Agents reach it through the Kubernetes API like any operator.

Reading

ODF scores as Ceph RGW minus the freedom: the same engine gives it erasure coding, Regional and Metro DR and Object Lock on RGW buckets, but only inside OpenShift and on the OpenShift calendar. Immutability sits at 3 because ODF documents no lock modes, the gateway's object lock arrived only with NooBaa 5.22.0 in July 2026, and no backup vendor validation was found. S3 server-side encryption for RGW is still a developer preview in 4.22, which holds security at 3.5. Before using it as a backup target, ask Red Hat which ODF release carries NooBaa 5.22, which Object Lock modes are supported on each path, and read the subscription guide, because Red Hat's own pages disagree on whether stand-alone editions exist.

Open questions and items to re-score

Which ODF release carries NooBaa 5.22.0 and its object lock, and which Ceph release sits inside each ODF version.
Object Lock modes and legal hold as documented for ODF; backup vendor validation (Veeam, Commvault, Kasten, Rubrik).
Edition differences and the price metric are in a subscription guide PDF (revised 2026-10-06) that could not be read.
Whether the 2026-08-19 CephX fixes have shipped in an ODF z-stream.
Whether ODF exposes the RGW Swift API or NFS to clients outside the cluster.
Release notes for 4.10 to 4.13, 4.15 and 4.17 were not read; the 2020 to 2022 steps are held at the first documented state.