Zenko CloudServer: Object Storage Ledger 2026 Scorecard

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

Snapshot

• Type: engine (open-source S3 server from Scality; not sold on its own)
• Owner: Scality (GitHub organisation scality); repository created 2016-06-01; secondary sources say ARTESCA is built on libraries such as CloudServer and that it shares code with the RING S3 interface, which no Scality document read confirms
• Licence: Apache-2.0; no commercial edition; Scality sells ARTESCA and RING separately
• Latest release: 9.4.8 (2026-10-15, year inferred from the release page); 9.5.0-preview.6, 9.3.23 and 9.2.43 the same day; 7.10.61 on 2026-10-13
• Support lifecycle: Four release lines patched in parallel (7.10, 9.2, 9.3, 9.4) with backports; no published support policy
• Next milestone: 9.5.0, in preview since at least 2026-09-28; no date
• Object lock: Handlers for bucket object lock configuration, retention and legal hold are in the 9.4 source tree; the retention handler honours the governance bypass header and refuses delete markers (objectPutRetention.js); governance and compliance behaviour not verified; none of the ten 2026 release notes read mentions Object Lock; no backup vendor validation found
• Tier: Open-source engine
• Archetype: Dependable builder, maintenance-led
• Evidence grade: C. The GitHub repository page, README, API source tree, release list, Docker Hub page and readthedocs site were read directly, so activity, licence and the 2026 release contents are primary. Capability depth rests on which handlers exist in the source tree, which says nothing about tested behaviour, and the years of all steps before 2026 are inferred (grade C). The link to ARTESCA and RING comes from secondary sources only.

Scope of the scores: CloudServer is scored as an engine on its own: a single S3 server in front of a data backend (local files, Scality sproxyd, AWS, Azure or Google). Durability and much of the scale come from that backend, not from CloudServer. The source is active, with releases into October 2026, while the readthedocs site matches branch 8.2, the README still lists Node.js 10, and the Docker Hub image was last updated about four years ago.

Scorecard

Capability by domain, 2015 to today

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

Year by year: 2016: 28.6 · 2017: 28.6 · 2018: 28.6 · 2019: 39.3 · 2020: 39.3 · 2021: 45.6 · 2022: 45.6 · 2023: 45.6 · 2024: 45.6 · 2025: 45.6 · 2026: 46.6

What moved the score

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).

• Centre of gravity: Packaging (2), S3 API (2), Lifecycle (1)
• Blind spots (no items): Immutability, Performance, Deployment, Protocols, Ecosystem, Licensing, AI
• Driver mix: Vision 0%, Customer need 75%, Market window 0%, Upstream 13%, Portfolio 13%
• Idea-to-need index: 0.00 (0 = demand-pulled, 1 = thesis-pushed)

Credibility: 15.5 / 25

Commercial risk: not scored

CloudServer is an open-source engine: Scality sells ARTESCA and RING, not CloudServer, so there are no commercial terms to score.

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

Integrator fit: 7.0 / 20

AI leverage: 2.0 / 20

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

Year by year: 2016: 2 · 2017: 2 · 2018: 2 · 2019: 2 · 2020: 2 · 2021: 2 · 2022: 2 · 2023: 2 · 2024: 2 · 2025: 2 · 2026: 2

AI say-do, 2023 to 2026: 0 AI items announced; 0 GA, 0 still preview, 0 pending, 0 dropped. The project publishes release notes only and announced no AI item from 2023 to 2026.

CloudServer has no AI features and claims none. It can serve as an S3 front end for data that other tools use, and agents can drive it only through the S3 API.

Reading

CloudServer scores as a capable S3 front end and little more: the source tree carries handlers for versioning, lifecycle, replication, notifications and object lock, while durability, scale and identity come from the backend and from Scality's proprietary Vault. Its credibility rests on cadence, with four release lines patched in parallel through October 2026, while the documentation and the Docker Hub image have not kept up. Lock-in is low because data sits in files or in the customer's own cloud buckets and leaves through S3. The one thing to check is object lock behaviour in governance and compliance mode on the release you deploy, since no test result or backup vendor validation was found.

Open questions and items to re-score

• Governance and compliance behaviour of object lock; the mode logic sits in helper code that was not read, and no test or backup vendor validation was found.
• Whether ARTESCA or RING embeds CloudServer; only a sponsored 2021 review, an analyst brief and Wikipedia say so.
• Where current container images are published; the Docker Hub image is about four years old.
• Release dates before 2026 and the years of the capability steps (grade C); the release page shows dates without a year, so 2026 is inferred.
• Contributors outside Scality and the current status of the Zenko brand.
• Whether IAM, STS and multi-tenancy are possible without Scality's proprietary Vault.

Related reading

• Object Storage Ledger 2026 overview
• Scality ARTESCA scorecard
• Scality RING scorecard
• S3-compatible storage explained