Skip to main content

Synchronize local directories with Tahoe-LAFS storage grids.

Project description

Gridsync aims to provide a cross-platform, graphical user interface for Tahoe-LAFS, the Least Authority File Store. It is intended to simplify the Tahoe-LAFS installation and configuration process and ultimately provide user-friendly mechanisms for common use-cases like backing up local files, synchronizing directories between devices, and sharing files and folders with other users across all major desktop platforms (GNU/Linux, macOS, and Windows). More broadly, Gridsync aims to duplicate most of the core functionality provided by other, proprietary “cloud” backup and synchronization services and utilities (such as Dropbox and BitTorrent Sync) but without demanding any sacrifice of the user’s privacy or freedom – and without requiring usage or knowledge of the command line. Accordingly, Gridsync is developed with the goal in mind of making secure cloud storage freely available to everyone, without exception, without added barriers, and regardless of one’s operating system choice.

Why Gridsync?

Tahoe-LAFS already provides a number of highly desirable properties for secure file-storage: in addition to offering client-side encryption, it is decentralized, robust, free (as in both beer and speech), stable and mature, and written by a group of very talented developers. Unfortunately – and despite all of its technical merits – Tahoe-LAFS has a number of persistent usability issues which steepen its learning curve: its installation requires manual compilation from source on Windows and macOS, its configuration consists in hand-editing text files, its primary interface requires heavy command line usage, and many of its fundamental concepts (e.g., “dircap”, “shares”, “servers-of-happiness”) are opaque to new users or otherwise demand additional reading of the project’s extensive documentation. Accordingly, Tahoe-LAFS’ userbase consists primarily in seasoned developers and system administrators; non-technical users are naturally excluded from enjoying Tahoe-LAFS’s aforementioned advantages.

The Gridsync project intends to overcome some of Tahoe-LAFS’s usability barriers by means of following features:

  • “Batteries included” packaging – Gridsync bundles will include Tahoe-LAFS and all required dependencies for a frictionless installation experience; no python installation or manual compilation is required.

  • A graphical user interface for managing primary Tahoe-LAFS functionality (e.g., starting, stopping, configuring gateways) – the user will never have to edit a text file by hand or touch the command line.

  • “Native” look and feel – Gridsync uses the Qt application framework, emulating native widgets on all target platforms; the user can expect Gridsync to behave like any other desktop application.

  • Automated bi-directional file synchronization – Gridsync will monitor local and remote directories, seamlessly storing or retrieving new versions of files as they appear (using Tahoe-LAFS’ “Magic Folder” feature [*] ).

  • Status indicators – the user will know, at a glance, the number of connected storage nodes, folder sizes and modification times, when folders are synchronizing, recently updated files, etc.

  • Desktop integration – Gridsync can (optionally) start automatically on login and provide desktop notifications when certain operations have completed.

  • Easy sharing – Gridsync uses the magic-wormhole library to provide human-pronounceable “invite codes” for joining storage grids and sharing folders with other users.

  • Simple recovery – Gridsync’s “Recovery Key” subsystem allows connections and folders to be easily restored from a single file in the event of a disaster.

  • Tor support (experimental) – Gridsync can tunnel outgoing connections through the Tor anonymity network, concealing users’ network location from storage service providers and each other.

Screenshots (latest release; running macOS 10.14 with dark mode enabled):

Screenshots (previous releases; running GNU/Linux with Xfce 4):

Installation and running:

Stable releases:

Downloads for “stable” releases of Gridsync can be found on the project’s GitHub Releases page and include pre-built/binary distrubitions for all three major desktop platforms that have been compiled inside dedicated virtual machines on dedicated hardware. Users wishing to install these packages are strongly urged to verify their signatures before running or, alternatively, to build/install Gridsync manually from source (see below).

To install and run Gridsync on GNU/Linux (64-bit only; supporting glibc 2.17 and above – including Debian 9+, Ubuntu 16.04 LTS+, CentOS 7+, and Fedora 28+):

  1. Download Gridsync-Linux.AppImage (and verify its signature)

  2. Make the AppImage executable (chmod +x Gridsync-Linux.AppImage)

  3. Run Gridsync-Linux.AppImage

To install and run Gridsync on macOS (64-bit only; supporting macOS 10.13 “High Sierra” and above):

  1. Download Gridsync-macOS.dmg (and verify its signature)

  2. Drag the enclosed “” bundle anywhere (e.g., ~/Applications)

  3. Double-click

To install and run Gridsync on Windows (64-bit only; supporting Windows Server 2012R2, Windows 7 SP1, Windows 8.1, and Windows 10):

  1. Download Gridsync-Windows-setup.exe (and verify its signature)

  2. Run the executable installer and follow/complete the setup wizard

  3. Select “Launch Gridsync” when installation is finished

