Technology

MinIO

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.

27 connections 4 resources 10 posts

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

  • CVE-2026-33322 — JWT algorithm confusion in OIDC auth. A high-severity flaw in MinIO's OIDC integration allowed JWT algorithm-confusion attacks against the auth path; patched March 2026. Per the o3.security advisory. It extends the CVE pattern this node tracks below — verify which distribution line (community vs AIStor) received the fix before relying on it.

  • MinIO named 2026 Databricks ISV Storage Partner of the Year (June 16). The commercial AIStor arm is ascending in exactly the period the community line froze — a clean data point for the OSS-pivot narrative. Per GlobeNewswire via Manila Times (wire reprint; vendor-announced award).

  • Latest community release: RELEASE.2025-10-15T17-29-55Z (October 2025) — and, notably, the last. No newer minio/minio RELEASE tag has shipped in 8 months; the community cadence effectively froze after October 2025, consistent with the post-archive / AGPL-pivot narrative this index tracks in What Survived MinIO. Per minio/minio releases.

  • MinIO AIStor joins the NVIDIA STX reference architecture as its object data store (March 16, 2026). AIStor runs natively within the BlueField-4 processor (ARM, no x86 storage nodes) to serve training, RAG, and agentic inference; GA targeted for H2 2026 with early access now. Per MinIO AIStor Brings Object Data Stores for the NVIDIA STX Reference Architecture.

  • 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.

  • Official Community Edition is now source-only, with AIStor enterprise licensing reported around $96K/year. No pre-compiled binaries or Docker images ship from the free line, consistent with the archival/AGPL-pivot narrative already tracked here; the commercial AIStor line was reported at roughly $96,000/year (tertiary source, no independent corroboration found — flagged accordingly). Per RustFS vs SeaweedFS vs Garage: Which MinIO Alternative Should You Pick?. Sources: MinIO Security Advisories index (GitHub) · CVE-2026-39414 — AIStor-only patched version (GHSA-h749-fxx7-pwpg) · MinIO repository (archived state) · pgsty/minio community fork (1,520+ stars, AGPL-3.0) · MinIO AIStor Brings Object Data Stores for the NVIDIA STX Reference Architecture (press) MinIO AIStor Brings Object Data Stores for the NVIDIA STX Reference Architecture (GlobeNewswire)

Connections 27

Outbound 8
scoped_to2
S3Object Storage
implements1
S3 API
enables1
Lakehouse Architecture
solves1
Vendor Lock-In
constrained_by2
Lack of Atomic RenameAGPL Licensing Risk
competes_with1
RustFS
Inbound 19
integrates_with2
txn2/mcp-s3ObjectCache
depends_on1
AIStor MCP Server
extends1
MinIO MemKV
alternative_to9
Technology9
pgsty/minio ForkVersity S3 GatewayGarageAlarikHS5Scality RINGOpenMaxIOCloudian HyperStoreRabata
competes_with2
pgsty/minio ForkRustFS
indexes1
LanceDB
constrained_by2
S3 Consistency Model VarianceMinIO Deletion Inconsistency
scoped_to1
MinIO Deletion Inconsistency

Resources 4

DocsHigh
min.io/docs/minio/linux/index.html

Official MinIO documentation covering deployment, configuration, and the full S3-compatible API surface.

GitHubHigh
github.com/minio/minio

The primary open-source repository for MinIO, the most widely deployed S3-compatible object store.

BlogHigh
blog.min.io/

Official MinIO engineering blog covering performance benchmarks, S3 API compatibility updates, and architecture decisions.

ChangelogHigh
github.com/minio/minio/releases

Rapid release cadence tracking every S3 feature addition and bug fix.

Featured in

