Blog
8 min read

Self-Hosted S3-Compatible Storage in 2026: MinIO, Garage, SeaweedFS, Ceph and When to Just Use R2

Self-hosted S3 compatible storage in 2026: MinIO's status, Garage, SeaweedFS, Ceph RGW and RustFS, Docker quick starts, and when hosted R2 or B2 wins.

For a new self-hosted, open source, S3-compatible store in 2026, look at Garage for small and geo-distributed setups, SeaweedFS for a single box or a larger cluster with lots of files, and Ceph RGW only if you already run Ceph or need petabyte scale. MinIO, the old default, is no longer a safe pick for new projects: its community edition became source-only in late 2025 and the GitHub repository was archived in April 2026. And for many small apps, a hosted S3-compatible service like Cloudflare R2, Backblaze B2 or Hetzner Object Storage is cheaper and less work than running your own.

If you're fuzzy on what object storage is or why the S3 API matters, start with what is object storage.

Statuses, licences and commands checked against each project's repository and docs, and prices against the providers' pricing pages, in November 2026.

The options at a glance

Licence Good for Watch out for
MinIO (community) AGPLv3 Existing installs Archived, source-only, no official images
Garage AGPLv3 Small clusters, mixed hardware, multiple sites No versioning, object lock or bucket policies
SeaweedFS Apache-2.0 One box to large clusters, many small files Many moving parts; some features in the Enterprise edition
Ceph RGW LGPL (Ceph) Large, serious storage clusters Heavy to run; overkill for one server
RustFS Apache-2.0 MinIO-style single binary with a console Young project; check maturity yourself

What happened to MinIO

MinIO was the go-to answer for "S3 in Docker" for years. A series of changes moved the free edition away from that role:

  • May 2025: MinIO stripped the admin features out of the community edition's web console, leaving a basic object browser. User, policy, bucket and configuration management moved to the command-line mc client or to MinIO's commercial product, AIStor.
  • Late 2025: MinIO stopped publishing community binaries and Docker images. The README now says the community edition "is now distributed as source code only" and that legacy binaries "will not receive updates". You build it with go install or from the Dockerfile yourself.
  • December 2025: The project went into maintenance mode.
  • April 25, 2026: GitHub shows the repository as archived and read-only, and the README says it is "no longer maintained".

The code is still AGPLv3, so it's not going to vanish, and there are community forks. MinIO's suggested path is AIStor, which has a free licence tier and a paid enterprise edition, but it's a commercial product rather than open source.

If you already run MinIO: it keeps working, but you won't get upstream fixes. Pin your version, keep it off the public internet if you can, and plan a migration. Because everything speaks S3, moving data is a rclone sync between two endpoints, and your app only needs a new endpoint URL and keys.

Garage

Garage, from the French non-profit Deuxfleurs, is designed to run on modest, mixed hardware spread across locations connected over the internet. Its site lists requirements of 1 GB of RAM, 16 GB of disk and any x86_64 CPU from the last decade or ARMv7/ARMv8, and it ships as a single dependency-free binary. In a multi-node setup it stores each piece of data in three zones.

Strengths: simple to operate, light on resources, works fine with a single node (replication_factor = 1) and grows to three sites when you want redundancy. Presigned URLs and multipart uploads are implemented, which covers most app needs. (Presigned URLs for direct uploads)

Gaps: Garage's S3 compatibility page lists no object versioning, no object lock, no bucket policies and only partial lifecycle rules (expiry and aborting incomplete uploads). Access control uses Garage's own per-key, per-bucket permissions instead of S3 ACLs and policies. If your app or backup tool requires versioning or object lock, Garage won't do.

The quick start runs a single node in Docker (current image tag dxflrs/garage:v2.5.0 at the time of writing), then you create a bucket and key with the CLI:

garage bucket create my-bucket
garage key create my-app-key
garage bucket allow --read --write --owner my-bucket --key my-app-key

SeaweedFS

SeaweedFS is a distributed storage system that started from Facebook's Haystack design: volume servers store blobs, a master tracks where they live, and a filer adds directories on top. Its S3 gateway is one of several interfaces alongside WebDAV, SFTP and FUSE. It's Apache-2.0 licensed, with a separate Enterprise edition sold at seaweedfs.com that adds features such as self-healing and customisable erasure coding.

