Document control for specs & SOPs

Everyone works from the approved version.

Docs get edited without review, and teammates and AI agents end up reading the wrong copy. In VersoDocs, every change is reviewed and signed off before it goes live.

Free for 2 people · No card · Import from Google Docs, Notion and more

The problem

“Which version is current?”

  • Edits go live unreviewedAnyone with access can change the live doc. Nobody checks it first.
  • Nobody knows which copy is currentOld PDFs, forwarded attachments and “final-v2” files outlive every update.
  • AI agents read draftsAn agent pointed at a wiki page reads whatever is there, half-finished edits included.
  • No proof of who approved whatWhen an auditor or an incident review asks, the answer takes days to rebuild.
How it works

Propose. Review. Publish.

Code review, for documents. No git required.

01 · PROPOSE

Start a private draft.

“Propose changes” opens your own copy of the live document. Readers see nothing until you share it.

DraftOnly you can see it
Refund policy / Your draft
Raise refund window to 45 days
Draft
Editing your working copy · autosaved just now

Customers may request a full refund within 45 days of purchase. After that, refunds are prorated to the unused term. 

02 · REVIEW

Get it reviewed.

Reviewers see what changed, comment on the line, and approve or request changes.

✓ Approved↺ ChangesPending
03 · PUBLISH

Make it the new Current.

One click publishes v8 with its review attached. v7 is kept, locked and dated.

Published · v8Now the version everyone reads
Northwind / Policies / Refund policy
Refund & cancellation policy
Current · v8
Published by you · just now · from “Raise refund window to 45 days”

Customers may request a full refund within 45 days of purchase. After that, refunds are prorated to the unused term.

Features

Approved, then actually used.

For technical specs, SOPs, policies, and any doc people act on. Coming from Google Docs? See how they compare.

See exactly what changed

A clear before-and-after of every proposal. Each revision shows reviewers only what moved since their last look. Compare or restore any version.

Nothing goes live unapproved

The live document can’t be edited directly. Require sign-off before publish on every plan. Pro adds auto-publish once everyone approves.

One thread per change

Inline comments, @mentions and verdicts live on the proposal. On Team, invite a client, legal or QA to review free: no account, no seat.

Old copies flag themselves

Every export carries its version number and a link to check it’s still current. Old versions and share links show a “superseded” banner.

The team hears about itTeam

New versions post to Slack or Teams with who approved them, on every plan; on Team, reviewers approve from Slack and versions push to Notion, Confluence or Google Docs, with AI change summaries. Pro keeps Notion and Confluence pages in sync.

Owners, review dates, read receipts

Give each doc an owner and a review cadence, and schedule changes to go live on a date. On Pro, require people to confirm they read the new version.

Developers & AI agents

Ops updates the spec. Your agent pulls it.

Engineers and their agents read the version everyone signed off on. Reading works on every plan.

  • MCP for AI agentsConnect Claude Code, Cursor or Copilot in one click. The agent reads the Current version, never a draft.
  • CLI and GitHubnpx @versodocs/cli pull writes the approved Markdown into your repo. A workflow opens a PR when a spec changes; on Team, a check fails PRs built from an outdated spec.
  • Agents propose, people approveOn Team, agents can open proposals (25 a month; unlimited on Pro), and an AI reviewer on your own LLM key checks each one against your checklist. Your reviewers decide.

VersoDocs for developers →

~/checkout-service
# Pull the approved spec into the repo
$ npx @versodocs/cli pull eng/specs/checkout-api
✓ docs/specs/checkout-api.md  v13 · Current

# In CI: fail when a spec has moved on
$ npx @versodocs/cli check
docs/specs/payments.md      v4  v4   up to date
docs/specs/checkout-api.md  v12 v13  outdated

# Or ask your agent (MCP)
› pull the approved Checkout spec and implement §3
✓ get_doc checkout-api v13 · Current
Audit trail

A record you can show an auditor.

  • Every version explains itselfAuthor, reviewers, approver and reason, attached. Published versions are locked and dated.
  • Overrides are loggedAdmins can publish an urgent fix without approval. The override is recorded on the version.
  • Audit-ready exportsPro adds an org-wide audit log, e-signatures on approval, and CSV or ZIP exports for your auditor.
  • Your data stays yoursExport any document to Markdown on every plan. Team and Pro add PDF, Word and HTML.
Switch in minutes

Bring your docs with you.

Paste a link or drop an export. Folders and images come along, and docs can go live as v1 right away. On every plan.

  • Google Docs
  • Notion
  • Confluence
  • GitHub
  • GitLab
  • Obsidian
  • Coda
  • Slab
  • Dropbox Paper
  • Quip
  • Word
  • Markdown
  • PDF
Pricing

Start free. Upgrade when the team grows.

Free
$0
for 2 members · 1 workspace
  • Up to 10 documents (sample spec free)
  • Proposals, reviews & approval rule
  • Latest 3 versions visible per document
  • Import from Google Docs, Notion & more
  • Read-only API, CLI & MCP
Start free
Pro
$20 / seat / mo
billed annually · $24/mo monthly
  • Everything in Team
  • Full version history visible
  • Auto-publish on approval
  • E-signature on approval
  • Read-and-acknowledge
  • Org-wide audit log & export
  • 500 AI credits / mo
Start 14-day free trial

Compare all plans →

Start with one document.

Pick the one that changes most. Run its next change through review.