Les Orchard <me@lmorchard.com>

Access other storage backends via the S3 API

Radicle is an open source, peer-to-peer code collaboration stack built on Git. Unlike centralized code hosting platforms, there is no single entity controlling the network. Repositories are replicated across peers in a decentralized manner, and users are in full control of their data and workflow.

🚀2.3x faster than MinIO for 4KB object payloads. RustFS is an open-source, S3-compatible high-performance object storage system supporting migration and coexistence with other S3-compatible platforms such as MinIO and Ceph.

SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, xDC replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding. Enterprise version is at seaweedfs.com.

In late 2025 the company behind MinIO decided to abandon it to pursue other commercial interests. As well as upsetting a bunch of folk, it also put the cat amongst the pigeons of many software demos that relied on MinIO to emulate S3 storage locally, not to mention build pipelines that used it for validating S3 compatibility. In this blog post I’m going to look at some alternatives to MinIO.

There’s a new kind of power emerging in culture: the identity industrialist. Not a filmmaker, not a technologist, not a marketer, but a person who manufactures human beings the way earlier generations manufactured steel, automobiles, or celebrities. They don’t manage talent; they produce it. And their raw material isn’t silicone or code but identity itself.

Identity-aware VPN and proxy for remote access to anything, anywhere.

They lined up the editors first, zip tying their hands together and leading them into vans downstairs. Then they began to gather the rest of the journalists. Laptops were gathered from desks. The server room, such as it was in the wake of zero trust and enterprise cloud services, had its door kicked in, switches and rack servers ripped out of their frames. One IT support engineer objected and found a gun in his face, the safety off, its owner ready to make them into an example.

What’s important here is making it very clear to potential users what they should expect from that software. I’ve started publishing my AI-generated and not 100% reviewed libraries as alphas, which I’m tentatively thinking of as “alpha slop”. I’ll take the alpha label off once I’ve used them in production to the point that I’m willing to stake my reputation on them being decent implementations, and I’ll ship a 1.0 version when I’m confident that they are a solid bet for other people to depend on. I think that’s the responsible way to handle this.