How do AI-generated doc PRs get into DraftView?

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.

Do my reviewers need a GitHub account?

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.

How does DraftView know which PRs were written by AI?

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.

What happens after a reviewer requests changes?

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.

Does DraftView replace GitHub, or lock us in?

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.

Can DraftView prove a human reviewed the AI's work?

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.

Can DraftView actually block a PR from merging until a human reviews it?

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.

Is DraftView free for open-source projects?

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.

Which documentation formats are supported?

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 use X platform for documentation. Can I still use DraftView?

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.

We use GitLab/Bitbucket. Can we still use your visual review engine?

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.

Is there a free tier or trial available?

Yes. DraftView is free forever for individuals and small teams. Reviewing PRs (public or private) is unlimited, and the free plan includes 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 reviewers, no credit card); when it ends you simply drop back to the free plan, and nothing pauses. Team is $29/month per organization with 5 active reviewers included.

Who qualifies for the open-source Team plan grant?

Public, community-run projects with an OSI-approved license. Open-source docs for a commercial product do not qualify.

Do we get Governance features with this grant?

No. Governance features are never included in the open-source grant.

ProductJuly 13, 20264 min read

DraftView Team Plan Is Free for Eligible Open-Source Projects

Community-run open-source projects can now apply for the Team plan at no cost. Add one verified link back to DraftView, apply from org settings, and our team will review your request.

Team plan, free for qualifying open-source projects

We are now offering the DraftView Team plan at no cost for genuinely community-run open-source projects.

This grant is for projects that are:

Public
OSI-licensed
Not documentation for a commercial product

If your project meets those requirements, you can apply from your org settings in DraftView.

What we ask in return

To keep the program sustainable, we ask each approved project to add one link back to DraftView.

Pick one method below, add it first, then submit your application.

The link is verified automatically when you apply and checked again periodically. Every request is then reviewed by a human.

Link-back methods (pick one)

1) README badge

Add this to your README:

[![Docs human-reviewed](https://draftview.app/api/badge/<your-org>/<your-repo>)](https://draftview.app)

2) Docs-site footer link

Add this to your docs site footer:

<a href="https://draftview.app"><img src="https://draftview.app/api/badge/<your-org>/<your-repo>" alt="Docs human-reviewed with DraftView" height="20" /></a>

3) DraftView Edit this page links

Point your docs site's Edit this page links to DraftView in this format:

https://draftview.app/edit?url=<original-file-url>

Setup guide: Edit this page integration guide

When you apply, we check the page URL you provide to confirm the links are in place.

What is not included

The open-source grant does not include Governance features.

If you need Governance capabilities, use a paid plan.

How to apply

Choose one link-back method.
Add it to your project site or repository.
Open your org settings in DraftView.
Submit your open-source Team plan request.

We will run automatic checks first, then a human reviewer will make the final decision.

Final eligibility note

We support open-source communities directly. We do not approve grants for open-source documentation that belongs to a commercial product.

If you are unsure whether your project qualifies, apply anyway and include context in your request.