Alarik

Shifts around MinIO left teams reconsidering how safe it is to depend on a single reference implementation of the S3 API. Alarik answers that with object storage written in Swift, licensed under Apache 2.0 and meant to be run by the teams that depend on it.

The S3 surface covers core object operations, multipart uploads, bucket versioning, conditional requests, range reads with correct partial content semantics, presigned URLs, bucket policies and lifecycle rules, authenticated with SigV4 in header, query and chunked forms.

Around the API sits the rest of the system.

• Web console: an object browser with drag and drop upload, metadata editing, version browsing and time-limited shared links.
• Access control: local accounts, several OIDC providers, per user access keys and a bucket level public access block.
• Webhooks: AWS-shaped event notifications, HMAC signed, retried from a persistent outbox that survives restarts.
• Replication: SigV4 signed writes to any remote S3-compatible target, filtered by prefix and synchronous per rule if you ask.
• Erasure coding: Reed-Solomon data and parity shards spread across nodes and rebuildable from any k of them.
• No external database: buckets, users, keys, policies and cluster membership live in Alarik's own storage directory.

Placement uses rendezvous hashing, so any node can serve any request and a failed node never reshuffles data. Writes acknowledge once a quorum of shards land, while read repair and a background scrub rebuild anything missing or corrupted. Alarik runs on Linux, is labeled beta, and its authors intend to migrate their own accounting product onto it.