Gstore View source

Pool your Google accounts into one drive.

Gstore links the accounts you already own and presents their free space as a single store on your desktop.

Download What’s new View source

45 GB one combined space
  • personal 15 GB
  • college 15 GB
  • old backup 15 GB
  • pooled by Gstore 45 GB
Example: three of your own accounts on Google's free 15 GB tier. Gstore reads the real quota of each one.

How it works

  1. 1

    Link your accounts

    Sign in to each Google account you own and want to use. Two or more is where this starts to pay off.

  2. 2

    Gstore reads each quota

    It asks Google how much space every linked account has and how much is still free, then adds them up.

  3. 3

    Uploads spread out

    New files go to an account with room. A file too big for any single account is split into chunks across several.

Download

This is early software, so expect rough edges. Version 0.1.0 — see what changed. Runs on macOS 11 or later, 64-bit Windows, or 64-bit Linux.

macOS looks like your platform

The two Mac builds are not interchangeable, and the wrong one will not run. If you are not sure which chip you have, check the Apple menu, then About This Mac.

Windows looks like your platform

64-bit Windows 10 and 11. There is no 32-bit build, and no installer: you unzip it and run it.

Linux looks like your platform

A tarball carrying its own Qt, so it runs on most current distributions without installing anything else. Keep the binary beside its files.

Each button downloads the current build straight from GitHub. Older versions, checksums and release notes are on the releases page. You will also need the Google accounts you want to pool; Gstore does not create accounts for you.

First launch

Neither build is signed with a paid Apple or Microsoft developer certificate, so both systems will warn you the first time you open Gstore. The source is public instead, so anyone can read what goes into a build. Here is what you will see, and what to do about it.

macOS

  1. Open the .dmg and drag Gstore into Applications.
  2. Open it. macOS blocks the first launch and says it cannot check the app for malicious software.
  3. Go to System Settings, then Privacy & Security. Scroll to the notice about Gstore and click Open Anyway.
  4. Gstore then asks for your login keychain password once, so it can store its encryption key there. Choose Always Allow and it stops asking.

Recent macOS versions removed the old right-click and Open shortcut, so the Privacy & Security panel is the only way through.

Windows

  1. Unzip the folder, then keep it in one piece.
  2. Run Gstore.exe from inside that folder. It needs the files next to it, so it is not a single portable exe you can move on its own.
  3. SmartScreen says "Windows protected your PC". Choose More info, then Run anyway.

Put the unzipped folder somewhere permanent before you make a shortcut to it.

Linux

  1. Extract the archive and keep the folder in one piece: tar -xzf Gstore-linux-x64.tar.gz
  2. Run ./Gstore/Gstore. There is no warning to dismiss.
  3. Gstore stores its encryption key in your desktop keyring, so a session with one running (GNOME Keyring, KWallet) is needed.

The Linux build is new in 0.1.0 and has had the least testing of the three. If it misbehaves, the log file named in the README is the place to look.

There is no server in the middle.

Gstore runs on your machine and talks to Google's APIs directly. File contents move directly between your device and Google, and nothing is sent to or stored by the developer. There is no analytics, no telemetry and no third-party SDK in the build. The one exception is an update check: at startup Gstore asks GitHub whether a newer version exists, which carries no account information, no file names and no identifier, and can be switched off. It is described in full in the privacy policy.

Credentials are encrypted at rest

Your Google tokens are encrypted with Fernet, and the master key is kept in your operating system keychain rather than on disk in plaintext. Gstore encrypts those credentials, not your file contents; files sit in your own Google accounts under Google's protections.

A narrow Google permission by default

Gstore asks for the drive.file scope, which only covers files Gstore itself put there. It is not asking to read the rest of your Drive. Browsing everything already in your accounts is an optional advanced mode that needs a broader permission you would have to grant on purpose.

No account to create

There is no sign-up, no email address, no license key and no update server to check in with. You link your own Google accounts, and a Google account is the only thing you need to bring.

Open source

The whole app is on GitHub. Read it before you trust it, build it yourself if you would rather not run someone else's binary, or fork it and change what you want.