Built on Cloudflare

Dropbox for your code.

easy. fast. secure.

Passive sync for developer workstations. Your working tree and Git state stay encrypted and current across every machine; dependencies, build output, and anything you choose are ignored.

Get started Sign in

~/code/ — rbox

$ rbox setup
? Are you new here, or do you already have an rbox account?
  Create a new account
? Account bootstrap secret (left blank for browser signup)
? Set up encryption on this first machine now? Yes
✓ encryption enrolled · recovery phrase shown — save it safely
? What do you want to track here?
  Create a new workspace from a directory
? Which directory should rbox sync? ~/code/
? How should rbox handle gitignored files?
  Skip gitignored untracked files (recommended)
✓ files published · end-to-end encrypted
? Keep syncing in the background?
  Start background sync now and on machine boot (recommended)
✓ background sync started · autostart enabled

Getting started

Set up once. Pick up anywhere.

Install rbox, then run rbox setup. It signs you in, enrolls encryption, and creates your first workspace. The recommended choice starts encrypted background sync and resumes it after reboot.

First machine: rbox setup. Next machine: run rbox pair on the first, then rbox setupon the new one and paste the token.

$curl -fsSL https://rbox.to/install.sh | sh

Works on Apple-silicon macOS and Linux (x64/arm64).

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.

01
Stop copying work between machines
Edit on one machine and pick up on another. No archives, manual transfers, or wondering which laptop has your latest work.
02
Skips dependencies and build output
node_modules, build output, and secrets stay out by default, so rebuildable files don't waste bandwidth, storage, or time. Root .gitignore rules apply by default; setup can also honor nested rules, with .rboxignore for sync-specific choices.
```
# .rboxignore — gitignore syntax
*.log
scratch/
!scratch/keep.md
```
→ How this compares with Dropbox ignore rules
03
Back up code without handing us the keys
Your files are encrypted before they leave your machine. A storage-provider breach — or rbox itself — can't expose your code.
→ How our encryption works
04
Keep agents from starting with stale code
Give writing agents individual keys, or share one across a pull-only fleet. Every environment starts from your latest working tree without a browser login. Beta.
```
$ rbox setup --workspace=myapp --daemon --pull-only
```
→ Agents & CI docs

Built for repositories, not generic folders. Dropbox and Syncthing sync files; rbox understands what belongs in a working repository. It skips rebuildable dependencies, notices lockfile changes, and carries uncommitted Git state between machines.

Git-aware by design

Your checkout follows you.

Branches, uncommitted changes, the index, and stashes move together. If another machine has local work, rbox waits instead of overwriting it.

Pricing

Storage for code, not `node_modules`.

Dependencies and build output never sync, and version history doesn't count against your quota. Your storage goes toward the code you're actually working on.

Solo

For you and every machine you use

$80$8/ year/ month($6.67/mo)

Choose Solo

First subscription: 14 days free · Card required · Cancel anytime

50 GB storage
Unlimited workspaces
30-day version history
Email support

Pro

More storage and a full year of history

$200$20/ year/ month($16.67/mo)

Choose Pro

First subscription: 14 days free · Card required · Cancel anytime

250 GB storage
1-year version history
Priority support

Coming soon

Team

Shared storage, roles, and audit logs

$12/ user / mo

Coming soon

150 GB / user pooled
Roles & permissions
Audit log
90-day version history

Measured, not marketed

The software gets out of the way.

On large transfers, your connection and hardware set the pace — not rbox. Everything remains end-to-end encrypted along the way.

Workload	Measured result
120,000-file repo · 9.7 GB	~3m 47s until files are usable on a new machine
Edit on one machine → applied on another	~17s · p50 16.7s over 233 events
Server accepts a change	~281ms · down from 6.6s earlier that week
Checkout follows to another machine	~71s · branch, HEAD, index, and stash
Large-file upload	As fast as the connection allowed

Methodology: measured July 13, 2026 on the live fleet using v1.6.0 with shipped defaults. Full history attached in the background.

Your work, ready on every machine.

Close the laptop. Open another machine. Pick up where you left off.

Start syncing View pricing

Dropbox for your code.

Set up once. Pick up anywhere.

Sync built for how code actually lives.

Stop copying work between machines

Skips dependencies and build output

Back up code without handing us the keys

Keep agents from starting with stale code