Garage

Use it when

• Nodes live in different buildings on ordinary internet links; zone-aware placement across sites is the design goal, not an add-on.
• Hardware is modest: one dependency-free Rust binary, 1 GB of RAM and 16 GB of disk per node, down to a Raspberry Pi.
• The operational surface must be minimal: no external database, no coordination service, no daemon zoo.
• Self-hosted applications (Nextcloud, Matrix, Mastodon) need an S3 backend without cloud spend.

Think twice when

• The workload is a lakehouse at scale; the project itself is not aimed at petabyte analytics, and choosing it for that reads the design against its intent.
• Capacity economics need erasure coding; durability is full copies only, replication factor 3 by default.
• Compliance features matter: no object lock, versioning, ACLs, tagging, or event notifications.
• Tiering and lifecycle beyond expiry are expected.

How it runs

A single self-hosted binary per node on any Linux (x86_64, ARMv7, ARMv8), clustering peer to peer and tolerating slow links between sites. It exposes the S3 API plus static website hosting and an optional K2V key-value store. AGPL-3.0 licensed, from the Deuxfleurs collective.