S3-orchestrator

S3-orchestrator is a self-hosted storage orchestration layer that presents multiple S3-compatible backends as a single S3 endpoint.

  • Cloud
S3-orchestrator is a self-hosted storage orchestration layer that presents multiple S3-compatible backends as a single S3 endpoint. It tracks where every object lives in its own database and enforces per-backend byte quotas, read failover, replication, drain and rebalance, and integrity scrubbing — so homelab users can consolidate free tiers and multiple clouds without rewriting their S3 clients.

Platform availability

Available on 2 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

67/100 Good

Maintained
100last commit 1 day ago
Popular
3662 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
No data
Security check
70no serious findings, 5 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
62
Open issues
62
Last commit
2026-11-20
Latest release
v0.178.3
License
MIT
Activity
steady

Checked yesterday - source: GitHub (afreidah/s3-orchestrator)

Resources & Compatibility

Requirements not published yet.

Checked yesterday - source: Docker Hub image tags and published docs

First-install notes

  • Database Tracks where every object lives in PostgreSQL or embedded SQLite — an external database is optional. source
  • Hardware planning ZimaOS sizing guide covers RAM, CPU, persistent storage, and service dependencies for different workloads. source

Fetched yesterday - each note links to its source

Alternatives (6)

Checked yesterday - source: AlternativeTo

Common questions

Do S3 applications need special configuration to use S3-orchestrator?

Applications can point directly at S3-orchestrator as the S3 endpoint. It acts as an abstraction layer, so clients do not need to know how it manages data behind the scenes.

Which database options can store object metadata?

S3-orchestrator tracks where every object lives in PostgreSQL or embedded SQLite. An external database is optional.

Can S3-orchestrator apply quotas and handle read failures?

It can keep a configurable number of copies across backends and provide read failover. It also supports optional per-backend byte, request, ingress, and egress limits.

Are encryption and compression available?

S3-orchestrator supports optional zstd compression and envelope encryption.

Answers sourced from github.com, github.com, news.ycombinator.com

Community

Collected yesterday - public community threads