The Post-MinIO Landscape — Self-Hosted S3 Branches Out

For nearly a decade, "self-hosted S3" meant MinIO. It was the default answer — simple, fast, single-binary, open-source. The February 2026 archival of MinIO's community repository ended that era. But the vacuum it left didn't create a crisis — it revealed a market that had been quietly specializing. RustFS targets raw performance with Apache 2.0 licensing. WarpStream proves you can build Kafka-class streaming on S3 alone. Apache Doris queries lakehouse tables on S3 at sub-second latency. Infinidat and SoftIron address enterprise and sovereign infrastructure with hardware-backed S3 compatibility. Ceph's Tentacle release made the "ops-heavy" objection weaker. The question is no longer "which MinIO replacement?" — it is "which specialized self-hosted S3 layer fits your workload?"

• Topics: S3, Object Storage
• Technologies: MinIO, RustFS, SeaweedFS, Garage, Ceph, Apache Ozone, WarpStream, Apache Doris, Infinidat, SoftIron, LanceDB, S3 Express One Zone
• Standards: S3 API, Lance Format
• Architectures: Separation of Storage and Compute, Lakehouse Architecture, Cache-Fronted Object Storage
• Pain Points: Vendor Lock-In, S3 Compatibility Drift, Cold Scan Latency

1. Map your workload archetype first:

   • General-purpose data lake: You need broad S3 API coverage, multi-tenant isolation, and proven durability. This is the traditional MinIO use case.
   • AI/ML training pipeline: You need high sequential throughput, GPU-direct data paths, and checkpoint storage. Latency matters less than bandwidth.
   • Real-time streaming: You need low-latency writes, high write throughput, and S3 as the durable tier behind a streaming platform.
   • Analytics serving: You need sub-second queries over lakehouse tables stored on S3. The storage layer must support efficient columnar reads.
   • Sovereign/defense: You need auditable supply chains, air-gapped deployment, and hardware-level trust guarantees.
   • Edge/homelab: You need minimal resource footprint, geo-distribution, and simplicity over raw performance.

2. General-purpose data lake replacements:

   • RustFS — The performance-first Apache 2.0 successor. Rust-based, no GC pauses, targeting MinIO's throughput tier. Best for teams that want the "new MinIO" with a permissive license. Trade-off: younger project, smaller community, less battle-tested at multi-petabyte scale.
   • Ceph RGW — The exabyte-proven standard. Tentacle release (v20.2.0) added FastEC for faster erasure coding, narrowing the performance gap with MinIO. Best for organizations with dedicated storage teams. Trade-off: operational complexity remains high — expect 3-6 months of tuning to reach production readiness.
   • SeaweedFS — Optimized for billions of small objects with distributed metadata. Best for content-addressable storage and workloads that hit the small files problem hard. Trade-off: single primary maintainer, thinner enterprise support.
   • Apache Ozone — The Hadoop ecosystem's native object storage. Best for organizations already running HDFS that need an S3 gateway without a forklift migration. Trade-off: tightly coupled to the Hadoop ecosystem.

3. Streaming on S3 — the WarpStream pattern:

   • WarpStream eliminates Kafka's stateful brokers entirely. All data goes straight to S3 (preferably S3 Express One Zone as the buffer tier).
   • The 2025 S3 Express 85% price reduction made this economically viable. WarpStream + Express One Zone competes on TCO with self-managed Kafka.
   • Best for: teams running Kafka that want to eliminate disk management. Not a fit for: ultra-low-latency (<5ms) use cases where local-disk Kafka still wins.

4. Analytics directly on S3 — the Doris pattern:

   • Apache Doris reads Iceberg, Hudi, and Paimon tables on S3 natively. Late 2025 added Paimon Deletion Vector support.
   • Sub-second dashboard queries without ETL into a separate serving layer. Doris queries S3 directly and caches hot data locally.
   • Best for: real-time analytics over lakehouse data. Not a replacement for the table format engine — Doris reads tables but doesn't manage compaction or snapshots.

5. Enterprise and sovereign S3:

   • Infinidat — Hardware-defined performance guarantees at petabyte scale. S3-compatible API on enterprise storage with deterministic latency SLAs. Best for: regulated industries that need on-prem S3 with contractual performance guarantees.
   • SoftIron — Ceph-based S3 on custom hardware with auditable supply-chain manufacturing. Best for: government, defense, and critical infrastructure where hardware provenance matters. Trade-off: Ceph's operational complexity is inherited.

6. Edge and lightweight:

   • Garage — Designed for geo-distributed deployment on low-end hardware. CRDT-based consistency model. 3-node clusters on Raspberry Pis. Best for: edge, homelab, and multi-site setups where you need S3 everywhere with minimal resources.

7. AI-native storage:

   • LanceDB + Lance Format — Stores vectors and data directly on S3 in a format optimized for random access (100x faster than Parquet for retrieval). Best for: embedding-heavy RAG pipelines that need vector search without a dedicated vector database.
   • AIStor (commercial MinIO) — MinIO's pivot to AI-optimized storage. GPU-direct RDMA support, training data acceleration. Best for: existing MinIO users with AI workloads who accept commercial licensing.

• 2015–2025: MinIO was the default. "Self-hosted S3" was synonymous with MinIO. Ceph was the enterprise alternative but operationally heavy. Few other options existed.
• 2021: MinIO moved to AGPL. The first governance risk signal. Most users accepted it, but enterprise legal teams started evaluating alternatives.
• 2022–2024: SeaweedFS and Garage matured. Cloudflare R2 disrupted managed S3 pricing. The landscape began diversifying, but MinIO remained dominant.
• Early 2025: S3 Express One Zone 85% price cut made S3-native architectures (like WarpStream) economically viable. The storage layer became cheap enough to build streaming directly on it.
• February 2026: MinIO community repository archived. AIStor becomes the commercial path. pgsty/minio community fork restores the open-source distribution. RustFS emerges as the performance-first Apache 2.0 alternative.
• The pattern: self-hosted S3 is no longer a single-product category. It has fragmented into specialized tiers — general-purpose (RustFS, Ceph), streaming (WarpStream), analytics (Doris), sovereign (SoftIron, Infinidat), edge (Garage), and AI-native (LanceDB, AIStor).