S3-compatible object storage
An S3-compatible store implements a subset of Amazon's S3 API so AWS SDKs, rclone, backup software, media services, and data platforms can often use it by changing the endpoint and credentials. Compatibility varies: check the exact APIs your application needs, including policies, versioning, Object Lock, lifecycle rules, notifications, multipart uploads, encryption, replication, ACLs, and S3 Select.
Object, block, and file storage
Amazon S3 is object storage, where applications access objects by keys through APIs. Ceph also provides block storage through RADOS Block Device and a distributed filesystem through CephFS. That flexibility suits private clouds, but a full Ceph cluster can be unnecessary if an application only needs an S3 endpoint for uploads.
Distributed and decentralized storage
Garage targets geo-distributed machines and heterogeneous hardware. Ceph is suited to larger clusters in data centers and private clouds. Alarik can start smaller and scale toward distributed erasure-coded storage. Storj distributes encrypted, erasure-coded data across an external storage network rather than a cluster you operate.
MinIO Community status
MinIO was historically a widely adopted S3-compatible server, but its Community server repository is archived and no longer actively maintained. The repository remains under AGPL-3.0 while MinIO Inc. focuses commercially on AIStor. For new deployments, evaluate maintenance status alongside historical popularity and feature compatibility.
S3 servers and adjacent storage engines
MinIO, Ceph RGW, Garage, and Alarik expose S3-compatible object-storage services. Storj offers S3 access through a gateway to a decentralized hosted network. SlateDB is different: it is an embedded database engine that uses an object store as its persistence layer and does not replace S3.