Strengths: fast with large numbers of small files, scales from a single process to a large cluster, permissive licence, and a broad S3 surface. The weed mini command runs every component in one process, which is the easiest way to try it:

docker run -p 8333:8333 -v weed-data:/data \
  -e AWS_ACCESS_KEY_ID=admin \
  -e AWS_SECRET_ACCESS_KEY=secret \
  -e S3_BUCKET=my-bucket \
  chrislusf/seaweedfs

The S3 endpoint is then http://localhost:8333. Change those example credentials before using it for anything real.

Trade-offs: a production cluster has several components (masters, volume servers, filers, a metadata store) to understand and monitor. The docs are extensive but spread across a wiki.

Ceph RGW

Ceph is the heavyweight: a distributed storage platform that provides block, file and object storage on one cluster. The Ceph Object Gateway (RGW) is the S3 piece. Ceph's docs describe it as implementing "a large subset of the Amazon S3 RESTful API", plus a Swift-compatible API over the same data. It's deployed with cephadm or, on Kubernetes, commonly via Rook.

Choose it when you already run Ceph, or you need many nodes, many disks and serious durability with a team to run it. Don't choose it for one server and a few hundred gigabytes. Ceph's operational overhead is real, and every guide assumes multiple machines.

RustFS and others

RustFS is a newer Apache-2.0 project written in Rust that positions itself as a MinIO-style replacement, with an S3 API on port 9000 and a web console on 9001. It's moving quickly. Read its current release notes and feature table before trusting it with data you can't lose.

There are also community forks of MinIO itself that restore the console and publish packages. They may be a short-term bridge for existing users, but their long-term maintenance is unproven.

When a hosted S3-compatible service is the better call

Self-hosting storage means you own durability: disks fail, nodes need upgrades, and you need a second copy somewhere else anyway (the 3-2-1 backup rule). For many apps, a hosted service is simply the better deal:

  • Cloudflare R2: $0.015 per GB-month for Standard storage, a free tier of 10 GB-month, and no egress fees at all. Good for public files served to lots of users.
  • Backblaze B2: from $6.95 per TB per month, first 10 GB free, and free egress up to three times your stored data per month.
  • Hetzner Object Storage: a base price of €6.49 per month (excl. VAT) including 1 TB of storage and 1 TB of egress, in Falkenstein, Nuremberg and Helsinki. Handy if your servers are already at Hetzner in the EU.

(Prices from each provider's pricing page in November 2026. Check them before you budget.)

Self-host when:

  • You have local disks or servers already paid for, and lots of data that would be expensive to store elsewhere.
  • Data must stay on your hardware for legal or contractual reasons.
  • You need S3 on a private network with no internet dependency (a home lab, an air-gapped site, CI caches next to your runners).
  • You want a local S3 endpoint for development and tests. (Docker Compose for local development)

Use a hosted service when:

  • Your app stores user uploads in the gigabytes to low terabytes. (Where to store user uploads)
  • You don't want to be the person paged when a disk dies.
  • You serve files publicly and egress costs would matter.

A sensible default

  • Local dev and tests: SeaweedFS weed mini or a single-node Garage in Docker Compose.
  • Small production, self-hosted: Garage across two or three machines, or SeaweedFS if you need versioning or a fuller S3 API.
  • Big cluster with an ops team: Ceph RGW.
  • Still on MinIO: keep it running for now and plan the move.
  • Small app with no hardware of its own: a hosted provider, with your code pointing at a configurable S3 endpoint so you can switch later.

EasySpawn includes bucket storage with every server (50, 100 or 250 GB), so a small app can store uploads without running its own storage cluster. See how it works or join the waitlist.

Related: What Is Object Storage? S3, Buckets, and Where Your Files Should Live · Direct-to-Storage Uploads With Presigned URLs · The 3-2-1 Backup Rule for Apps and Databases · Docker Compose for Local Development: App, Postgres, and Redis in One Command

Keep reading