Get your memory onto every machine you work on.

Your Shared Memory is built on the machine where you did the work, which means every other machine you code on starts empty again. Personal Sync carries the same canonical memory to every machine you work on, encrypted on the device before it leaves and readable only on machines you approve. Local recall and plaintext memory never move into the hosted service.

Start Personal Sync →Read the setup guide →

Connect the machine that has your memory

Run docmancer cloud connect on the machine that has your memory and authorize it in the browser. It creates and checks a recovery kit, shows the kit once for offline storage, and starts the first encrypted upload automatically. The account page then asks for a payment method to start the 30-day trial. There is no separate recovery verification or first-sync step.

Add a VPS or second machine

Install Docmancer, run docmancer setup, and run docmancer cloud connect with the same account. The new machine shows a four-word code. Run the same command on an already connected machine to compare and approve it, then run connect once more on the new machine to download memory. Use docmancer cloud connect --recover only if every connected machine is unavailable.

After the trial

Your selected monthly or yearly plan begins automatically unless you cancel. A failed renewal has a fixed 7-day upload grace period, followed by 30 days of read-only pull and export before hosted ciphertext is scheduled for deletion. Local Docmancer remains free and fully usable throughout.

What Personal Sync includes

Encrypted sync across every personal machine you approve
Managed encrypted revision history and recovery wrappers
Device approval, revocation, export, and remote deletion
Account and billing controls on docmancer.dev

What remains free

Local discovery, grounded Ask, Shared Memory, and Library
CLI, MCP, web app, capture hooks, and agent integrations
Local Markdown memory, revisions, history, and export
Every local retrieval and memory-quality improvement

Failure is local-first

If the sync service is unavailable or a subscription lapses, local recall and capture continue. Pull and export remain available during the final download window, and disconnecting returns you to the complete local workflow.

The local interface

Run docmancer web inside a project for the human interface. It binds to loopback, uses the same local memory as connected agents, and never accepts actions from the hosted account site.

Cryptographic boundary

Each device holds private keys. The service receives ciphertext, signatures, wrapped workspace keys, opaque references, and delivery metadata. Memory text, query text, and local paths remain on approved devices. Email login alone cannot decrypt an existing workspace.