Technology

OpenMaxIO

Initial community fork of [MinIO](/node/minio) created in May 2025 to restore the management UI and admin features that MinIO Inc. removed from the open-source community edition. Was attempted as the open-source landing zone for operators left behind when MinIO Inc. pivoted to AIStor commercial product. **Status as of late 2025: abandoned.** The community fork that actually carries the ongoing MinIO-without-the-company workload is [pgsty/minio](/node/pgsty-minio-fork) instead.

2 connections

Definition

What it is

Initial community fork of [MinIO](/node/minio) created in May 2025 to restore the management UI and admin features that MinIO Inc. removed from the open-source community edition. Was attempted as the open-source landing zone for operators left behind when MinIO Inc. pivoted to AIStor commercial product. **Status as of late 2025: abandoned.** The community fork that actually carries the ongoing MinIO-without-the-company workload is [pgsty/minio](/node/pgsty-minio-fork) instead.

Primary use cases

None — the project is abandoned. Operators previously interested in OpenMaxIO should evaluate [pgsty/minio fork](/node/pgsty-minio-fork) (active CVE patching, builds shipped through April 2026), [SeaweedFS](/node/seaweedfs), [Garage](/node/garage), [Ceph](/node/ceph), or [RustFS](/node/rustfs) as live alternatives — see `Self-Hosted S3 after MinIO` for the broader landscape.

Recent developments

Latest signals

Connections 2

Outbound 2
scoped_to1
alternative_to1