AI draft, flagged by a reviewer: The most amazing review platform that revolutionizes your documentation workflow.

The human review layer for your AI‑generated docs.

AI writes the docs. DraftView is where a qualified human reviews, edits, and signs off before the change merges, and where the AI's response to that feedback gets verified. Built on top of GitHub.

Try on any public PR

Signing in only shares your GitHub name and email. DraftView can see a repository only after you install it there, and reviewers never need an account at all.

Works with any AI generator · Reviewers skip GitHub · $0 for public repos

Same move, real PR

Every AI doc PR gets read the way you just read that headline.

Reviewers comment and suggest on the rendered page. Each suggestion lands in GitHub as a native suggested change, and in the record as proof a person looked.

Read the story: what happens to a doc PR after the AI opens it?

draftview.app/r/api-v3-migration
Changed Files
docs/api-v3.md
guides/migrating.md
index.mdx
changelog.md
Status
In review

Migrating to API v3

API v3 introduces cursor-based pagination, a new auth header format, and deprecates the /v1/search endpoint in favor of /v3/query.

Breaking changes

  • Auth header now requires Bearer prefix
  • Pagination params changed from page/per_page to cursor/limit
  • Response envelope dropped; data is returned at root
  • Rate limits scoped per-token instead of per-IP

Migration timeline

v1 is deprecated on June 30, 2026. Migrate by then or requests will start returning 410 Gone.

Why now

Your AI opens doc PRs faster than your team can review them.

Writing got automated. Review did not. Every agent your team uses feeds the same merge button. What sits in front of it decides how much of that text a person ever reads.

Your gate
showing each gate · pick one to stay

Someone clicks Approve. Nobody is asked to read the page.

Claude CodeGitHub CopilotCursorOpenAI CodexDevinWindsurfMintlifyPeopleAPPROVEREAD, ON THE RECORD · 0READ, NO RECORD · 0MERGED UNREAD · 20
  • From 7 AI agents and people · gate: approve
  • read, on the record: 0
  • read, no record: 0
  • merged unread: 20
A month of 20 doc PRs, 60% of them from agents, 3 reviewers asked on each. The EU AI Act asks you to show a person reviewed AI output (Article 14). Only the orange exit gives you that.Run it with your team's numbers

PR reviews

Every AI doc PR gets a state, an owner, and a person who read it.

  1. New
  2. In review
  3. Changes requested
  4. Waiting on AI
  5. Addressed
  6. Signed off
  7. Ready to merge
acme/api-docs #482AI-authoredopened by copilot-swe-agent

docs: migrate pagination guide to v3

docs: migrate pagination guide to v3New
Update auth header guideIn review
Add webhooks reference pageAddressed

team queue · 3 repos · nobody pasted a link

It arrives on its own.

Connect the GitHub App once. Every doc PR in a connected repo lands in one team queue, and DraftView notes when an agent wrote it.

A person reads the page.

The reviewer sees the rendered doc, not a diff, and comments where the problem is.

Feedback goes back as GitHub suggestions.

Comments and edits sync to the PR as native review threads and suggested changes.

The agent takes its turn.

The queue shows whose move it is, so a PR never sits with nobody owning it.

Did it actually fix it?

A push only counts as addressed when it touches the passage someone commented on. The reviewer gets the before and after, and confirms in a glance.

An approver signs off.

Who, when, against which version, and how long they spent reading. Appended, never edited.

Then, and only then, it's ready.

Green CI plus a current sign-off. The merge stays a human act in GitHub.

Doc reviewsPreview

Review the docs you already have, with the people who know them.

For docs already in your repository: no PR to start with, no GitHub needed to take part. Their accepted edits come back as one pull request.

acme/docs / security/data-retention.mdmain
maindoc review3 reviewers3 editsdecided
ReviewersTRTinamagic linkNBNeetamagic linkPNPrinceGitHub

Data retention

We keep application logs for 90 days and then delete them. Backups are encrypted and kept for 35 days.

Deleted data cannot be recovered.

No reviewers yet.

Start from the page, not a pull request.

Not every doc change begins as a PR. Pick a repo and the pages that need a second look, and share one link. The review runs in DraftView, beside main, and nothing touches your repo until you finish.

Invite the people who know the facts.

