Pricing
Planned pricing for early-access builders.
We expect simple Basic and Pro plans after the hosted launch. Join early access now and help shape the limits before billing turns on.
Prices shown are representative placeholders and are subject to change. Early access is invite-based while the product hardens.
Basic
For solo devs working across a few machines.
- Up to 3 devices
- 25 GB mirrored
- 30-day version history
- Standard support
Pro
Your whole setup — every machine and every agent.
- Unlimited devices, plus agent & CI seats
- 150 GB mirrored
- 90-day version history
- Priority support
Every plan includes
- Full-fidelity mirror, .git and all
- End-to-end encryption by default
- Conflict-safe — never lose work
Annual billing and volume pricing coming at launch.
Trust
Built for source code, not random folder sync.
The important answers are simple: treesync does not replace git, does not read your code, and does not silently overwrite conflicts.
What happens after I join early access?
You get on the invite list for the first hosted treesync.dev rollout. We'll use the email only for early-access updates and invitations.
How is this different from Dropbox or iCloud?
treesync is built for source code, not generic files. It mirrors each repo's .git directory byte-for-byte, dedupes content across repos, and is end-to-end encrypted by default.
Does it interfere with git?
No. treesync doesn't wrap, rewrite, or proxy git. It mirrors the actual files on disk — including .git — so you keep using git exactly as you do today. There's no fragile git integration to break.
Can treesync read my code?
No. Your code is encrypted on your device before upload, and the keys stay with your devices. End-to-end encryption is on by default.
What happens on a conflict?
If the same file changes on two machines, treesync keeps both versions as sidecar copies rather than overwriting either one. You decide what to keep — you never silently lose work.
Which platforms are supported?
macOS and Linux today, with more on the way. A single mirror can span any mix of supported machines — your laptop, a remote build box, and the hosts your agents run on.
Is it good for AI agents?
Yes — it's a core use case. Agents can run on any machine and start from your exact, up-to-the-second workspace, and their changes sync back conflict-safe alongside yours.
Early access
Put your laptop, cloud box, and agents on the same working tree.
We are inviting developers already moving code between local machines, remotes, and AI-agent hosts.