Product overview

Every change named, every version kept, and a sign-off only a person can give.

People and agents draft and suggest side by side. Reviewers comment on the rendered page, someone with edit access accepts or rejects each change, and a person signs off on one exact version — on plain files that stay yours, wherever they live.

Install free Read the FAQ

One document, end to end

Five steps, and the document never leaves its file.

Draft, ask an agent, review in place, decide, keep — the same shape whether you are alone with three agents or eleven people and a deadline. Each section below looks at one of these steps up close.

A five-step flow across four swimlanes — author, AI agents, reviewers and guests, and approver. Step one, draft the file in place. Step two, ask an agent, which returns suggestions signed with its own name. Step three, reviewers and guests question and suggest on the rendered text. Step four, a human accepts or rejects and the approver signs off on one version. Step five, the save is kept as a restorable version. Accepting suggestions can be delegated to an agent by a person; approving, restoring and sharing are always human acts. — At no point does the document leave your machine unless you switch sync on for that workspace.

See how it all works →

Sign-off

Ask for a sign-off, and know exactly what was approved.

Turn ‘could you look at this?’ into a tracked request with a recorded answer.

A named request with a due day

Ask for sign-off… names the people, with an optional note and due day; on a hosted account they're emailed the ask.

Pinned to one version

Every approval records who approved which version, and greys out when the text changes.

External stays external

A guest's approval is marked external and reads “Awaiting an internal sign-off” until someone in your organization approves.

Waiting on others

Waiting on others lists your open sign-off requests, unanswered questions and pending suggestions.

A phone review queue

In a phone browser, approve the exact version named on the card, or reply, with five seconds to Undo.

Version history

Never lose work, even when two people edit at once.

Every version is kept, restoring one takes a click, and when two edits collide you're told — nothing is silently resolved.

Every version kept

Nothing is pruned to save space. Each save is a version with an author and a time on it — yours, a teammate's, or an agent's — back to the very first.

Restore is one button

Restoring an earlier version makes it the current document as a new version, so nothing is destroyed by restoring. Nothing to untangle by hand.

Collisions are flagged, never overwritten

If two edits land on the same document at the same time, DraftMesh keeps both and tells you there's a conflict to resolve — it never picks one silently and discards the other.

Approvals pin to a version

A sign-off records who approved and exactly which version they approved. When the document moves on, the approval visibly goes stale rather than quietly covering new text.

The DraftMesh version history panel listing saved versions of a document, each with its author and the time it was saved, with a prior version open in a read-only preview beside Compare with current and Restore. — The history panel: a list of versions, who saved each one, and a button that brings one back. That is the entire interface.

Suggested edits

Propose a change. Someone with edit access accepts or rejects it.

A suggested edit attaches to the document like a comment, and the live text stays as it is until someone with edit access accepts the change.

How a suggestion moves through review

A reviewer selects text, proposes a replacement, and the suggestion sits alongside the document as a pending change. The owner reads it in place, then accepts or rejects it with a single click, right where the reviewer left it.

Commenting

Comment on markdown the way you actually read it.

Highlight the formatted words on the page, not the raw syntax underneath. The comment stays attached to those words, even as the text around them is edited.

No translating between page and source
GitHub pull requests make reviewers translate formatted prose back onto raw markdown. That translation step is where reviewers give up.
Comments don’t vanish on edit
Confluence comments disappear when a page is edited or retitled. A DraftMesh comment stays attached to its words through ordinary edits nearby.
Attached to words, not line numbers
A comment is tied to the text it quotes, so it survives reformatting, rewrapping, or the paragraph moving elsewhere in the document.

policy-checklist.md

Policy Readiness Checklist

Support needs two business days of lead time before the policy change takes effect.

Priya · Support lead

Make it three days — we still need to brief the on-call rotation.

Beyond prose

Share a live dashboard and let stakeholders comment on it.

An .html document renders as a real page people can comment on and approve. A .json file holds the numbers behind it.

HTML renders, and takes comments
The page renders in a sandbox — styles and scripts work, but the page cannot reach anything outside it. Reviewers highlight the rendered content and comment on it, and the document can be approved like any other.
JSON is the data underneath
A data file opens as a browsable tree. DraftMesh refuses to save invalid JSON — from you or from an agent — so a typo cannot silently break the dashboards reading it.
The page updates when the data does
An HTML document can read JSON from its own workspace and redraw the moment the file changes. Edit the numbers in DraftMesh, from a script, or with an agent, and every open page updates.
Versioned exactly like prose
All three types carry full history, so "who changed this number, and when" has the same answer as "who changed this paragraph".

An HTML dashboard document rendered inside DraftMesh, showing charts and figures drawn from a JSON data file in the same workspace. — An .html document reading a .json file from the same workspace.

Markdown is the only type that takes suggested edits — the full capability matrix is in supported file types.

Your files, your disk

Plain files you can open anywhere, with nothing to export.

Your documents live in a folder you choose. DraftMesh reads and writes the same ordinary .md, .html and .json files any other tool can open — and on markdown, the comments travel inside the file itself.

Portable by construction

A DraftMesh document is an ordinary file — a .md, .html, or .json. Open it in Vim, VS Code, a browser, or any other tool and every byte is there.

Nothing to migrate away from

Your content isn't held in a proprietary database, so there is nothing to move out if you stop using DraftMesh.

Comments live inside the file

Comments are stored inside the markdown as HTML comments that don't show when rendered, so sending the file to someone sends the review with it.

Offline-first

Works the same with no connection at all.

The free local app never goes to the network to open or save a document. It isn't waiting for a connection to come back — airplane mode, an air-gapped machine, or dead Wi-Fi all behave the same.

Install free

Questions about how DraftMesh works

How is commenting different from GitHub or Confluence?

GitHub PRs force you to map rendered content back onto raw Markdown source — reviewers who don’t read markdown fluently give up. Confluence comments vanish when the page is edited or retitled. DraftMesh anchors comments to the rendered text span itself, so they survive edits to the surrounding prose.

What happens when two people edit the same document at once?

Both edits survive. DraftMesh never silently overwrites one person’s work with another’s. When two changes collide, DraftMesh tells you and you decide what stays — nothing is dropped without your knowledge.

Do I need to be technical to use version history?

No. You see a list of saved versions with an author and a time on each, and a button that restores one. No developer jargon, and no commands to type.

Where do suggested edits and comments actually live?

Inside the markdown file itself, as HTML comments that don’t show when the document is rendered. There’s no separate record to fall out of sync with the document — send the file to someone and the comments go with it.

Does DraftMesh require an internet connection?

Not for the free local app. It reads and writes files on your disk, so it works the same in airplane mode, on an air-gapped machine, or with no Wi-Fi.

Will my documents still be plain files if I stop using DraftMesh?

Yes. There is no export step, because there is nothing to export from. Your files were already ordinary .md, .html, and .json files in a folder you chose — uninstalling DraftMesh leaves them exactly as they are, comments and all.

Can I do this with anything other than markdown?

Yes. Markdown (.md) supports comments, suggested edits and approvals. HTML (.html) supports comments and approvals, but no suggested edits. JSON (.json), CSS (.css) and JavaScript (.js) can be edited in Source and keep history and sync without review annotations. Office files (.docx, .xlsx, .pptx) are previewed without editing or review; Google references (.gdoc, .gsheet, .gslides) point to documents opened in Google. Office files and Google references also keep history and sync.

See supported file typesfor the full editing, preview and review matrix.

Good work. Woven together.

The local app is free forever — no account, no upload, no card. Your markdown never leaves your machine.

Install free Compare plans

Free forever, local, no account