Security, Legal, the expert down the hall. They open a magic link from their inbox and review the rendered page. No GitHub account, and no Markdown, AsciiDoc or MDX to learn.

Edits arrive as suggestions.

Reviewers edit the page directly. Save shares the change with everyone as a proposal next to the text, with who made it. Nobody overwrites anybody.

A maintainer decides each one. Here, that's you.

Accept or reject the three edits, then finish. Undecided edits aren't lost: they go to the pull request as review comments.

Finish opens one pull request.

Accepted edits become one branch and one pull request into main, with the review record in the same commit. Your CI and branch protection take it from there.

The longer story of doc reviews

The closed loop

The loop GitHub never closes.

A reviewer comments. The agent pushes a commit. Whether it fixed what was asked, or just moved a line somewhere else, is the check everyone skips. DraftView makes it for you.

Try it. The agent's commit changed one paragraph. Drag the commit onto a paragraph, or pick one, and watch the verdict.

docs/api-v3.md

  1. API v3 introduces cursor-based pagination.

  2. v1 is deprecated in July 2026.

    Indy · WriterThe deprecation date is wrong. It's June 30, not July.
  3. before: Migrate before then or requests return 410 Gone.after: Migrate before the deadline or requests return 410 Gone.

Not addressed

The push changed paragraph 3, not the one Indy commented on. GitHub shows a fresh commit either way; DraftView keeps the PR waiting on the agent and sends Indy nothing.

For the reviewers who make or break it

No GitHub account. No problem.

PMs, Legal and SMEs can tell whether the AI got it right, and most of them will never have GitHub accounts. They join by email and review the page. Their words reach the PR as native suggestions.

  • Invited for free. Inviting and viewing never cost anything.
  • A GitHub-linked teammate verifies and pushes, so every suggestion comes from a real GitHub account.
  • GitHub stays the single source of truth. No second copy to reconcile.
docs/rate-limits.mdWhat GitHub receives
@@ -14,3 +14,3 @@ ## Rate limits
Every request counts toward a limit of 600 per minute.
Limits apply per IP address.
NAindy-jsuggested a change
- Limits apply per IP address.
+ Limits apply per token.

Sales confirmed this last week. Limits are per token now.

Review by Dom G. · verified & pushed by indy-j via DraftView

What Dom seessigned in by email

Rate limits

Every request counts toward a limit of 600 per minute. Limits apply per IP address token.

Dom G. · Product managerSales confirmed this last week. Limits are per token now.
← what Dom seesdrag the linewhat GitHub receives →

From conversations with technical writers

Senior Technical Writer · Enterprise software team
Getting PM reviews is the biggest problem for any doc-review workflow. Their feedback is disconnected from the original.
Documentation Lead · Help center team
We hate the duplicative Google Doc ‘article to source, then source to doc’ situation, but also kind of need it.
Senior Documentarian · Open source
I have never encountered someone with access to GitHub who can't get lost in convoluted source structure.

Oversight and governance

Turn “a human reviewed this” from a claim into evidence.

A green checkmark on a PR is a sentence, not proof. DraftView keeps the record GitHub doesn't: who read what, what they changed, and who signed off.

Append-only sign-off
Who reviewed, what changed, how long, against which version. Captured as it happens, never editable after the fact.
Substantive-review metric
The share of AI doc PRs that got a real human read, against the ones that were rubber-stamped.
Exportable for audit
Evidence of human oversight for EU AI Act Article 14 and procurement. One export, not a hunt through PRs and email.
Example recordappend-only
  1. 09:12Headlineaccepted Chloe's rewrite
  2. 09:13The gateput a read review gate on the doc PRs
  3. 09:15Doc reviewfinished with 2 of 3 edits accepted, one PR opened
Sealed when appendedsha256:··········…······
What's on screen nowsha256:··········…······

Seal matches

Accept the headline at the top, or select any text to comment, and your own actions replace this example.

This demo hashes in your browser. Notes you leave on this page stay in this browser only; nothing is sent. Real exports are sealed with HMAC-SHA256 on the server and can be checked under Oversight, Verify a record.

GitHub owns the content

No second source of truth. Comments, threads and review state sync natively.

Scoped access only

