Dynodoc, version control for the documents your team edits together
Alpha 0.1.0-alpha.2 · published 8 November 2026. Windows and Linux desktop app. macOS is planned.
Edits made in Word, Excel, PowerPoint and Google's editors become drafts and change requests. They are reviewed, merged and kept in a history the server can verify.
Last reviewed
What works today and what is not there yet
Works today
- A desktop app for Windows and Linux that runs its own database and engine, with no server or account needed.
- Import of Word, Excel and PowerPoint files, with captured changes, drafts, change requests, review, comments, merge and restore.
- Two-way sync with a Dynodoc server after browser sign-in, with a choice for each conflict.
- Add-ins for Word, Excel, PowerPoint, Google Docs, Google Sheets and Google Slides, installed by hand.
- An optional agent that uses your own model key or an installed agent CLI. It proposes comments and commit messages, and cannot approve or merge.
Not there yet
- A macOS build, signed installers and automatic updates.
- Editing document content inside the desktop app. Today that happens in the editors, through the add-ins.
- Any add-in on a Microsoft or Google marketplace. Acceptance inside installed editors is not complete.
- A call to a live model provider with a real key. The agent was checked against a stand-in.
What Dynodoc is built to do
- Two people edit the same proposal at once.
- Built to keep each person's changes as a draft until someone reviews and merges them.
- A restore wipes out a week of work.
- Designed so a restore adds a new recorded change and keeps every edit in between.
- Nobody knows who changed a figure.
- Built to record each edit with its author, chained to the edit before it.
For your engineers
- Each paragraph, question and spreadsheet row gets a permanent ULID when it is created.
- Edits are stored as typed events with an author. Each shared event is chained to the one before it with SHA-256.
- The engine is MIT-licensed. It can recompute a document's hash chain and replay its events from the start.
- The engine states its limits: no CRDT, no offline replica and no external anchoring.
- The builds are not code-signed, so Windows SmartScreen warns before the first run.
See Dynodoc on a sample workspace
We walk through drafts, review and history on a sample workspace, and say plainly what the alpha cannot do yet.