Trust messy folders.
Bindhub keeps your intent centered on folders while the engine handles object storage, cache metadata, and future chunk transfer — whatever your folder actually contains.
Bindhub · folder continuity
Your code folder, already there.
Open another machine and the folder you trust is ready — source, context, machine state, and the bytes to keep moving.
One folder, continuous in one place.
apps/128 filesFully local
node_modules/2.4 GBPartial cache
.env1.2 KBSecret · policy
agent-work/remoteRemote-only
One folder, every machineSource & contextMachine stateLocal bytesFolder revisions
Shared folders
The folder is the product boundary.
One repo, many repos, no repo, nested apps, secrets, dependencies, generated files, agent work. Bindhub treats that as normal developer life instead of asking you to clean it up first.
Capture file versions often
Loom records individual file states frequently, then coalesces stable folder revisions at sync, restore, checkpoint, and merge boundaries.
Restore a coherent tree
Folder revisions describe a complete view of the tree without turning every edit into a whole-folder snapshot.
Machines
Move between computers without rebuilding context.
Machines are first-class. Each one needs a clear cursor, a known hydration state, and a trusted auth boundary before it can materialize or update a shared folder.
Cursor clarity
Machine, remote, and materialized-folder cursors explain what each side believes is current.
Checkpoint intent
Human labels and pins help you retain meaningful folder revisions without managing object internals.
Sandbox work
Humans and agents get isolated parallel workspaces that can merge back into a trusted shared folder.
Sparse and lazy storage
Know which bytes are here before pretending they are.
Cache entries record object byte availability separately from file versions and folder revisions — so a folder can be present long before every byte is local.
Remote-only
Metadata is known, but the object bytes are not local yet.
Partial
Some bytes are available while future chunk transfer fills gaps.
Fully local
The cache can serve the object without remote reads.
Pinned
Retention intent keeps important revisions from being pruned.
Product and engine
Bindhub is the product. Loom is the engine.
Bindhub is the product
You think in folders and machines — not protocol details or Git-only workflows.
Loom is the engine direction
The deeper sync and source-control model underneath: objects, file versions, revisions, cursors, and cache records.
Git still matters
Bindhub respects today's repos, but it is not built around Git as the only shape a folder can take.
Trust and safety
Continuity is only useful when the boundary is clear.
Bindhub needs plain behavior around secrets, generated files, authentication, and what is safe to hydrate on a new machine.
Secrets deserve policy
Secret detection and block policies should stop unsafe captures before object writes.
Auth stays server-owned
Browser code never passes WorkOS access tokens directly to the hosted Bindhub API.
Generated files need intent
Dependencies, caches, build output, and local overlays are useful, but they shouldn't blur the trusted source boundary.
Developers and agents
Get your folder continuous.
Bindhub is heading toward sandboxes for human and agent work, with merge points that make folder state, overlays, and machine identity explicit. Request alpha access and tell us the folder you want continuous.