Alarik

Capabilities

• S3-compatible API Alarik speaks the S3 protocol for buckets and objects, including multipart uploads, versioning, range reads, and presigned URLs, so existing AWS SDKs, rclone, and s3cmd work against it without code changes.[1][2]

• Web console A Nuxt-based console covers bucket management, object browsing, version history, shared links, and an admin dashboard, giving small teams a usable interface without building their own tooling.[1][2]

• Access control Local accounts or admin-managed OIDC providers control sign-in, with per-user S3 keys and bucket policies scoping what each integration can read or write.[1]

• Event webhooks Bucket webhooks emit S3 event-shaped JSON with HMAC signatures and retryable delivery, so object uploads can trigger downstream processing in your own services.[1]

• Bucket replication Per-bucket replication copies objects to any S3-compatible target under sync or async rules, which supports off-site backup and migration workflows.[1]

• Cluster mode Opt-in clustering spreads objects as Reed-Solomon erasure-coded shards across nodes with rendezvous placement, quorum writes, and background repair, without requiring an external database.[1][2]

• Single-node deployment A single node runs from Docker Compose with no external database to provision, storing objects as local files that are fsynced before acknowledgement with streaming bodies and bounded memory.[1][2]

• Open license The codebase carries the Apache-2.0 license with no open-core split documented, so the full feature set described in the docs is the software you actually get.[1][2]

Who will love it

• Private S3 for product assets Teams serving uploads, backups, or datasets from their own infrastructure get an S3-shaped store with a console, without per-gigabyte cloud billing or egress surprises.[1][2]

• Homelab and small-team storage Docker Compose deployment with no database to manage keeps the operational floor low for homelabs and small teams that already run their own servers.[1][2]

• S3-tooling shops Shops already standardized on AWS SDKs, rclone, or s3cmd can redirect those tools at Alarik and keep existing workflows, presigned-URL sharing included.[1]

Limitations

• Beta status The project documents itself as beta as of July 2026, with breaking-change-era versioning, so operators should review release notes and keep tested backups before production use.[1]

• Narrow independent review sample No independent load, durability, or comparison measurements were found in this pass, and Reddit/G2 firsthand reports could not be inspected, so claims about behavior at scale rest on vendor documentation alone.[1][2]

• Operator skill required Clustering, OIDC, webhooks, and replication assume an operator who understands storage and access policy; there is no managed-hosting option documented for teams that want someone else on call.[1]

Compatibility