Tahoe-LAFS

Tahoe-LAFS is free, open-source software for distributing files across multiple storage servers. It is best suited to people prepared to run a gateway and connect it to a storage grid. Its key advantage is recoverable, encrypted storage without trusting storage servers with file contents; the trade-off is that users must arrange and operate the infrastructure.

Overview

Tahoe-LAFS splits files into erasure-coded shares and distributes them across storage nodes. Its documented defaults create 10 shares across at least 7 servers, with recovery possible from any 3 shares. That gives the system room to withstand server failures, but the default shares.happy setting prevents uploads on grids with fewer than 7 storage nodes unless it is adjusted.

Encryption and integrity checks take place at the gateway, so storage servers cannot read or modify file contents. This is a meaningful protection against untrusted storage operators, provided you control the gateway: an operator of a remote gateway can view and change the data. Tahoe-LAFS does not provide anonymity, and it does not conceal file size. Tor and I2P integrations are documented, but do not change those stated limits.

Key features

Recovery and integrity

Erasure coding lets clients recover files from a subset of shares when storage servers fail. The gateway also checks integrity and ignores corrupted shares. This makes Tahoe-LAFS a stronger fit for distributed infrastructure with imperfect availability than for a simple single-server file store. The default redundancy settings also mean that a small deployment needs configuration changes before uploads will work.

Gateway access and permissions

A gateway connects users to a storage grid over HTTP(S) or SFTP, and a REST-style Web API supports programmatic operations. Files can be immutable or mutable; mutable files and directories can allow either read-write or read-only access. These options suit deployments that need controlled sharing and application access, though they do not remove the work of maintaining a gateway and storage nodes.

Deployment and retention

Users can run a gateway against other people’s storage nodes or operate a complete grid with storage nodes and an introducer. The project documents installation for Windows, macOS, Linux, and BSD, and requires Python 3.9 or later; Python 2.7 users are directed to version 1.17.1. The public test grid is for experimentation, not dependable or large-scale storage. Storage servers may delete shares after leases expire if garbage collection is enabled; garbage collection is disabled by default, so retention depends on deployment settings.

Pricing

Free and open-source software: free. The self-hosted storage grid is the included model; there is no hosted plan or paid tier stated. That makes it a practical choice for users willing to provide their own infrastructure, not for readers looking to buy managed storage. The software is offered under GNU GPL version 2 or later, or the Transitive Grace Period Public Licence version 1.0 or later.

Platforms

Tahoe-LAFS is listed for API, Linux, macOS, self-hosted, web, and Windows use. Its installation guide also covers BSD systems. The typical setup has each user running a gateway locally and connecting to storage servers on other computers. Users who need deployment help can turn to the tahoe-dev mailing list or Libera.Chat.

Who it's for

Choose Tahoe-LAFS if you can run a gateway, arrange storage nodes, and want files encrypted before they reach storage servers, with recovery across failed nodes. It is a poor fit if you want a provider-managed storage plan, a dependable public test service, or anonymity. The default minimum of seven storage nodes is also a significant consideration for small grids.

Pros and cons

• Pros: Gateway-side encryption and integrity checks keep storage servers from reading or modifying file contents.
• Pros: Recovery from any 3 of the default 10 shares offers tolerance for unavailable storage nodes.
• Pros: HTTP(S), SFTP, and a REST-style API support both interactive and programmatic gateway access.
• Cons: The default configuration requires at least 7 storage nodes for uploads, making an unadjusted small grid unsuitable.
• Cons: A remote gateway operator can view and modify data, so users must trust the gateway or run their own.
• Cons: It has no hosted plan, and the public test grid is explicitly unsuitable for reliable or large-scale storage.
• Cons: It does not attempt anonymity and does not protect file size.

Alternatives

For a broader comparison, browse Distributed File System Software or Secure Cloud Storage.

• SeaweedFS is worth considering if its free Community support plan, which covers any cluster size and offers public documentation and GitHub support without a guaranteed response time, better matches your deployment.
• MooseFS offers a free GPLv2 Community plan with a single active master and single-parity erasure coding; choose it if those stated limits suit your cluster needs.
• Hadoop Distributed File System is another free, self-hosted cluster option under the Apache License 2.0.
• JuiceFS has a self-hosted Community Edition with support through GitHub and Discord; it may suit readers looking for those channels.
• OpenAFS is a free, open-source distributed filesystem to consider as another self-hosted option.
• OrangeFS offers a downloadable open-source release for readers comparing free filesystem software.
• Quobyte may suit readers whose needs fit its free edition, capped at 150 TB.
• Ceph is free distributed storage software for readers who have a running Ceph cluster for block storage.

Verdict

Tahoe-LAFS is a strong choice for technically capable users who want encrypted, recoverable files across storage servers they can connect to and a gateway they can trust. Its combination of gateway-side protection and recovery from a subset of shares is compelling; look elsewhere if you want managed storage, a small default-ready grid, or anonymity.