Skip to content
senn-techsenn-tech
Back to blog
Storage
Storage, backup and replication2026-11-19· By Franz Senn

MinIO's AGPL edition is archived, and the free AIStor edition forbids production use

MinIO has ended its open edition. The minio/minio repository is archived on GitHub, and the archived field in the API is true. On its pricing page the vendor says the AGPL edition is no longer maintained and its code base is frozen: no new features, no bug fixes, no security patches. For everyone who does not want to pay, the page points to AIStor Free, free of charge and aimed at developers, researchers, enthusiasts and small organisations. We read both pages and the license text on 19 November 2026 and measured the replacement projects through the GitHub API on 20 November 2026.

MinIO logo
MinIO, Inc. ended the AGPL edition and offers AIStor Free under a proprietary license. (Quelle: Simple Icons 16.36.0, file minio.svg (repository CC0), brand: MinIO, Inc.)

In short: AIStor Free is the free edition of MinIO's commercial object store, AIStor. It runs on one node with at most 10 TiB, is licensed for development and testing only, and prohibits production use, clusters, high availability and publishing benchmarks. MinIO's AGPL edition is frozen by the vendor's own account: there are no more bug or security fixes.

The repository is closed, the last release is over a year old

Measured through the GitHub API on 20 November 2026: minio/minio is archived, with 61,250 stars, 8,357 forks, 78 open issues and the AGPL-3.0 license. The last commit on the main branch is from 24 April 2026. The last published release is RELEASE.2025-10-15T17-29-55Z, published on 16 October 2025.

The client libraries are still active: minio-go (Apache-2.0, 3,019 stars) was last pushed on 12 November 2026, minio-java on 30 October 2026 and minio-js on 12 October 2026. The clients keep working while the server underneath receives no security fixes.

Unit: stars and days since the last published release. Measured 20 November 2026 through the GitHub REST API, our own measurement.

ProjectLicense per GitHubStarsLast releaseDays since release
minio/minio (archived)AGPL-3.061,250RELEASE.2025-10-15 (16 Oct 2025)400
rustfs/rustfsApache-2.036,3181.0.6 (15 Nov 2026)5
seaweedfs/seaweedfsApache-2.036,1624.54 (16 Nov 2026)4
juicedata/juicefsApache-2.014,763v1.4.2 (22 Oct 2026)29
ceph/cephno single license listed17,250not collectednot collected
Days since the last release, measured 20 Nov 2026SeaweedFS 4.544 · 4 daysRustFS 1.0.65 · 5 daysJuiceFS v1.4.229 · 29 daysMinIO OSS (archived)400 · 400 days0420
Days between publication of the last release and our measurement on 20 November 2026. A short gap proves nothing about quality. For MinIO OSS the long gap means, by the vendor's own statement, that there are no more security fixes. (Quelle: GitHub releases API, own measurement 20 November 2026)

What the license forbids

AIStor Free is not a plain download. The download page leads through "Request License Key Access" to a license key. The AIStor Free Tier License Agreement is dated 14 November 2026 and applies, by its own introduction, from version 11.x. The text names an individual who downloads the software as the contracting party.

The grant is a single sentence: a limited, non-exclusive, non-transferable, royalty-free license for non-commercial purposes, for up to 10 TiB of storage, in object code form, on one single node, expressly for development and test only. The restrictions, paraphrased from the text:

  • Distributed, cluster or high availability configurations are excluded.
  • Use in a production environment "of any kind" is forbidden.
  • Modifying, reverse engineering, derivative works, redistribution, renting and resale are forbidden.
  • You may not publish or share benchmarking tests with third parties.
  • You may hold only one license at a time and may not connect the software to "any third party's Software".
  • There is no support.

On "Ownership": MinIO keeps all rights to data derived from use, called "Usage Data", including configuration, deployment access, performance and operation. The same paragraph says users own the data they store. The text does not describe how the usage data is collected.