2026-07-05 The Frontier Moved Again — and the Floor Compounded In June we argued the AI stack had split into a closed, expensive frontier and an open, cheap floor. Six weeks later the frontier proved the point the hard way: Claude Fable 5 was pulled offline for 19 days by an export-control order, then restored with a retention mandate that quietly bars the most sensitive data from ever touching it. Meanwhile the floor didn't just hold — it compounded. Object storage got RDMA-fast, the query engines converged on one substrate, and the data plane grew a control plane built for agents instead of humans. This is the field report. 2026-06-22 The Training I/O Tax: Storage Just Got Repriced by the GPU Three June 2026 signals — Alibaba's 30% CPFS price hike, a MinIO-vs-Dell RDMA throughput benchmark, and LanceDB's first published Enterprise latency numbers — show the same force at work: AI training I/O is repricing the storage layer. Managed parallel file storage is becoming a premium good, while commodity RDMA object storage closes the throughput gap at ~1% host CPU. The bottleneck moved, and so did the bill. 2026-06-16 The Whole Stack Went Open — Weights, Storage, and Sovereignty In the same quarter that a 1.6-trillion-parameter open-weights model landed on top of last year's closed frontier — and Anthropic's Claude Fable 5 promptly sprinted ahead again — the storage layer underneath it went open too: DeepSeek open-sourced its file system, Europe stood up sovereign S3, and the post-MinIO self-hosted stack matured. The frontier and the floor are pulling apart, and the pattern underneath all of it is the oldest pain point this index maps: vendor lock-in. 2026-05-16 When AI Memory Became an Architecture: KV-Cache Persistence, MCP, and the Night S3 Got Its Memory Tier Stateful agents needed stateful storage. Tonight 33 new nodes joined the index: Mem0, Zep, LMCache, SGLang, Mooncake, MCP, cuObject, BlueField-4, Animesis CMA. The architectural thesis: AI memory infrastructure crystallized around object storage in 2026, and the persistence layer the industry settled on is S3. 2026-05-10 When the AI Stack Became an I/O Stack: S3 Vectors GA, Real-Time Lakehouses, and the May 2026 Storage Rewrite Amazon S3 Vectors hit GA at 20 trillion vectors per bucket. Apache Paimon is doing 40 million rows per second at ByteDance. Aliyun OSS embedded similarity search directly in the storage control layer. Three independent signals, one architectural truth: 2026's AI bottleneck is no longer compute — it's I/O, and the storage layer is being rewritten to absorb it. 2026-05-08 When the Index Gained 13 Nodes: A Field Guide to the May 2026 Wave On May 7 the index added 13 new nodes — five technologies, six pain points, one architecture, one standard. Each answers a specific question engineers building on object storage are asking right now: what is China's S3 stack, why are GPUs starving, what replaced MinIO, what are the three data gravity wells, and a few more. This post walks through them by question rather than by node type, because that's how the questions actually arrive in production. 2026-05-07 When DeepSeek Made Storage Strategic: The China Direction Reshaping the S3 Ecosystem DeepSeek's $5.6M training run didn't just reset model architecture. It made object storage performance-critical, made silicon export controls a storage decision, and pushed Aliyun OSS, Tencent COS, and Huawei OBS from regional curiosities into the global S3 vocabulary. This index added 13 nodes to track what changed. 2026-05-01 What Survived MinIO: The Post-Archive S3 Server Landscape, May 2026 On April 25, 2026, MinIO archived its main GitHub repository. This index has tracked Vendor Lock-In as a first-class pain point since launch. Here is what the post-MinIO Apache-2.0 server set actually looks like — Alarik, RustFS, SeaweedFS, Garage — and what the fragmentation tells us about what we believed open-source meant. 2026-04-16 When S3 Became a File System: The April 2026 Evolution and What It Means for Local-First Builders AWS shipped S3 Files on April 7, 2026. NVIDIA productized RDMA for S3 five months earlier. Both moves validated architectural patterns the local-first ecosystem had been proving for years — and both collapse gaps that this index has been mapping since day one. 2026-03-21 The Shift to Local Intelligence: How Local S3 and Edge Inference Are Replacing Cloud Latency The economics and architecture behind the migration from cloud inference to local-first AI — covering the Local S3 semantic storage pattern, CXL memory expansion, specialized inference silicon, and why 80% of AI inference is moving to the edge.