what instead of minio? seaweedFS?

I discovered [seaweedFS]() from an email of @stebo85 describing his https://github.com/Australian-Imaging-Service/ais-devstack/tree/stanford and their https://github.com/Australian-Imaging-Service/ais-edge

and its [documentation for comparison against minio](https://github.com/seaweedfs/seaweedfs#compared-to-minio) said

> Please note, as Apr 25, 2026 MinIO ceased development.

which is apparently the case and https://github.com/minio/minio is now "archive" .

So, I wondered if anyone heard of/tried seaweed? From aforementioned comparison stating

> MinIO followed AWS S3 closely and was ideal for testing for S3 API. It had good UI, policies, versionings, etc. SeaweedFS is trying to catch up here.

it sounds like seaweedFS should be a viable alternative and potentially even with some pros due target `O(1)` complexity on operations with many files (Zarrs!)... I quickly searched for `versionId` and system seems to be aware of it so should be using it.

Start by reading the linked ais-devstack and ais-edge projects, then review SeaweedFS's comparison with MinIO and the current MinIO repository status. Determine whether SeaweedFS can replace the project's object-storage use cases, including versioning and large-file or Zarr workloads; the issue is done only when a supported direction and concrete infrastructure changes are defined.

Written by the indexing model from the issue text.