MinIO's community edition is archived. What still runs in 2026
MinIO's community edition is archived. What actually changed, what it means if you run it, and the open-source S3 options still maintained in 2026.
In December 2025, MinIO declared its open-source repository in maintenance mode. In February 2026 it updated the README again with language most readers took as end-of-life. On April 25, 2026 the repository was formally archived, and it has been read-only since.
If you run MinIO Community Edition today, your deployment still works. That is the trap. Storage that keeps serving while its upstream goes dark feels fine right up until the day it doesn't.
What changed for MinIO Community Edition
MinIO did not relicense. The server code is still AGPLv3, still open source by the only definition that matters legally. What ended was maintenance and distribution. No new releases, no reviewed patches, no official community binaries. The path went from "pull the image" to "build it yourself from frozen source."
For most components that would be an annoyance. For the storage layer under your backups, your uploads, and your build artifacts, the change in risk profile is the whole story. The last community release shipped a privilege-escalation fix in October 2025. The next CVE in that codebase is yours to find, patch, build, and ship. You have inherited a release pipeline you never asked for, on the one piece of infrastructure you most want to be boring.
MinIO alternatives still maintained in 2026
You have three honest options.
Keep running it and own the maintenance. Viable if you have the Go expertise on staff and the appetite to track CVEs against a codebase nobody upstream is watching. Be honest with yourself about whether that is true.
Move to a commercial product, MinIO's own or someone else's. Reasonable, as long as you read the license and the exit path before you commit, so the next wind-down doesn't strand you the same way.
Move to an S3-compatible engine whose open-source upstream is still alive. This is the path worth naming, because it exists. Garage, built by Deuxfleurs is AGPLv3, actively maintained, and designed for the self-hosted, multi-node, S3-compatible job MinIO used to do. The community around it did not abandon the commons. It is still shipping.
| MinIO Community Edition | Garage | Commercial (MinIO or other) | |
|---|---|---|---|
| License | AGPLv3 | AGPLv3 | Proprietary / commercial |
| Upstream status | Archived, read-only since April 2026 | Active, still shipping (Deuxfleurs) | Vendor-controlled |
| Security patches | You build and ship them | Upstream, and you can send them back | Vendor, while your contract holds |
| Official releases | None, frozen source | Yes | Yes |
| Multi-node / distributed | Yes, but unmaintained | Yes, designed for it | Yes |
| S3-compatible | Yes | Yes | Yes |
| Who carries maintenance | You, alone | Shared with a live community | The vendor, until terms change |
Where Storm Buckets fits
We are not recommending Garage from the sidelines. Garage is the engine under Storm Buckets: we operate it in production, we file issues upstream, and we have patches merged into the Garage codebase. When we hit a CORS bug in the S3 layer, the fix went back to Deuxfleurs, not into a private fork. We run the exact public version we document, and there is nothing in our stack you cannot read.
The agent that manages the nodes, Storm Pulse, is open source too, published and installable today. You can take Garage and Pulse and run all of it yourself for free. If you'd rather have someone else carry the operations, the whole stack is readable, run by a company whose only job is this layer.
That is what Storm Buckets is, currently in closed alpha: Canadian-hosted, S3-compatible, Garage underneath. Every S3 and admin operation against your account is recorded, and you can watch it happen in real time.
The lesson for self-hosted storage
MinIO's wind-down followed a familiar pattern. The company and the commons were the same entity, and the company changed its mind. The defense against that is infrastructure you can read, on a license that cannot be revoked out from under you, run by people who feed the upstream instead of mining it. Trusting a different vendor just relocates the same risk to a new logo.
That is the bet Storm is built on. MinIO made the case for it better than we could.
Frequently asked questions
Is MinIO Community Edition discontinued?
Effectively yes. MinIO put the open-source repository in maintenance mode in December 2025 and formally archived it on April 25, 2026. It has been read-only since: no new releases, no reviewed patches, no official community binaries.
Is MinIO still open source?
The Community Edition server code is still AGPLv3, so it is still open source by the license that matters legally. What ended is maintenance and distribution, not the license. You can read and build the frozen source, but nobody upstream is patching it.
Does MinIO Community Edition still work in 2026?
Yes, existing deployments keep serving. That is exactly the risk.
It runs fine until a CVE lands in a codebase no one upstream is watching, and then finding, patching, building, and shipping the fix is entirely on you.
What is the best maintained MinIO alternative?
For a self-hosted, S3-compatible, multi-node engine whose open-source upstream is still active, Garage (by Deuxfleurs, AGPLv3) is the closest like-for-like replacement. If you would rather not run the storage yourself, Storm Buckets is Canadian-hosted object storage built on Garage.
The Storm Buckets alpha is invite-only while we harden the platform. If you are leaving MinIO and want a Canadian, open, auditable place to land, request alpha access. Storm Pulse is public now: git.stormdevelopments.ca/official-public/storm-pulse.
100% Canadian Hosted.