MinIO
MinIO · cloud storage · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-12
Still the de-facto standard self-hosted S3 with a huge ecosystem — but no tagged release since Oct 2025 and a narrowed public branch: no longer the default pick.
#11 of 12 in Cloud Storage
ToolScore breakdown — why 41/100
10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →
What it does well
- ▸Still the de-facto standard self-hosted S3 with a huge ecosystem
- ▸Client SDKs stay Apache/MIT — the license trap does not reach your clients
- ▸Unmodified use is fine under AGPL §13 — the obligation triggers only on modified network service
- ▸The S3 surface is the reference implementation everything else is measured against
Where it costs you
- ▸No tagged release has shipped since Oct 2025 — 13 months stale at our check
- ▸The public branch narrowed in 2025: features were removed from the web UI
- ▸AGPL §13: a modified MinIO offered as a network service owes the source of your modifications
- ▸The hub's verdict for new deployments: weigh SeaweedFS or Garage first
Hidden traps — the stuff the pricing page doesn't say
The last public release is dated 2025-10-15 — 13 months stale as of our 2026-11-12 check. No tagged release has shipped since. For software whose job is to hold your data, a frozen release pipeline is the trap that outranks every feature.
Features were removed from the web UI as the public branch narrowed in 2025. Deployments that depended on the removed surface discovered the change from the changelog of an absence — the hub's reason for scoring transparency low.
A modified MinIO offered as a network service owes the source of your modifications (unmodified use is fine; client SDKs stay Apache/MIT). The license was Apache 2.0 until April 2021 — deployments older than the switch should know which regime they married.
Know the limits before you pay: read the traps above, then decide with eyes open.
Visit official siteAffiliate link where available — never affects the score.
- official MinIO — AGPL-3.0 license and release history (checked 2026-11-12 via the hub's GitHub pass) verified
Data as of 2026-11-12. Prices and limits change monthly — report anything stale. How we verify: methodology.
Closest alternatives
"Free egress" with three conditions: a 1TB minimum floor, a 90-day minimum storage duration, and a 1
The egress tax incumbent: $0.09/GB out makes egress ~94% of the bill — the same workload that costs
A Dropbox/Drive replacement (sync clients, sharing, apps), not an object-storage server — S3 can sit
MinIO review
In-depth analysis · last updated 2026-11-12
The standard that stopped shipping
MinIO remains the de-facto standard self-hosted S3 with a huge ecosystem — the name everyone means by "self-hosted S3". That installed base is exactly why the hub's verdict stings: the last public release is dated 2025-10-15, 13 months stale at our 2026-11-12 check, and no tagged release has shipped since. The "default" self-hosted S3 is no longer the default pick.
What narrowed
The public branch narrowed in 2025, with features removed from the web UI — so even the running software is a smaller product than the one the ecosystem wrote its tooling around. Combine that with the release freeze and the risk profile inverts: the safest-sounding name in self-hosted storage has become the least-maintained row in the table.
The license chapter
AGPL-3.0 applies: a modified MinIO offered as a network service owes the source of your modifications — unmodified use is fine, and client SDKs stay Apache/MIT. The license was Apache 2.0 until April 2021, so long-running deployments should know which regime they signed up under. None of this touches a private unmodified cluster; all of it matters the moment you ship MinIO inside a product.
How the pillars land
Track record 1.5: 13 months without a tagged release is the single worst maintenance signal in the hub — this pillar alone sinks the total. Pricing transparency 2.5: the narrowing was quiet; features vanished from the public branch rather than from a priced tier. Feature set 3.5: still a full S3 surface, minus what the narrowed branch removed. Price/Value 4.5: $0 license, but the hub scores value per operational effort for a new deployment — and a stale release pipeline is operational risk. Real limits 4, Transfer speed 4, Ease 4: unremarkable and unmaintained. S3/API interop 8: the ecosystem is real — the huge tooling surface and SDK support remain MinIO's one undiminished strength. Privacy 5 and Support & docs 5, neutral: nothing verifiable in this snapshot.
Verdict — NICHE, 41/100
Stay on MinIO if you are already on it and it works. For new deployments the hub is explicit: weigh SeaweedFS or Garage first — maintained, permissive-or-clear licenses, and no 13-month gaps.