Why Rig keeps your code on the Mac
Every cloud dev environment makes the same opening move: give us the repo. Rig makes the opposite bet. Your source never leaves the Mac it lives on — the cloud only ever sees the shape of your setup.
That single decision drives most of the architecture. Sync becomes cheap, because preferences and project registries are kilobytes. Security review becomes short, because there's no code custody question to answer. And a stolen laptop is an afternoon's inconvenience, not a client phone call.
Sync the setup. Never the source.
What does sync, then? Three things: the project catalog (names, scripts, tags — not paths), device presence, and Continuity packages — your env profiles and secrets, encrypted on-device before upload with a key we never hold.
→ catalog: { name, script, tags }
→ continuity: aes-256-gcm ciphertext
✗ /Users/…/Code/** — never leaves diskThe trade-off is honest: Rig can't run your code for you in the cloud, and won't pretend to. What it can do is make every Mac you own feel like one machine — which, for agency work, is the problem that actually hurts.
More in the docs: Cloud sync & Continuity and Live Link.