Summary

What it is

An open-source, S3-compatible object storage server designed for high performance and self-hosted deployment. As of February 2026, the community repository is archived (read-only) as MinIO shifts to AIStor for commercial AI-optimized storage.

Where it fits

MinIO is the primary open-source alternative to AWS S3. It enables organizations to run the same S3 workloads on-premise, at the edge, or in any cloud — breaking vendor lock-in while keeping the S3 API contract. The 2026 archival triggered the pgsty/minio community fork, which restored the admin console and binary pipeline.

Misconceptions / Traps

MinIO implements the S3 API but is not AWS S3. Some AWS-specific features (S3 Select, S3 Inventory) may not be available or behave differently.
MinIO provides strict read-after-write consistency by default — stronger than historical AWS S3 behavior.
The February 2026 archival does not mean MinIO is dead — AIStor (Free and Enterprise tiers) continues active development. The pgsty/minio fork provides an alternative community-maintained distribution.

Key Connections

implements S3 API — full S3-compatible interface
enables Lakehouse Architecture — can serve as the storage layer
solves Vendor Lock-In — S3-compatible self-hosted alternative
constrained_by Lack of Atomic Rename — same S3 API limitation applies
LanceDB indexes MinIO — vector search over MinIO-stored data

Definition

What it is

An open-source, S3-compatible object storage server designed for high performance and self-hosted deployment. In December 2025 MinIO announced maintenance mode and pivoted toward **AIStor**, its commercial AI-optimized distribution. Withdrawal proceeded in stages — admin console removal from the OSS distribution, end of Docker Hub publishing, tightened AGPL v3 enforcement on remaining open code — and the main GitHub repository's archival timeline itself was non-monotonic: first archived **February 13, 2026**, briefly **unarchived in March** to ship a single security patch, then **re-archived read-only on April 25, 2026** as the permanent end-of-life state. The community fork **pgsty/minio** restored the admin console and binary distribution pipeline, and new development has fragmented across Apache 2.0 alternatives (**Alarik**, **RustFS**, **SeaweedFS**, **Garage**).

Why it exists

Organizations need S3-compatible storage they can run on their own infrastructure — on-premise, at the edge, or in any cloud — without depending on a single vendor.

Primary use cases

Self-hosted data lakes, on-premise lakehouse storage, CI/CD artifact storage, S3-compatible development and testing environments, AI/ML training data (via AIStor).

Recent developments

Latest signals

The OSS-vs-AIStor patch split shows up in the CVE record. Through March and April 2026 GitHub Security Advisories published five high-severity and three medium-severity advisories against MinIO with assigned CVE IDs — CVE-2026-42600 (path traversal in ReadMultiple), CVE-2026-41145 (unauthenticated object write), CVE-2026-40344 (unauthenticated write via Snowball auto-import), CVE-2026-39414 (DoS in S3 Select CSV parsing), CVE-2026-34204 (SSE metadata injection), and others. CVE-2026-39414 is the most direct evidence of the OSS/AIStor split — per the GHSA-h749-fxx7-pwpg advisory, its patched_versions list contains only MinIO AIStor RELEASE.2025-12-20T04-58-37Z. The free MinIO line does not receive the fix.
Four credible migration paths now stand. Post-archive, the migration target landscape has stabilized: RustFS (Apache 2.0, drop-in binary replacement, alpha-stage), SeaweedFS (Apache 2.0, broad Kubernetes adoption), Garage (AGPL v3, edge / homelab niche), and pgsty/minio (AGPL v3 community fork backporting the CVE patches MinIO Inc. now ships only in AIStor). For organizations that need to keep the existing data layout intact while planning a longer move, pgsty is the immediate-term answer; for clean-slate Apache 2.0 deployments, RustFS is the strongest target.