MinIO may terminate "immediately for its convenience", after which all copies must be destroyed. Breach notices go to the email address on file and count as received after 24 hours unless MinIO hears otherwise. The "Compliance" clause requires obeying applicable laws and sanctions lists; a violation of that clause means all copies must be deleted "immediately and irrevocably". California law applies, with Santa Clara County as venue. An arbitration clause (JAMS, San Francisco) applies only to parties outside the United States whose courts would not enforce a California judgment. MinIO's liability is capped at 20 US dollars.

Anyone who watches only the 10 TiB limit misses the sharper points: the production ban applies from the first byte, and the liability cap is 20 US dollars.

No fork in sight

An archived repository with 8,357 forks suggests that a branch lives on somewhere. In a limited GitHub search for "minio" we found no server derivative with notable traction: soulteary/otterio (Apache-2.0, 98 stars, described as an independently maintained fork of the Apache-licensed MinIO code base, created 3 June 2026) and miniosv/miniosv with 10 stars. We did not go through the full fork list.

Independent projects with an S3 interface include RustFS and SeaweedFS, both Apache-2.0 and freshly maintained on the measurement day (table above). JuiceFS is a file system with an S3 gateway. We ran Ceph ourselves and explain in the storage journey on Ceph why we moved away.

What is affected on our side

Our mail blobs live in a MinIO bucket. The Stalwart 1.0 migration post gives the state of 2 November 2026: 69,553 objects, 4.9 GB. We did not re-read which MinIO edition and which license tier runs there for this post. The answer depends on the contract and not on the bucket size. The store of a production mail system is a production environment in the sense of the Free license, and the clause on "third party's Software" touches every S3 client from another vendor. Whether it means an ordinary client is a question for a contract review.

What the decision depends on

For companies with a grown MinIO estate there is no free path that continues where the AGPL edition ended. The pricing page lists three tiers: AIStor Free, Enterprise Lite (by the page, for capacities below 400 TiB, distributed and highly available) and Enterprise. We found no price list with amounts there, so this post gives no figure. Anyone migrating towards AIStor should know three things: Free excludes any multi-node layout, even a second node meant only as a safeguard. The license can be terminated at any time, with an obligation to delete. And measurements made under Free may not be published.

For new builds without budget, Apache-2.0 projects remain. SeaweedFS needs an understanding of its split into master, volume and filer. RustFS is at version 1.0.x, so still early. The vendor's license risk turns into your own operations burden. We would choose by asking which team can read the source when something breaks, and not by stars.

Our recommendation in three steps. First, record which container pulls which image, with digest, because minio/minio as a tag means something different today than two years ago. Second, review your own license with the contract in hand. Third, measure RustFS and SeaweedFS against each other with your own object counts. More measurements on storage options are in the Storage and Backup topic hub; for selection and migration, see our IT operations and consulting.

Further Reading

Primary sources, all read on 19 November 2026, figures from the GitHub API measured on 20 November 2026:

Own measurement: stars, forks, license field, commit and release dates through the GitHub REST API, one request per repository on 20 November 2026, days counted up to that date. For our mail bucket the post uses only the figures published on 2 November 2026.

Questions?
Is AIStor Free open source?+

No. AIStor Free is proprietary software. You request a license key through the download form, and it is governed by the AIStor Free Tier License Agreement dated 14 November 2026 (read on 19 November 2026). The AGPL edition of MinIO was open source; it is archived on GitHub.

What about a MinIO container that has run for years?+

It keeps running but receives no fixes. The last release of the AGPL line is RELEASE.2025-10-15T17-29-55Z, the repository is archived, and its last commit is from 24 April 2026 (GitHub, 20 November 2026). The vendor's pricing page says the code base is frozen, with no new features, bug fixes or security patches. A running container does not report this state by itself.

Who is AIStor Free enough for?+

A single node with at most 10 TiB that serves development and testing only and publishes nothing that counts as a benchmark. Using it for customer previews, backups or a document archive falls outside the license as written, however full the disk is. Whether a given use is covered is a question for the contract.