Built on Cloudflare

Dropbox for your code.

Sync what you want, ignore what you don't. Start it once and it runs in the background — your files fully encrypted, your dependencies and build output ignored.

Get started Sign in

~/code/api — rbox

$ 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 quiet

The one-line install

Up and syncing in one command.

No 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 | sh

Works on macOS and Linux. Windows via WSL.

How it works

Sync built for how code actually lives.

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.

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.

End-to-end encrypted

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.

Git-state aware

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.

You decide what syncs

node_modules, build output, and caches are skipped automatically — and a one-line .rboxignore lets you exclude anything else: secrets, logs, scratch files, whatever. Your ignore rules sync across machines too.

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.

Pricing