Garage

Decentralized Storage Network

An S3-compatible object store for small, self-hosted, geo-distributed deployments, designed so that a cluster can run outside datacentres on whatever second-hand machines are available. Each chunk of data is replicated in three zones; the cluster tolerates network failures, latency, disk failures and operator error; it ships as a single dependency-free binary and runs on modest hardware (any x86_64 CPU of the last ten years, ARMv7 or ARMv8, 1 GB of RAM, 16 GB of disk, 200 ms latency or less). It implements the Amazon S3 API so many applications already work with it, and it draws on research on Dynamo, conflict-free replicated data types and Maglev. It is run and funded as a community and public-funding project and is not a network anyone can join: the operator of a cluster decides who the nodes are .

Community
Links
Visit Website See this tool in the graph Suggest an edit

Details

License Copyleft (AGPL-3.0). https://git.deuxfleurs.fr/Deuxfleurs/garage (Rust; the project's own Forgejo instance)
Dev Status 🟢 Active
Owner Deuxfleurs (the project's repository and website are hosted on Deuxfleurs' own infrastructure; the project's funders are listed on its site)
Governing Body Deuxfleurs, with its community; no formal governance document is described in the cited sources
Country Not stated by the project.
Start Year 2020
Stack Rust (single dependency-free binary); S3-compatible API; replication across zones; the site cites Dynamo, CRDT and Maglev research as inputs
Funding Public funding: NGI POINTER (European Union Horizon 2021, three full-time staff for a year, 2021-2022), NLnet / NGI0 Entrust (one staff, 2023-2024) and NLnet / NGI0 Commons Fund (1.5 staff, 2025); donations and support contracts are invited
Last Investigated Oct 29, 2026

Use Case Domains

Platform Evolution & Sovereignty

Affordances

Self-hostable Data portability

Decentralized Storage Network Attributes

Origins Software for small, community-run clusters: sysadmins who know the value of operator-friendly software, who do not have a dedicated backbone and want redundancy over the ordinary internet
Database Object store with internal replicated metadata; no external database
Query Language S3 API (Amazon S3-compatible)
Data Formats S3 objects and buckets; data stored in chunks replicated across zones
Mobile Support None: server software accessed through the S3 API
Web Support Can host static websites from buckets, per the site's 'Host a Website' use case
Native Apps None: server binary
Terms Free and open source (AGPL-3.0); support contracts are available on request
Funds Not stated by the project.
Based On Research on Dynamo (Amazon's highly available key-value store), conflict-free replicated data types and Maglev, per the site
P2P Architecture A cluster of nodes run by one operator (or a group of friends) across several zones or datacentres, with data replicated three times; not an open network
Overlay Network None: the cluster connects over ordinary internet links between operator-chosen nodes
Content Addressing No: objects are addressed by bucket and key through the S3 API
Local-First No: it is a storage server for self-hosting rather than a local-first data layer
E2EE No: the server stores objects as given; encryption is the client's job
Byzantine Fault Tolerance No: nodes are trusted members of one operator's cluster; the design targets crashes, partitions and disk failures
Signature N/A: requests are authenticated with S3-style access keys
Permissions S3-style access keys and bucket permissions managed by the operator
Semantic Web Compatibility N/A: no RDF, JSON-LD or SPARQL layer.
Smart Contract N/A: no ledger or contract component
Protocol Stack Position Application-layer (S3 over HTTP)
Asset / Value Embedding None: no token or value-transfer mechanism
Protocol Maturity / Standardization Version 2.x production software that implements the de facto S3 API; no standards-body involvement
Update Policy Mutable: objects can be overwritten or deleted through the S3 API; versioning is not described in the cited sources
Storage Proof Mechanism None: the operator runs the nodes; replication in three zones is the integrity mechanism rather than audits or proofs
Economic / Incentive Model None: no payments or tokens between nodes; funded by public grants, donations and support contracts
Retrieval Guarantee Replicated in three zones and designed to resist network failures, latency, disk failures and operator error; no external guarantee is offered