s3-orchestrator

Storage orchestration layer presenting many cloud providers as a single S3 endpoint, keeping N copies across them with read failover, plus optional per-backend byte, request, ingress and egress limits, zstd compression and envelope encryption.

Steady · 57
57/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 18/40
Releases 25/25
Community 1/20
Momentum 13/15

Commit activity more than 45% of tracked projects; popularity more than 3%. How this is calculated.

Commits, last 11 months

2025-12: 0 commits 2026-01: 0 commits 2026-02: 0 commits 2026-03: 0 commits 2026-04: 0 commits 2026-05: 0 commits 2026-06: 0 commits 2026-07: 0 commits 2026-08: 0 commits 2026-09: 112 commits 2026-10: 144 commits
2025-12 256 total 2026-10
Stars45
Latest releasev0.178.3 · 29 Oct 2026
Repo updated18 Nov 2026
LicenceMIT
Built withGo, Docker, deb, K8S

Is s3-orchestrator actively maintained?

Over the last 11 months the project absorbed 256 commits, of which 256 arrived in the most recent quarter — roughly 85 commits a month.

The most recent tagged release, v0.178.3, shipped within the last month — a current, installable version exists today.

s3-orchestrator ranks #6 of 8 tracked file transfer - object storage & file servers projects. Several better-maintained options exist in the same category — they are listed below.

What s3-orchestrator actually does

s3-orchestrator is a storage proxy that exposes multiple cloud object storage providers behind a single S3-compatible API. It manages data redundancy by maintaining configurable numbers of copies across backends, handles read failovers, and applies optional controls such as zstd compression, envelope encryption, and usage limits.

Best fit: Systems administrators who need to aggregate disparate cloud storage services into a unified endpoint while enforcing redundancy and extra security measures like client-side encryption.

Worth knowing: The project lacks tagged releases and recorded commit activity, indicating an early stage of maturity with uncertain community support. Relying on an unrated single-maintainer proxy for critical object storage redundancy introduces significant operational risk.

Deployment notes

As a Go application packaged for Docker and Kubernetes, it typically runs as a stateless container behind a reverse proxy for TLS termination. You will need to configure environment variables or config files to point it at your underlying cloud storage backends.


s3-orchestrator as a replacement for


Alternatives to s3-orchestrator

Projects in the same categories, ordered by health score.