Alarik Is Now in Beta
Alarik has moved out of alpha and into beta. It's still early, and we're not asking anyone to bet production workloads on it just yet - but the core feature set has stabilized enough that it's time to call it what it is: beta software.
What "Beta" Means Here
Alpha meant the API and console were still shifting under our own feet. Beta means the S3-compatible API surface, the console, and the configuration model are stable - the things we build on top of it (including our own internal usage) aren't expected to break with every release. We're now focused on hardening, performance, and closing gaps rather than reshaping core behavior.
What Alarik Supports Today
S3-Compatible API
The core of Alarik is a standard S3-compatible REST API. The AWS SDK, s3cmd, rclone, and any other S3-aware tool work against it unchanged - point them at your Alarik endpoint instead of AWS and go.
Web Console
A built-in, modern web console for managing buckets and objects - browsing, uploading, and administering your storage without needing a separate CLI for everyday tasks.
Webhooks
Alarik can deliver HTTP notifications when objects are created or removed, with HMAC-signed payloads and retry behavior for failed deliveries. Useful for triggering downstream processing - thumbnail generation, indexing, virus scanning, whatever your pipeline needs.
Replication
Continuous replication of a bucket's objects to another S3-compatible endpoint, with support for replicating existing objects and deletes, plus retry handling for failed replication tasks.
OIDC SSO
Alongside local username/password login, Alarik supports signing in via external OIDC identity providers - Okta, Google Workspace, Microsoft Entra, Keycloak, Auth0, and others. Providers are managed entirely from the console by an admin and stored in the database, so they can be added or removed without redeploying.
Admin Controls
Full admin API and console support for managing users, buckets, and OIDC providers, plus storage and system statistics for keeping an eye on your deployment.
Simple Deployment
Two containers - the API and the console - started with a single docker-compose.yml file. No cluster setup, no external database to provision.
What's Next
Beta is about hardening what's here, not chasing new surface area. Expect continued performance work, more operational tooling, and bug fixes as more people run Alarik on their own infrastructure. If you hit something broken, open an issue on GitHub - that feedback is exactly what beta is for.
Want to try it? Get started in a few minutes with Docker Compose.