Self-hosted alternatives to Amazon S3

Storage is cheap; egress is not, and that asymmetry is the entire business model.

Below are 7 open-source projects that cover the same ground, each scored 0–100 on how actively it is actually maintained — commit volume, release cadence and recent trend. 5 of the 7 are currently rated healthy or better. Ordering reflects that score, not sponsorship.

Shortest path: SeaweedFS is the best-maintained option here (health 93/100). SeaweedFS is an open source distributed file system supporting WebDAV, S3 API, FUSE mount, HDFS, etc, optimized for lots of small files, and easy to add capacity.
Project Health Activity (11 mo) Stars Licence Last release
SeaweedFS
SeaweedFS is an open source distributed file system supporting WebDAV, S3 API, FUSE mount, HDFS, etc, optimize
Thriving · 93 2025-10: 110 commits 2025-11: 134 commits 2025-12: 279 commits 2026-01: 347 commits 2026-02: 238 commits 2026-03: 303 commits 2026-04: 360 commits 2026-05: 364 commits 2026-06: 316 commits 2026-07: 245 commits 2026-08: 379 commits 35k Apache-2.0 14 Sept 2026
Harbor
Cloud native image registry that stores, signs, and scans content.
Healthy · 80 2025-10: 18 commits 2025-11: 6 commits 2025-12: 15 commits 2026-01: 45 commits 2026-02: 22 commits 2026-03: 19 commits 2026-04: 21 commits 2026-05: 29 commits 2026-06: 46 commits 2026-07: 39 commits 2026-08: 58 commits 29k Apache-2.0 24 Sept 2026
sftpgo Community Edition
Flexible, fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support.
Healthy · 76 2025-10: 20 commits 2025-11: 9 commits 2025-12: 24 commits 2026-01: 9 commits 2026-02: 13 commits 2026-03: 15 commits 2026-04: 5 commits 2026-05: 27 commits 2026-06: 30 commits 2026-07: 25 commits 2026-08: 73 commits 13k AGPL-3.0 19 Sept 2026
Zenko CloudServer
Implementation of the Amazon S3 protocol on the front-end and backend storage capabilities to multiple clouds,
Healthy · 76 2025-10: 49 commits 2025-11: 44 commits 2025-12: 83 commits 2026-01: 100 commits 2026-02: 95 commits 2026-03: 65 commits 2026-04: 82 commits 2026-05: 18 commits 2026-06: 38 commits 2026-07: 83 commits 2026-08: 77 commits 2k Apache-2.0 25 Sept 2026
ZOT OCI Registry
A production-ready vendor-neutral OCI-native container image registry.
Healthy · 74 2025-10: 33 commits 2025-11: 38 commits 2025-12: 20 commits 2026-01: 16 commits 2026-02: 21 commits 2026-03: 17 commits 2026-04: 32 commits 2026-05: 24 commits 2026-06: 25 commits 2026-07: 61 commits 2026-08: 54 commits 2.8k Apache-2.0 6 Sept 2026
Flare
A nonbloated, modern, and highly configurable file/screenshot vault server with support for ShareX, Flameshot,
At risk · 24 2025-10: 0 commits 2025-11: 0 commits 2025-12: 7 commits 2026-01: 3 commits 2026-02: 9 commits 2026-03: 15 commits 2026-04: 14 commits 2026-05: 2 commits 2026-06: 6 commits 2026-07: 7 commits 2026-08: 9 commits 137 MIT 6 Jul 2025
GarageHQ
Geo-distributed, S3‑compatible storage service that can fulfill many needs.
Unrated 2025-10: 0 commits 2025-11: 0 commits 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 — AGPL-3.0 —

How these were picked

Every project listed here is open source and can run entirely on hardware you control. We start from the categories that match Amazon S3's job — File Transfer - Object Storage & File Servers — then rank by health score so that a popular-but-abandoned project never appears above a smaller one that is actively shipping. The scoring method is documented in full.

The scores are recomputed from repository data on every rebuild, so this page reflects the state of these projects as of 1 Oct 2026 — not the day it was written.

SeaweedFS

SeaweedFS is an open source distributed file system supporting WebDAV, S3 API, FUSE mount, HDFS, etc, optimized for lots of small files, and easy to add capacity.

Best fit: Environments that need to handle millions of small files while serving them through common object storage and network file system protocols.

Worth knowing: Operating a distributed storage cluster introduces significant operational complexity regarding node management, data replication, and network partitioning.

Full health breakdown for SeaweedFS →

Harbor

Cloud native image registry that stores, signs, and scans content.

Best fit: It is well-suited for engineering teams running Kubernetes clusters who need centralised, private control over container image lifecycles and security scanning.

Worth knowing: Running a full container registry with integrated scanning and signing involves significant resource overhead and operational complexity compared to simpler storage solutions.

Full health breakdown for Harbor →

sftpgo Community Edition

Flexible, fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support.

Best fit: Self-hosters who need a dedicated, configurable file transfer endpoint with alternative protocol support for multiple users.

Worth knowing: The software is distributed under the AGPL-3.0 licence, which places copyleft requirements on network services if you modify the code and host it for others. It also carries the operational overhead of managing file access permissions and secure authentication credentials.

Full health breakdown for sftpgo Community Edition →

Zenko CloudServer

Implementation of the Amazon S3 protocol on the front-end and backend storage capabilities to multiple clouds, including Azure and Google.

Best fit: This is a suitable choice if you need a self-hosted, S3-compliant object storage endpoint for development, testing, or internal applications without relying on external cloud providers.

Worth knowing: You should consider how well it competes with more established S3-compatible alternatives like MinIO regarding performance and community resources. Scaling and maintaining object storage in production also introduces inherent operational overhead for data durability and backup.

Full health breakdown for Zenko CloudServer →

ZOT OCI Registry

A production-ready vendor-neutral OCI-native container image registry.

Best fit: It is a suitable choice if you require a dedicated OCI-compliant registry that avoids vendor lock-in for your container infrastructure.

Worth knowing: It overlaps heavily with well-established alternatives like distribution or Harbor, meaning integration documentation and community tooling may be less extensive.

Full health breakdown for ZOT OCI Registry →