MinIO

High-performance S3-compatible object storage for any cloud

3.6(0 reviews)freemiumFounded 2014United States

free tieropen sourceself hostables3 compatibleapi access

Integrates with

AWS Kubernetes Terraform Redis S3-Compatible Storage NVMe SSD

MinIO is a high-performance, S3-compatible object storage you deploy on your own infrastructure. Single binary, Kubernetes-native, and handles enterprise workloads. Used in ML pipelines and data lakes

What MinIO actually is

MinIO is the S3-compatible object store that became the default answer to "I need object storage inside my own datacenter." Founded in 2014 by Garima Kapoor, Anand Babu "AB" Periasamy, and Harshavardhana and based in Redwood City, California, MinIO, Inc. built a single-binary Go server that speaks the S3 API convincingly enough that AWS SDKs, Terraform providers, backup tools, and data platforms run against it unchanged. Erasure coding, bitrot protection, distributed multi-node operation, server-side encryption, lifecycle rules, and replication are all in the box. For the better part of a decade it has been the reference private cloud object store for AI/ML pipelines, analytics lakes, and anyone who wanted S3 semantics without an AWS bill.

Two things about MinIO need to be stated plainly in 2026, because they change the buying decision. First, the licensing: the project moved from Apache 2.0 to GNU AGPL v3 in 2021, which is network copyleft — if you offer a service built around it, the AGPL reaches your code. That caused several vendors to remove it from their stacks. Second, the open-source edition is finished. MinIO's own pricing page now says the AGPL edition is "no longer maintained," with a frozen codebase and no new features, bug fixes, or security patches. The web console lost its administrative features in May 2025 (users and policy management moved to the mc command line), community binaries stopped shipping after the October 2025 releases, and the GitHub repository has been reported archived read-only. What you can still get for free is AIStor Free — a proprietary-licensed, full-featured, single-node build — and the commercial AIStor tiers above it.

We list MinIO in our object storage category because the engineering is genuinely excellent and the deployment footprint is enormous. But the story of this product is now a story about a commercial company managing an open-source funnel, and buyers should price that policy risk alongside the hardware.

Pricing: what you really pay

The free paths are real. AIStor Free costs nothing: the complete feature set on a single node, as many drives as the machine holds, erasure coding and bitrot protection included, community Slack support. It cannot be redistributed or resold, and it does not do distributed high-availability — for a homelab, a backup target, a CI artifact store, or a single-node production workload that can tolerate a node outage, it is the best free object store you can run.

Above that, pricing is quote-only. AIStor Enterprise Lite covers distributed, highly available deployments below 400 TiB with an optional support add-on at a sub-five-day SLA. AIStor Enterprise is the unlimited-scale tier with 24/7/365 direct-to-engineer support, a sub-four-hour SLA, and a "Panic Button." The company does not publish these prices; the figures in circulation come from MinIO's own site as quoted by third parties — competitor Cloudian's CMO told Blocks & Files the software and support cost "a minimum of $96,000 per year, rising to $244,032 per year for 1 PB of usable capacity," and trade press has reported the enterprise license starting at $96,000 annually for up to 400TB usable. Treat those as reported, not confirmed: we could not verify current list pricing from a public MinIO page, and enterprise quotes vary.

The comparison that matters: one year of that reported enterprise floor buys several very large benchmark-tier storage servers outright. MinIO's answer is that the subscription covers the engineering, the certifications (FIPS 140-3, SOC 2, ISO 27001, SEC 17a-4(f), FINRA), and the support SLA — which is a fair argument for a bank and a hard sell for a startup. Our practical guidance: build on AIStor Free or the frozen AGPL code if you can operate it alone, and enter enterprise negotiations knowing the public floor figures above.

Performance & infrastructure

MinIO the software is fast. It is written to extract parallel throughput from NVMe and spinning disks alike, and its own marketing claims terabytes-per-second scale — claims we have not independently benchmarked, so we point you instead to the storage results in our benchmarks methodology and to the very large production deployments in ML and analytics that speak for themselves. What we can say from the architecture: single binary, no external dependencies, runs on Linux, macOS, Windows, Kubernetes (via its operator), bare metal, and edge devices; distributed mode spreads objects and parity across nodes with erasure coding that survives drive and node loss; bitrot detection hashes data at rest.

