Dynodoc is version control for documents, spreadsheets and presentations. Edits made in Word, Excel, PowerPoint and Google's editors become drafts and change requests, are reviewed and merged, and land in a hash-chained history that the server can verify.
Windows alpha 0.1.0-alpha.1, published 29 October 2026: a workflow manager with responsive panels, installed-agent CLI connections and the multi-project sync fix. Edit through your editors and add-ins. Prior Linux desktop builds remain at 0.0.1c; the hosted workspace runs its existing web tier.1
Works today
A standalone Windows alpha workflow manager that starts its own database and engine on your computer, with no server and no account: import of Word, Excel and PowerPoint files, captured changes, history with chain hashes and verification, drafts, change requests with review, comments, conflict choices and merge, restore, export, a watched folder, and backup and restore.1
Sign in to a server with your browser, link a project and sync it both ways, with a choice for each conflict. Every screen of the app can also read and change a real Dynodoc server.1
An agent that uses your own model provider and key or an installed official agent CLI (Claude Code, Codex, Cursor, Antigravity or Grok), with consent before the first send, caps and an offline switch. It proposes comments and commit messages as cards you press, and cannot approve or merge.1
A sample workspace of your own in the browser: three projects with their history, drafts, reviews and issues from invented colleagues. No account, it is removed after 24 hours, running the existing web tier separately from the Windows alpha.1
Add-ins for Word, Excel, PowerPoint, Google Docs, Google Sheets and Google Slides, installed by hand. None is on a Microsoft or Google marketplace yet, and installed-editor acceptance is not complete.2
Not there yet
macOS build, signed installers and automatic updates.1
Editing document content inside the desktop app. Today that happens in Word, Excel or PowerPoint on a copy, in the editor add-ins, and in the web workspace.1
No live model provider has been called with a real key: the agent was checked against a stand-in that speaks the three wire formats.1
Live account sign-in and subscription validation were not rerun in alpha acceptance; each official CLI owns its login.1
Engine: MIT
Windows x64 and Linux x64
macOS planned
Source on GitHub
Builds not code-signed
Try it
Open a sample workspace, or download the app.
A sample workspace of your own on the hosted pre-alpha server, with invented colleagues. It runs the current web tier; the Windows alpha desktop app does not need it. No account. It is removed after 24 hours, so do not put anything private in it.
Each paragraph, question, and spreadsheet row gets a permanent identifier when it is created.3,5 Edits are stored as typed events with an author, and each shared event is chained to the one before it with SHA-256.3,4 A restore adds a new event instead of rewinding the log.
How the record grows · illustration
Team versionv1
Field methods
NodeCreated5d1e…a09c
1 / 5 Maya writes the Sampling paragraph.
NodeCreatedMaya · 5d1e…a09c · prev 0000…0000
Illustrative names and shortened hashes. Draft revisions stay private and outside the team chain until shared; each shared event's hash covers its content, its author, and the previous hash.
Version control in everyday language.
01
Work where you already work
Edit in Word, Excel, PowerPoint or a Google editor, or in the web workspace. The add-ins capture your changes as drafts.
02
Make a personal draft
Try a change without altering the shared team version. Keep some work private while sharing selected changes.
03
Review the difference
Compare versions, see attribution, and resolve overlapping edits before combining the work.
04
Keep the record
Save named versions and restore earlier content as a new recorded change. Restoration preserves the intervening history.
What the workspace covers
One workspace, an accountable history.
Projects with several files, a main version and private drafts per file, change requests, comparisons and history.2
Review with approvals against the project's rules, explicit choices for overlapping edits, merges and declines, and revert, cherry-pick or restore as a new recorded change.1
Roles for people, issues and labels, published copies, and an AI agent policy per project.1
Read-only imports from ODK Central, KoboToolbox, REDCap, SurveyCTO and SurveyMonkey, plus CSV or XLSX files exported from CSPro. An import creates a new document and keeps its provenance.2
Try it with representative files and the people who will review them. Format compatibility and the editor add-ins need acceptance testing against your actual workflow. Test uploads are limited to 3 MB.
For engineers
Inspect the engine.
The standalone Dynodoc Engine is published under MIT as an early 0.1 source release, written in Rust with PostgreSQL. It covers append, verify, replay, snapshots, and merge; it does not include the browser editors or any production data.3
Verification recomputes the chain from stored events. It detects an inconsistent recorded chain; detecting a wholesale rewrite also needs a hash you kept elsewhere.
Shelldynodoc-engine · verify and replay
# Build the MIT engine and check one document's recorded history.git clone https://github.com/ArefinAlter/dynodoc-enginecd dynodoc-enginecp .env.example .env # set PASETO_LOCAL_KEY and WEB_SERVICE_KEYtask up && task test # PostgreSQL 16 for the integration tests# Recompute the hash chain over the stored events and report any break.cargo run --locked -p engine-cli -- verify DOCUMENT_UUID# Rebuild the document state by replaying its events from the start.cargo run --locked -p engine-cli -- replay DOCUMENT_UUID
Sources
Evidence and further reading
Product claims on this page are checked against the Windows alpha release notes and the published repositories.
01
Dynodoc 0.1.0-alpha.1 release notes (opens in a new tab)GitHub, ArefinAlter/dynodoc · 29 October 2026The Windows and Linux alpha manager, responsive panels, official installed-agent CLI connections, multi-project sync fix and remaining acceptance limits.
02
Dynodoc: README and implementation status (opens in a new tab)GitHub, ArefinAlter/dynodoc · accessed 26 October 2026The editor add-ins for Word, Excel, PowerPoint and Google's editors, that they are not on any marketplace yet, the research-tool imports, and the open items.
03
Dynodoc Engine: README, guarantees and limits (opens in a new tab)GitHub, ArefinAlter/dynodoc-engine · 0.1 source releaseThe MIT engine's scope, its SHA-256 event chain and ULID node identities, the engine-cli verify and replay commands, and its stated limits: no CRDT, no offline replica, no external anchoring.
