alberry brings instant snapshots, self-healing integrity, and live resizing to every workload — from a single edge node to a fleet of Kubernetes clusters.
BUILT FOR
ext4 and xfs were designed for machines that stay put. Enterprise SAN/NAS solves scale but drags in cost and complexity most teams don't need.
One filesystem, one CLI, no bolt-on tooling.
Copy-on-write snapshots complete in milliseconds regardless of volume size — take one before every deploy.
Every block is checksummed with BLAKE3. Corruption is detected and repaired automatically from redundant copies.
Grow or shrink a mounted volume with zero downtime — no unmount, no reboot, no maintenance window.
Zstd compression applied at the block layer, invisible to applications, typically 1.5–2.5x on real workloads.
Per-volume AES-256 encryption with key rotation, managed through the same CLI you use for everything else.
One binary for format, mount, snapshot, and scrub operations — plus a gRPC API for automation and orchestration.
Snapshot stateful sets before every rollout and roll back a volume as fast as you roll back a deployment.
Take a consistent snapshot before migrations and schema changes without taking the database offline.
Self-healing checksums catch flash-media corruption on remote hardware nobody can walk up to.
Clone a golden snapshot for every build runner in milliseconds instead of re-provisioning disks.
Snapshot training datasets alongside model checkpoints so every run is exactly reproducible.
Per-tenant volumes with independent quotas, encryption keys, and snapshot schedules on shared hardware.
alberry is built around a B-tree metadata layer and a copy-on-write allocator, the same family of design as ZFS and Btrfs, tuned specifically for fast local NVMe and predictable resource use on small hosts.
Every write is checksummed before it's acknowledged. A background scrubber walks the tree on a schedule you control and repairs any block that fails verification using redundant metadata.
alberry batches writes differently depending on what it's talking to — sequential bursts to spare a spinning platter, fanned-out parallel writes across NAND channels on flash.
Mechanical seek — one write at a time, latency dominated by head movement.
Parallel NAND channels — many writes complete simultaneously, no moving parts.
Linux x86_64 / arm64 · kernel 5.10+
curl -sSL https://get.alberry.tech | sh
Prefer a package? .deb · .rpm · source tarball