Because it is self-hosted, there is no datacenter list, no bundled bandwidth, and no vendor SLA on the free path — your hardware is the performance envelope and your ops team is the reliability story. The S3 compatibility is the infrastructure feature that counts: bucket policies, versioning, object locking for immutability, lifecycle transitions, and replication (active-active and multi-site in AIStor) line up with the S3 API surface that the ecosystem expects. AIStor adds the pieces enterprise buyers ask for — KMS-backed encryption, an Iceberg catalog for table formats, SFTP and S3 Express protocol support, and the full web management console that the community build lost.

Where it falls short

The direction of travel is the concern. In under two years MinIO removed the admin console from the free build, stopped shipping free binaries, froze the open-source codebase, and moved every operational nicety behind a licence key. The company's stated reason — maintaining two consoles is expensive, and unmaintained admin code is a security risk — is understandable. The effect is not: anyone who adopted MinIO as permanent Apache-licensed infrastructure with a management UI is not running that product anymore. In our view, treating MinIO as a fixed point in your architecture now carries policy risk, not technical risk.

The AGPL deserves a legal look before you commit. If you expose MinIO as part of a hosted service, expect copyleft obligations to attach; several infrastructure vendors dropped MinIO for exactly this reason. Commercial AIStor licensing removes that exposure, at quote-only prices that start high enough to exclude small teams.

Then there is the ordinary self-hosting overhead: capacity planning, hardware failure handling, upgrade choreography across nodes, monitoring, and backup strategy (replication is not a backup). The learning curve for distributed tuning is real, and the free tier gives you community Slack and docs — with the caveat that parts of the community documentation have gone dark along with the binaries. The user complaints from 2025 about the console removal were less about the feature itself than about the manner: a changelog that did not announce it, and no migration path other than "use the CLI or pay."

Who should pick this

We pick MinIO when S3 semantics must live inside your boundary: data-sovereignty workloads, air-gapped or regulated environments, private AI training lakes where data gravity rules out the public cloud, edge aggregation points, and dev/CI stacks that want S3 behaviour without a cloud account. AIStor Free on a single well-built storage node is our pick for homelabbers, researchers, and small teams running backups or media repositories where a node outage is acceptable.

We would not pick the frozen AGPL edition for anything that needs security patches going forward — that is a hard no for production in our view. And we would think twice before standardising a startup's entire data layer on a product whose free tier has narrowed twice; open-source alternatives (Ceph/RGW, SeaweedFS, Garage) trade polish for stability of terms, and cloud object stores trade control for zero ops. For large enterprises with compliance requirements and support budgets, AIStor Enterprise is a coherent purchase — just negotiate against the reported public figures and get the SLA terms in writing.

Key takeaways

Top-tier engineering for self-hosted S3-compatible object storage: single binary, erasure coding, bitrot protection, distributed mode, huge ecosystem compatibility.
The free open-source AGPL edition is frozen — no features, bug fixes, or security patches — per MinIO's own pricing page; the admin console left the community build in May 2025.
AIStor Free ($0, single node, proprietary licence, no redistribution) is the current free path; Enterprise Lite and Enterprise are quote-only.
Reported enterprise pricing runs from about $96,000/year at the low end to $244,032/year for 1PB usable (third-party quotes of MinIO's site — verify before buying).
AGPL network copyleft is a legal consideration if you expose MinIO inside a hosted service.
Our pick for private AI/ML data lakes, regulated and air-gapped environments, and single-node backup targets — with eyes open about licence risk.

Sources

Pros

S3 API compatibility that the whole tool ecosystem works against unchanged
Single-binary deployment on Linux, macOS, Windows, Kubernetes, bare metal, and edge hardware
Erasure coding, bitrot detection, versioning, object locking, and multi-site replication
AIStor Free is genuinely free for single-node use with the full feature set
Certified enterprise path (FIPS 140-3, SOC 2, ISO 27001, SEC 17a-4(f), FINRA) with sub-4-hour support SLA

Cons

Open-source AGPL edition is frozen — no security patches — and the community console lost admin features in 2025
AGPL network copyleft creates legal exposure when MinIO sits inside a hosted service
Enterprise pricing is quote-only, with reported floors around $96,000/year
Self-hosted means you own capacity planning, failure handling, and backups; replication is not a backup

Best For

Private AI/ML data lakes, regulated or air-gapped environments needing S3 inside their boundary, edge aggregation, CI artifact stores, and single-node backup targets.