DraftView sees a repo only after you install it there. Signing in shares your name and email.

Never auto-merges

DraftView is the verification view for the AI loop. It is never the AI, and it never merges for you.

Pricing

Invite everyone. Pay only for active reviewers.

The full product is free forever for individuals and small teams. When the team grows, the bill counts the members who actually reviewed that month. Viewing is always free.

Try it. Here's a team of twelve on Free. Mark who reviewed this month, set your repos, and switch plans to see the bill.

Your team · this month2 of 12 reviewed
Repos in the queue
2
Base · Free, per org
$0
Active reviewers · 2, 2 included
included
Viewed only · 10 members
free
Repos in the queue · 2
up to 2

This month

Free covers up to 2 active reviewers and 2 repos.

$0/ mo

Free plan: $0 a month for 2 active reviewers and 2 repos. Free covers up to 2 active reviewers and 2 repos.

Prices in USD, per organization, before tax.

A year of doc review
Outside the PR, in Google Docs$61,800
DraftView Free, your estimate$0

A team reviewing 20 doc PRs a month in Google Docs spends about $62,000 a year of writer and reviewer time keeping docs and PRs in sync. Your estimate is $0 a year: nothing at all.

Run the numbers for your team

Drift cost from the calculator's defaults: 3 reviewers per PR, $85/h writers, $130/h reviewers.

Free

Your plan

Individuals & small teams

$0

Free forever, nothing ever pauses

Start free
  • Unlimited PR reviews: public and private, your own GitHub access
  • Review queue for 2 repos: doc PRs auto-ingested, AI PRs labeled
  • 2 active reviewers per month, sign-off recording included
  • Closed AI loop: see exactly what changed after your review
  • External review links + editing for Markdown, MDX, AsciiDoc
  • Google-Docs-style editing, zero Markdown needed

Team

The AI review loop

$29/ org / mo

5 active reviewers included · $10 each after

Start 14-day FREE trial

No credit card required · cancel anytime

  • 14-day free trial, full features, no card
  • Merge gate: a required GitHub check that blocks merging until a human signs off
  • Sign-off freshness: new AI pushes automatically reset a stale sign-off
  • Unlimited repos in the review queue
  • Invite unlimited reviewers, no GitHub accounts needed
  • Unlimited active reviewers (5 included, then $10 each)
  • Shareable sign-off certificates + review scorecard on every PR
  • Slack notifications for the whole review loop
  • CI-aware sign-off and ready-to-merge tracking
  • Free for community open source: apply for an OSS grant

Governance

Audit & compliance

$299/ org / mo

10 active reviewers included · $19 each after

Book a demo
  • Everything in Team, 10 active reviewers included ($19 each after)
  • Sealed, verifiable oversight records for every PR and doc review
  • Human-oversight report: substantively reviewed vs. rubber-stamped, by AI generator
  • Doc review oversight: reviewed-before-finish rate and self-approved edit alerts
  • Org-wide oversight ledger export (CSV or sealed JSON)
  • Rubber-stamp alerts when an AI PR merges without real review
  • Review-latency analytics: time from AI PR to first human review
  • Sign-off invalidation history in every audit export
  • Signed compliance webhooks for your GRC tooling
  • Built for EU AI Act Article 14 human-oversight evidence

Enterprise

For orgs at scale

Custom

Talk to our team

Book a demo
  • SSO + SAML authentication
  • GitHub Enterprise Server support
  • Self-hosted deployment option
  • Custom retention + procurement support
What's an active reviewer?
A member who submitted edits or comments, signed off, or pushed a teammate's review that month. Viewing is always free. Invite everyone, pay only for who reviews: an extra reviewer is $10/mo, less than five minutes of their billed time.
After the trial
You drop to the Free plan; nothing pauses or is deleted. The queue, the AI loop, and sign-offs keep working within Free limits, and your review history (including audit data) is kept.
Open source?
The Team plan is free for genuinely community-run open-source projects. Apply from your org settings. In return your project links back to DraftView (README badge, docs-site link, or “Edit this page” links, your pick). Open-source docs of a commercial product don't qualify, and Governance features are never included in the grant. Questions? ossgrant@draftview.app.
Annual billing
Team and Governance annual plans (20% off) are available on request: email us.
FAQ

