Zenko CloudServer
Zenko CloudServer, an open-source Node.js implementation of the Amazon S3 protocol on the front-end and backend storage capabilities to multiple clouds, including Azure and Google.
Zenko CloudServer is an open-source object storage project on GitHub under the Apache-2.0 license (permissive), with 2k stars. It is built with V8, CPython, Redis and Mongo. Its last push was today.
- Stars
- 2k
- License
- Apache-2.0
- Activity
- Active
- Latest release
- 9.5.2
Judgement
- What it is
- Building block
- What it does
- A Node.js server implementing the Amazon S3 API that stores data locally or passes it to Azure, Google Cloud and other backends.
- Adopt it when
- You need a local S3-compatible endpoint for development and tests, or one S3 API in front of several clouds.
- Watch out
- It is mainly a component of Scality's products, and dedicated object stores outperform it for heavy production use.
- Ready for
- Usable
- Runs as
- Self-hosted server
- Built with
- JavaScript and Node.js
- How established
- Established: started 10 years ago, latest release 9.5.2.
- What the license allows
- You can build it into a product you sell, as long as you keep its copyright notice.
Judged on 2026-11-06 from the project's README and GitHub data. The license and age lines are worked out directly.
Built from
Follow it down: Zenko CloudServer → V8 → LLVM project → runs on a microchip
Open-source alternatives to Zenko CloudServer
-
1
SeaweedFS seaweedfs
SeaweedFS is a distributed storage system for object storage (S3), file systems, Iceberg table buckets, and Lance vector buckets, designed to handle billions of files with O(1) disk access and effortless horizontal scaling.
Building block Production-ready You need self-hosted S3-compatible storage for very many small files and want one system for both object and file access.
★ 36k Apache-2.0 Go Active, pushed today
-
2
RustFS rustfs
RustFS is an open-source, S3-compatible high-performance object storage system supporting migration and coexistence with other S3-compatible platforms such as MinIO and Ceph.
Building block Usable You need self-hosted S3 storage under Apache 2.0 now that MinIO has moved away from its open-source edition.
★ 36k Apache-2.0 Rust Active, pushed today -
3
Parse Server parse-community
Parse Server for Node.js / Express
Framework or platform Production-ready You want a mature, self-hosted app backend with SDKs for many platforms, or you are migrating an old Parse app.
★ 21k Apache-2.0 JavaScript Active, pushed today -
4
JuiceFS juicedata
JuiceFS is a distributed POSIX file system built on top of Redis and S3.
Building block Production-ready You need a shared filesystem across servers or Kubernetes pods backed by cheap object storage, for example for AI training data.
★ 15k Apache-2.0 Go Active, pushed today -
5
GreptimeDB GreptimeTeam
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.
Building block Usable You want one cost-efficient store for all observability data instead of separate metric and log databases.
★ 6.8k Apache-2.0 Rust Active, pushed today -
6
Mountpoint for Amazon S3 awslabs
A simple, high-throughput file client for mounting an Amazon S3 bucket as a local file system.
Developer tool Production-ready Your data-processing or ML jobs read large files from S3 and you want filesystem access without copying the data first.
★ 5.8k Apache-2.0 Rust Active, pushed yesterday -
7
CubeFS cubefs
cloud-native distributed storage
Building block Production-ready You run large on-premise data platforms and need one shared storage layer for Hadoop, Kubernetes and S3 clients.
★ 5.7k Apache-2.0 Go Active, pushed today -
8
Garage deuxfleurs-org
(Mirror) S3-compatible object store for small self-hosted geo-distributed deployments. Main repo: https://git.deuxfleurs.fr/Deuxfleurs/garage
Building block Usable You want replicated S3 storage across a few machines in different locations, such as homelabs or small organisations, without running Ceph.
★ 4.8k AGPL-3.0 Rust Active, pushed 12 days ago
Stars, license and activity come from GitHub and refresh on a rolling hourly schedule. The project's own description is quoted as written.