Passive background sync
Run rbox daemon start once and it runs quietly in the background, streaming changes across every machine in real time — source, configs, and the messy in-progress work between commits. Set it and forget it.
Start the daemon once and rbox streams your working directories across every machine in real time — passive background sync you set and forget. Your uncommitted git state travels by default, end-to-end encrypted. Never your node_modules.
$ rbox daemon start
● passive sync on · watching ~/code/api · 3 machines
source + configs streaming live
node_modules, dist/ ignored out of the box
$ rbox ignore "*.env" # keep secrets on this machine
✓ added to .rboxignore · the ignore list syncs too
$ rbox status
● synced 2s ago · idle · your CPU stays quietNo accounts to wire up first, no config to write. Run it, sign in, and point rbox at a directory.
curl -fsSL https://rbox.to/install.sh | shWorks on macOS and Linux. Windows via WSL.
File sync was designed for documents and photos. rbox is designed for repositories — it knows what's regenerable, what's secret, and what git is doing under the hood.
Run rbox daemon start once and it runs quietly in the background, streaming changes across every machine in real time — source, configs, and the messy in-progress work between commits. Set it and forget it.
Your files are encrypted on your machine before they sync — our servers never see your code. Secrets like .env and keys are excluded by default.
Your uncommitted index, stash, and detached HEAD travel with you by default — end-to-end encrypted via git bundle. Pick up on any machine exactly where you left off.
Your code syncs — not the gigabytes that rebuild from it. node_modules, build output, and caches are skipped automatically, so your storage and bandwidth go to what actually matters. A fresh machine rebuilds them locally in one command.
Not Dropbox. Not Syncthing. Both happily ship the gigabytes of dependencies you can rebuild from a lockfile, and neither understands an uncommitted git index. rbox reconstructs deps locally and moves working git state with git bundle — and the daemon stays a polite background citizen, so it won't peg your CPU mid npm ci.
Because rbox never syncs your dependencies, your quota goes a lot further than it would anywhere else.
Need more room? + $3/mo per extra 100 GB on any paid plan.
Close the laptop, open the desktop, keep typing. That's the whole pitch.