Frequently asked questions.

Everything you need to know about DraftView. If your question isn't here, we're an email away.

Still have questions?
Email hello@draftview.app | we reply in 1 business day.
Connect the GitHub App to your organization once. After that, every documentation PR in a connected repo (public or private) lands automatically in a shared review queue with its own lifecycle state, so nothing gets pasted in by hand and nothing falls through. You can still load any individual public PR by URL when you just want to try it.
No. Reviewers join your organization by email with a magic link and start reviewing right away, with no GitHub account or password. A GitHub-linked teammate then pushes their feedback upstream under a real account, so every suggestion stays properly attributed. For one-off outside reviewers like legal counsel or localization, you can also share a password-protected external link.
DraftView reads signals from the PR itself: the author, branch name, description, and commit trailers. Detection is generator-agnostic, so it works whether the docs came from Claude Code, Copilot, Cursor, or an in-house pipeline, and it is held to a strict precision bar before a label ever drives a filter or a metric. The label flags a PR for human review. It never blocks or merges anything on its own.
Their comments and edits sync to GitHub as native review threads and Suggested Changes, so GitHub stays the single source of truth. When the agent pushes a new commit, the addressed view shows the before and after of the exact region they commented on, so the reviewer can confirm the feedback was really handled, not just that a line moved.
Neither. GitHub still owns your content, your comments, and the merge button. DraftView sits on top as a review layer you can add or remove at any time, and it never auto-merges. The one thing we keep that GitHub does not produce is the human-oversight record.
Yes. Every sign-off writes an append-only record of who reviewed, what changed, how long they spent, and against which version. You can export a per-PR oversight audit, and the dashboard reports the share of AI doc PRs that received a substantive human review versus those rubber-stamped. That is the evidence a green checkmark cannot give you, framed around EU AI Act Article 14 human oversight.
Yes, on the Team plan and above. DraftView posts a draftview/human-review status check on every doc PR in the queue: pending until a maintainer signs off, green once they do. Mark it a required check in your branch protection rules and GitHub will refuse to merge AI-generated docs that no human has approved. And the sign-off stays fresh: if the agent pushes another change to the docs after approval, the check flips back to pending and the reviewer is asked to look again; a trivial rebase or code-only commit carries the approval forward.
The Team plan is free for genuinely community-run open-source repos: public, OSI-licensed, and not the documentation of a commercial product. In return, your project links back to DraftView in one way of your choosing: a README badge, a link on your docs site, or DraftView-powered “Edit this page” links. Apply from your org settings: the link-back and license are verified automatically, and a human on our side approves each grant, so an enterprise publishing its product docs under an open-source license still uses a paid plan. OSS grants cover Team features only; Governance (audit exports, oversight metrics, compliance webhooks) is never part of the grant. If your request is declined and you believe that's a mistake, email ossgrant@draftview.app.
We currently support standard Markdown, MDX and AsciiDoc. AsciiDoc renders correctly, however some features may not be fully functional. We are actively working on improving AsciiDoc support. If you have specific format needs, please contact us to discuss how we can accommodate your workflow.
We support Docusaurus, Mintlify, GitBook, Hugo, MkDocs, and any other platform that uses a GitHub-based workflow. As long as your files are in a GitHub repository, we can render the preview.
Not yet. DraftView currently only supports GitHub. We are building integrations for GitLab and Bitbucket next. Contact us to request priority for your platform.
Yes, all data is encrypted at rest and in transit. We follow industry best practices for security and compliance, including SOC2 readiness. Your documentation, review sessions, and the human-oversight record are protected with enterprise-grade security measures.
Yes. DraftView is free forever for individuals and small teams: unlimited PR reviews (public or private) plus a review queue for 2 repos with 2 active reviewers per month. Connecting your GitHub organization starts a 14-day free trial of the Team plan (unlimited repos and invited reviewers, no credit card); when it ends you drop back to the free plan, and nothing pauses. Team is $29/month per organization with 5 active reviewers included. See pricing for full details.
Ready when you are

AI writes the docs.
You decide what ships.

See the experience on a PR you already know in about 60 seconds. No login, no card, no setup.

Try on any public PR

Signing in only shares your GitHub name and email. DraftView can see a repository only after you install it there.