BetaPrivate beta is open. Teams are onboarded in stages.

Branch a dock without rebuilding it.

Dock snapshots the filesystem before a normal archive. Any successful snapshot can seed a branch: a new dock with its own identity that starts from the exact same state.

Independent descendants
Changes to the source, a branch, or sibling branches never alter one another. Each branch is writable on its own.
Lineage you can trace
Every branch records the snapshot and dock it came from, so parallel work stays explainable.
Parallel agents from one setup
Prepare a repository, dependencies, and services once, then fan out many agents from the same starting point.
Same tier resumes fast
Same-tier branches resume from the snapshot. Cross-tier branches rebuild from disk, and Dock never silently moves you to a higher tier.

Questions

What is the difference between resume and branch?

Resume brings the same dock back under its existing identity. Branch creates a new dock from a snapshot, leaving the original untouched.

Can I move a dock to another tier?

Tiers are fixed per dock because snapshots cannot resume across backends. Branch the dock into the new tier instead.

Tell us what your agents need to run.

Private beta is open. Describe your workload and we will reply about access.