Alternatively, Windows users who do not wish to use the executable installer can download and verify, extract the enclosed “Gridsync” folder anywhere, and run Gridsync.exe.

From source:

Because Tahoe-LAFS has not yet been ported to python3, and because some GNU/Linux distributions might contain especially old versions of some dependencies, it is recommended to install and run Tahoe-LAFS and Gridsync inside their own virtual environments using updated dependencies from PyPI (ideally with hashes verified).

The following series of steps (run from the top level of the Gridsync source tree) should work on most Debian-based GNU/Linux distributions:

sudo apt-get install build-essential libffi-dev libssl-dev python python-dev python3 python3-dev virtualenv
virtualenv --python=python2 ./venv2
./venv2/bin/python -m pip install --upgrade setuptools pip
./venv2/bin/python -m pip install tahoe-lafs
virtualenv --python=python3 ./venv3
./venv3/bin/python -m pip install --upgrade setuptools pip
./venv3/bin/python -m pip install -r requirements/requirements-hashes.txt
./venv3/bin/python -m pip install .
PATH=$PATH:./venv2/bin ./venv3/bin/gridsync

Users of other distributions and operating systems should modify the above steps as required (for example, by installing Xcode on macOS in addition to python – or the dependencies listed at the top of make.bat in the case of Windows).

Alternatively, users can use PyInstaller to generate a more “portable” binary distribution of Gridsync and Tahoe-LAFS (suitable for running on other machines of the same platform) by installing the required dependencies and typing make in the top-level of the source tree. This will create a standalone executable distribution of Gridsync and all of its dependencies (including a “frozen” python interpreter and Tahoe-LAFS), placing the resultant files/installers in the dist/ subdirectory.

Note, however, that PyInstaller-generated binaries are typically not backward-compatible; a PyInstaller executable that was built on a newer GNU/Linux distribution, for example (i.e., with a more recent version of glibc) will not run on older distributions. Accordingly, if you intend to distribute Gridsync binaries for use on a wide range operating system versions, it is recommended that you build the application on as old of a system as is reasonable for a given platform (i.e., one which can build and run Gridsync but which still receives security updates). Presently, CentOS 7, macOS “Mojave” (10.14), and Windows Server 2012 R2 arguably constitute the most suitable candidates for GNU/Linux, macOS, and Windows build systems respectively (insofar as binaries generated on these systems will be forward-compatible with all others in that platform-category that are still supported upstream).

To help facilitate the testing, building, and distribution of forward-compatible binaries – as well as to enable a crude form of “cross-compilation” – a custom Vagrantfile has been provided inside the Gridsync source tree; users or developers with Vagrant and VirtualBox installed [] can automatically provision a complete Gridsync build environment that produces forward-compatible binaries via the following commands:

make vagrant-build-linux
make vagrant-build-macos
make vagrant-build-windows

These will download and configure a suitable virtual machine for the target platform (from the public Vagrant Boxes catalog), provision it with all required dependencies (such compilers/SDKs, python interpreters, X11 libraries, etc.), copy the Gridsync source code into the target VM, run the Gridsync test suite, and compile a final PyInstaller-generated binary package suitable for distribution (the result of which can be found in the ~/gridsync/dist directory of the guest VM).

Development builds:

Unsigned binary distributions (currently tracking the master branch) are also available from the project buildbot’s “artifacts” directory. These packages, however, should not be considered trustworthy or reliable in any way and are made available only for testing purposes by developers. Please excercise appropriate caution when using these files (ideally by downloading and running them inside a disposable virtual machine).

Known issues and limitations:

While Gridsync ultimately aims to provide an easy-to-use frontend for users of Tahoe-LAFS, at present, its interface only supports a very limited subset of Tahoe-LAFS’s underlying features and potential use-cases (namely, it provides simplified means for joining storage grids, creating and sharing “magic-folders,” and receiving status updates and notifications pertaining to those processes). Accordingly, users should not (yet) expect Gridsync to provide a complete backup solution or to serve as a stand-in replacement for other tools with robust sharing and collaboration capabilities.

In addition, it should be noted that Tahoe-LAFS’s “magic-folder” functionality itself is currently considered “experimental” and has a number of known issues and limitations and open development tickets.


Contributions of any sort (e.g., suggestions, criticisms, bug reports, pull requests) are welcome. Any persons interested in aiding the development of Gridsync are encouraged to do so by opening a GitHub Issue or by contacting its primary developer:


Copyright (C) 2015-2020 Christopher R. Wood

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see <>.


The ongoing development of this project is made possible by the generous sponsorships provided by Least Authority and UXFund.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

gridsync-0.4.3.tar.gz (600.7 kB view hashes)

Uploaded source

Built Distribution

gridsync-0.4.3-py3-none-any.whl (614.7 kB view hashes)

Uploaded py3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page