Practices · MinIO

MinIO's open-source repository is archived: nothing breaks, nothing gets fixed

The minio/minio repository is archived, with its last commit in April 2026, and the README now points at AIStor instead. Existing installs keep serving unchanged, but no further upstream fixes are coming, so the question is when to migrate and to what.

By BoneThursday 22 October 20263 min readPractices

entryread only

filedThursday 22 October 2026

length3 min

sectionPractices

subjectMinIO

sourceson the page

You can check this one in ten seconds. The minio/minio repository on GitHub reports "archived": true, and its README opens with a banner that says it outright: “THIS REPOSITORY IS NO LONGER MAINTAINED.” The project still describes itself as a “high-performance, S3 compatible object store, open sourced under GNU AGPLv3 license”, and the archived code remains available under that license. What stopped is maintenance, and the repository page dates the moment: “This repository was archived by the owner on Apr 25, 2026. It is now read-only.” Its last commit is a day earlier, on 24 April 2026. No vendor announcement explaining the decision was found beyond that banner.

What stops, and what keeps running

Nothing breaks today. Existing binaries and container images keep serving, and the S3 API is whatever it was, so every client that pointed at your MinIO yesterday still works.

Nothing gets fixed upstream either. An archived repository with a banner saying it is no longer maintained is not going to produce another release, which means the daemon that holds your backups, photos or media library stops receiving security fixes. That is the whole cost, and it is a quiet one: MinIO is often the one service on a homelab that answers on the LAN and occasionally from the internet, and “no more upstream fixes” is a sentence with a long tail. The data is fine. The tap that used to close holes is off.

The vendor’s successor

The README points at two products: AIStor Free, described as “Full-featured, standalone edition for community use (free license)”, and AIStor Enterprise, described as “Distributed edition with commercial support”.

The download page describes AIStor Free as being “For developers, researchers, enthusiasts, small organizations, and anyone comfortable with a standalone deployment who needs a powerful S3-compatible object store for structured and/or unstructured data”, and offers an enterprise trial that grants “a 60 day trial license with full enterprise features”.

Two limits on that. “Free license” is the README’s own phrase, and AIStor Free is described there as a standalone edition; the license terms themselves were not read for this piece, so none of that is a claim that AIStor Free is open source or AGPL. What is AGPL is the archived MinIO code you already have, and that does not change.

Two S3 alternatives

If you would rather move to a different S3 server, two projects came with primary evidence.

SeaweedFS is the one with a current push in the records gathered here: Apache-2.0, 35,685 stars, last pushed on 22 October 2026. Its description reads “a distributed storage system for object storage (S3), file systems, and Iceberg tables, designed to handle billions of files with O(1) disk access and effortless horizontal scaling.”

Garage, from Deuxfleurs, sells itself in one line: “An S3 object store so reliable you can run it outside datacenters.” Its site links documentation, downloads and a blog. Its license was not verified here, so treat it as described by its own pages rather than characterized by this piece.

Neither gets a benchmark, a capacity claim or a promise from this piece that it slots in without work. What is supported here is that both speak S3; how actively either is maintained is a question for its own releases page, worth checking before you commit.

What a move actually involves

Moving is a project, not a toggle. Your clients point at an endpoint with keys and a bucket layout, and a different server means repointing all of that and copying the data across, then convincing yourself that every application which held a credential still works. The size of the job is the size of what you store, and this piece has no timing estimate to offer.

The decision is about what your MinIO holds. If it is the storage behind apps you rely on, or the destination your backups write to, put the migration on the calendar and give it a weekend. If it is a scratch bucket for experiments, you have time and the archival costs you nothing yet.

Sources: the minio/minio repository record, the project README, the MinIO download page, the SeaweedFS repository record, and the Garage homepage.

PracticesForgejo drops OpenID 2.0 in v19, and your deadline depends on your release trackA Forgejo notice dated 2 November 2026 says OpenID Authentication 2.0 support ends in v19, scheduled for 25 March 2027, with v15 LTS the last release to carry it on the LTS track and v17 and v18 on the stable track. The notice also says OIDC and OAuth are unaffected, gives no CVE or security reason, and sends readers to a discussion thread for the reasoning. No configuration keys or setup steps were collected for this note.

PracticesHaxy: a git forge in preview that keeps project metadata in the repoThe new MIT-licensed forge stores issues, discussions and patches as event commits on a repository branch so projects move between instances, serves its terminal UI over SSH, and warns that preview data is deleted before production.

PracticesThe blocklists carry GoatCounter's custom domains, and EasyPrivacy's ping rule catches cross-domain countingGoatCounter's FAQ warns that custom domains will not prevent adblockers from recognizing it; AdGuard's DNS filter enumerates more than 230 of them, a generic ping rule catches cross-domain counting, and first-party or server-side counting is what remains.