Markdown collaboration for people who don't speak GitHub.
Your boss, client, and legal team don't live in repos. Seal gives each of them an AI summary of the doc written for their role, and a clean page to comment and sign off — right in the browser.
Any .md file · reviewers need no repo or GitHub · in your repo or in the browser
Your agent writes a 40-page PRD. The people who must sign off — your manager, a client, legal — don't live in the repo. So it just sits there.
written by your agent — opens in Seal for review
What your reviewer opens — a summary written for their role, the document beside it, and one place to comment, suggest, and sign off. No GitHub, nothing to install.
Open this review live — no signup →
Comments pin to the text, not line numbers. Edit the doc and the comment still points at the right idea — never orphaned to a stale line.
Everyone gets a brief of what changed. Reviewers click to re-check just the diff instead of re-reading 40 pages — the thing Google Docs never tells you.
Suggest the exact change, old → new. Reviewers don't just comment — Accept lands the edit in your .md. No editor to learn, no write access to hand out.
Git underneath, Google-Docs feel on top. Your .md stays the source — no copy, no export, no fork.
Your agent's Markdown becomes a review page — reviewed, signed off, and committed back to your repo.
Need approval, not just review? Sign off in the browser — no agent.
The local plugin gives you role-tailored review, comments, and suggestions in your repo. seal publish adds the approval layer — paste a doc, send one link, and the boss, client, or legal reviewer who doesn't run an agent signs off in any browser, identity-verified. Nothing to install, on either side.
Free to start — for you and your reviewers.
Open in any browser
Send one link. Your exec, client, or legal reviewer reads, comments, and signs off — no agent, no repo, nothing to install.
Identity-verified sign-off
Sign-off is verified with WebAuthn — a named person approved, not an anonymous thumbs-up.
Bound to the exact words
Approvals bind to the doc's content hash and go stale the moment the text changes — a tamper-evident record. Encrypted at rest; only people you invite can open it.
Questions
Can I use Seal to collaborate on Markdown files with my team?
Yes. Seal turns any .md file into a shared review page where your whole team can comment, suggest changes, and sign off in the browser — like Google Docs, but for Markdown, and with no GitHub or repo required. The free local plugin works with Claude Code, Cursor, Codex, and Copilot; the hosted tier adds identity-verified approval for reviewers who never touch a repo.
Can I edit Markdown in Seal, or is it review-only?
Review, comment, and suggest — not a text editor. The doc is authored upstream, by you or your agent; Seal is where humans weigh in and sign off. Reviewers can suggest an exact change (old → new), and Accept lands it in your .md — a proposal, not free authoring, always human-gated. No editor to learn and no write access to hand out.
Why not just use Google Docs?
A thumbs-up in Google Docs is frozen the second you give it — the file moves on and no one tells you. With Seal, the moment anyone edits what you approved, it comes back to you to re-check before it counts again.
What happens when the document changes after I approve it?
Whether a teammate or an AI agent makes the edit, your approval lifts on the part that changed and comes back to you — just that part, not the whole doc. Nothing moves forward carrying your name unless it still matches exactly what you saw.
Is Seal a separate app, or does it plug into Google Docs or Notion?
Two ways in. Free & local: point your AI agent (Claude Code, Cursor, Codex, Copilot) at a Markdown doc and /sealmd opens a review page right in your repo — nothing to paste, no add-on, and it commits back. Hosted (seal publish): when you need verified, off-repo sign-off, import or publish the doc and invite reviewers — nothing for them to install.
Do reviewers need an account?
For the local plugin, no — reviewers open the page in your repo to comment and suggest, with git history as the audit trail. Formal approval lives in hosted seal publish: reviewers create a free account so sign-off is identity-verified — and reviewers never count toward a paid seat.
Is it free to try?
Yes — the local tier is free and open-source forever (MIT), runs in your repo via your agent, no card and no account. The hosted seal publish tier is free to start too: browser-only, up to 3 authors, your first identity-verified seal on us — no card.
Is there a free, local version?
Yes — sealmd is open-source (MIT): two Markdown files in your repo, no SaaS, no account. The review file makes no network calls; the live page is served by a local server bound to 127.0.0.1 and token-authenticated — a server, but only on your machine. Works with Claude Code, Cursor, Codex, and Copilot. seal publish adds a hosted shareable link and your first identity-verified seal free; you pay only for scale and durable evidence — more authors, recurring cross-author sign-off, and a tamper-evident audit trail.
Is a Seal approval a legal signature?
Approval is hosted-only. On seal publish it's a defensible internal record — proof a verified person approved exactly these words, unchanged since without re-approval. The local plugin does review, comments, and suggestions, not formal sign-off. Neither is an eIDAS/DocuSign legal e-signature, and we won't pretend otherwise.
Get the right people to actually review what your agent wrote.
Free & open-source, runs in your repo via your AI agent — no account, no copy-paste. Need verified, off-repo sign-off? Your first hosted seal is on us.