● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
KubeEra
M

MinIO

Runtime
Open source · AGPL-3.0

MinIO is an S3-compatible object storage server written in Go.

updated 2026-07-01

What it is

MinIO is an S3-compatible object storage server written in Go. It implements the S3 API surface closely enough that most S3 SDKs, CLIs, and tools (aws-cli, boto3, s3fs, backup tools, Spark/Presto connectors) work against it without modification. It runs as a single binary, scales from a laptop to multi-node erasure-coded clusters, and is commonly deployed as the storage layer behind Kubernetes-native data platforms — CI/CD artifact stores, ML training data lakes, Velero backup targets, log/metrics archival, and general-purpose blob storage where teams don't want to depend on a cloud provider's native object store.

Who builds it and why

Description not publicly available from the source data given, but MinIO is developed primarily by MinIO, Inc., a commercial company that dual-licenses the project: AGPL-3.0 for the open-source server, and a paid enterprise license (AIStor) for support, additional features, and organizations unwilling to comply with AGPL's copyleft terms. This is the standard "open core funds the company" model — the community edition is fully functional S3-compatible storage, but MinIO, Inc. drives the roadmap, and commercial pressure shapes what does and doesn't land in the OSS repo. Founding date and CNCF maturity status: not publicly available.

Production readiness signal

61,250 GitHub stars and 534 contributors indicate broad adoption and a real contributor base, not a single-vendor toy project. Last commit dated 2026-04-24 shows active, ongoing development. Release cadence uses MinIO's dated versioning scheme (RELEASE.2025-10-15T17-29-55Z), with releases shipping roughly monthly — consistent with a project under continuous production use rather than sporadic maintenance. CNCF maturity level is not publicly available, which matters: MinIO is not a CNCF project, so it doesn't carry the graduation/incubation signal that comes with formal CNCF governance review.

Who should use this

Teams running Kubernetes on-prem or in colo who need S3-semantics storage without a cloud object store — this is MinIO's core use case. It's a strong fit for air-gapped or regulated environments where data can't leave your infrastructure, for ML/AI pipelines needing high-throughput local object storage, and for teams already invested in the S3 API who want a drop-in on-prem equivalent. It's also a common choice as a Velero/Restic backup target and as scratch storage for Spark/Presto/Trino data lakes.

Who should NOT use this

Any organization uncomfortable with AGPL-3.0 needs legal sign-off before shipping MinIO as part of a product — AGPL's network-use clause triggers source-disclosure obligations that many companies' legal teams reject outright, especially if you're embedding it in a distributed SaaS offering. Teams already fully committed to a hyperscaler (S3, GCS, Azure Blob) with no on-prem requirement gain little by adding MinIO as another storage system to operate. Also skip it if you need a managed, hands-off experience — MinIO gives you the software, not the operations; you own erasure coding configuration, node failure handling, upgrades, and capacity planning, or you pay for AIStor to get that from MinIO, Inc.

Alternatives

  • Ceph (RGW) — more general-purpose distributed storage (block, file, object) with a steeper operational learning curve, no single-vendor licensing risk.
  • SeaweedFS — lighter-weight, simpler operationally, S3-compatible, smaller community and less battle-tested at large scale.
  • Cloud-native object stores (S3, GCS, Azure Blob) — the right choice if you're already cloud-committed and don't need on-prem/air-gapped storage.

Pricing

The MinIO server itself is open source under AGPL-3.0 — free to run, self-host, and modify, subject to AGPL's copyleft obligations. Commercial support, enterprise features, and management tooling are sold separately as AIStor by MinIO, Inc.; specific pricing is not publicly available and requires contacting sales.

Frequently asked

What is MinIO?+
MinIO is an S3-compatible object storage server written in Go. It implements the S3 API surface closely enough that most S3 SDKs, CLIs, and tools (aws-cli, boto3, s3fs, backup tools, Spark/Presto connectors) work against it without modification.
Who builds MinIO?+
Description not publicly available from the source data given, but MinIO is developed primarily by MinIO, Inc., a commercial company that dual-licenses the project: AGPL-3.
Is MinIO production ready?+
61,250 GitHub stars and 534 contributors indicate broad adoption and a real contributor base, not a single-vendor toy project. Last commit dated 2026-04-24 shows active, ongoing development. Release cadence uses MinIO's dated versioning scheme (RELEASE.
Who should use MinIO?+
Teams running Kubernetes on-prem or in colo who need S3-semantics storage without a cloud object store — this is MinIO's core use case.
Who should not use MinIO?+
Any organization uncomfortable with AGPL-3.0 needs legal sign-off before shipping MinIO as part of a product — AGPL's network-use clause triggers source-disclosure obligations that many companies' legal teams reject outright, especially if you're embedding it in a distributed SaaS offering.
What are the alternatives to MinIO?+
Ceph (RGW) — more general-purpose distributed storage (block, file, object) with a steeper operational learning curve, no single-vendor licensing risk. SeaweedFS — lighter-weight, simpler operationally, S3-compatible, smaller community and less battle-tested at large scale.
How much does MinIO cost?+
The MinIO server itself is open source under AGPL-3.0 — free to run, self-host, and modify, subject to AGPL's copyleft obligations. Commercial support, enterprise features, and management tooling are sold separately as AIStor by MinIO, Inc.; specific pricing is not publicly available and requires contacting sales.