# DocUp: docs written from your code, checked against it > DocUp writes user docs from your GitHub repo, checks every command, flag and variable against your source, and updates only the pages a push touches. Source: https://docup.dev/ DocUp (docup.dev) writes user documentation from a GitHub repository, checks every command, flag and environment variable against your source, and updates only the affected pages when you push. It hosts the docs with search and Ask AI. DocUp never runs your code: repositories are read as files, and nothing is installed, built or executed, on any plan. ## How it works 1. **Connect a repository.** Sign in with GitHub or Google and pick a public or private repo. 2. **Review the draft.** Every page is checked against your code before you see it. Anything that fails is fixed or held back. 3. **Edit what you like.** Change any section. Your edits are kept when the docs are regenerated. 4. **Publish.** Your site goes live on a docup.dev address or your own subdomain, with search and Ask AI built in. ## What DocUp will not do - **Never run your code.** Repos are read as files. Nothing is installed, built or executed, on any plan. - **Never keep private source.** For private repos, only hashes, extracted facts and a map of signatures are stored. The source is not. - **Never index private code for chat.** Ask AI on a private repo's site answers from the docs only. A database trigger blocks code chunks. - **Never link to private source.** Sites built from private repos never link to GitHub source. - **Never overwrite your edits.** An edited or locked section gets a suggestion, never a silent change. ## Pricing DocUp has three plans: Free, Pro and Team. Prices are in US dollars per month. Every plan includes sync on push, a docs site with search, and Ask AI. | Plan | Price | Repo size | Projects | Pages | Address | Ask AI | | --- | --- | --- | --- | --- | --- | --- | | Free | $0 a month | repos up to 50,000 lines | 1 project, public or private | 6 pages | your-project.docup.dev | 50 messages a month, as a trial | | Pro | $19 a month | repos up to 150,000 lines | 3 projects | 14 pages | Plus 1 custom subdomain | 3,000 messages a month | | Team | $79 a month | large repos and monorepos | 10 projects | 24 pages | Plus 5 custom subdomains | 15,000 messages a month | ## FAQ ### What is DocUp? DocUp (docup.dev) writes user documentation from a GitHub repository, checks every command, flag and environment variable against your source, and updates only the affected pages when you push. It hosts the docs with search and Ask AI. ### Does DocUp run my code? No. DocUp reads your repository as files. Nothing is installed, built or executed, on any plan. ### Can I use a private repository? Yes, on every plan including Free. Private source is never stored, only hashes, extracted facts and a map of signatures. Ask AI on those sites answers from the docs only, and the site never links to GitHub source. ### What happens when I edit a generated page? Your edits are kept. When your code changes, DocUp suggests an update for any section you edited instead of replacing it. Locked sections are only marked as possibly stale. ### How are docs kept current? A push to GitHub re-syncs the affected pages after a 10 minute wait, up to 8 pages per push. An hourly check catches pushes whose webhook never arrived. ### Can I use my own domain? Pro and Team include custom subdomains such as docs.example.com. Apex domains are not supported. ### Can I generate docs for a repo I do not own? For public repos, yes. The site is marked Unofficial, hidden from search engines, and shows a banner. The maintainers can claim the site or request a takedown. ### What happens when the Free chat quota runs out? Readers see a note that the site owner's free chat quota is used up. The docs themselves keep working. --- # DocUp Pricing: Free, Pro $19 and Team $79 a month > Free for one project. Pro is $19 a month and Team is $79 a month. See repo size, page, domain and Ask AI limits for each plan. Source: https://docup.dev/pricing DocUp has three plans: Free, Pro and Team. Prices are in US dollars per month. Every plan includes sync on push, a docs site with search, and Ask AI. | Plan | Price | Repo size | Projects | Pages | Address | Ask AI | | --- | --- | --- | --- | --- | --- | --- | | Free | $0 a month | repos up to 50,000 lines | 1 project, public or private | 6 pages | your-project.docup.dev | 50 messages a month, as a trial | | Pro | $19 a month | repos up to 150,000 lines | 3 projects | 14 pages | Plus 1 custom subdomain | 3,000 messages a month | | Team | $79 a month | large repos and monorepos | 10 projects | 24 pages | Plus 5 custom subdomains | 15,000 messages a month | --- # DocUp FAQ: Does it run my code, and can I use private repos? > Does DocUp run your code? Can you use private repos? What happens to your edits? Clear answers on how DocUp reads, writes and syncs your docs. Source: https://docup.dev/faq ## What is DocUp? DocUp (docup.dev) writes user documentation from a GitHub repository, checks every command, flag and environment variable against your source, and updates only the affected pages when you push. It hosts the docs with search and Ask AI. ## Does DocUp run my code? No. DocUp reads your repository as files. Nothing is installed, built or executed, on any plan. ## Can I use a private repository? Yes, on every plan including Free. Private source is never stored, only hashes, extracted facts and a map of signatures. Ask AI on those sites answers from the docs only, and the site never links to GitHub source. ## What happens when I edit a generated page? Your edits are kept. When your code changes, DocUp suggests an update for any section you edited instead of replacing it. Locked sections are only marked as possibly stale. ## How are docs kept current? A push to GitHub re-syncs the affected pages after a 10 minute wait, up to 8 pages per push. An hourly check catches pushes whose webhook never arrived. ## Can I use my own domain? Pro and Team include custom subdomains such as docs.example.com. Apex domains are not supported. ## Can I generate docs for a repo I do not own? For public repos, yes. The site is marked Unofficial, hidden from search engines, and shows a banner. The maintainers can claim the site or request a takedown. ## What happens when the Free chat quota runs out? Readers see a note that the site owner's free chat quota is used up. The docs themselves keep working. --- # DocUp Security: How Your Repository Is Read and Stored > How DocUp reads repositories without running them, what it stores for private repos, and how webhooks, sessions and billing are secured. Source: https://docup.dev/security Updated 2026-10-11. ## Your code is read, never run DocUp downloads a read-only snapshot of your repository and analyses it as text. Nothing from your repository is installed, built or executed, on any plan. Snapshots are unpacked safely: archives containing symbolic links or paths that escape the target folder are rejected. ## What is stored for private repositories Private source files are never stored. DocUp keeps only derived data, visible to the repository owner: - file hashes, used to detect what changed - extracted facts such as commands, flags, environment variable names and routes - a map of exported symbols and signatures - the generated documentation ## Secrets in repositories Files that commonly hold secrets, such as .env files, private keys and Terraform state, are excluded before any analysis. Remaining text is scanned for secrets and redacted before it reaches a language model or a search index. Generated output is scanned again before it is published. ## Untrusted repository content Repository text is treated as untrusted input. It is wrapped in per-run delimiters, the writing model has no tools, and output is limited to an allowlist of Markdown components and links. Instructions found inside a repository are never followed. ## GitHub access - Webhooks are verified with an HMAC signature and de-duplicated by delivery ID. - Installation ownership is verified before an installation is linked to an account. - Access tokens are minted per job, scoped to a single repository, and never stored. - Ask AI on a private repository's site answers from the documentation only. Sites built from private repositories never link to GitHub source. ## Accounts and sessions You sign in with GitHub or Google. Session cookies are limited to the app host, and no cookie is scoped to the shared docup.dev domain. Published documentation sites set no cookies for readers. ## Abuse protection Ask AI on published sites is protected by bot verification, session tokens, rate limits and per-site monthly quotas. Questions the documentation cannot answer are declined instead of guessed. ## Billing Payments are handled by Dodo Payments as merchant of record. DocUp never sees card numbers. Billing webhooks are signature-verified and processed idempotently, and plan limits are enforced on the server. ## Reporting a vulnerability Please report security issues privately and give us reasonable time to fix them before disclosure. A support address is published here before launch. Until then, reach us through the project repository's issue tracker. --- # DocUp Privacy Policy: What We Collect and How to Delete It > What DocUp collects and why, which providers process it, how cookies and local storage are used, and how to have your data deleted. Source: https://docup.dev/privacy Updated 2026-10-11. ## What we collect - Account details from GitHub or Google sign-in: your name, email address, avatar and the provider's account ID. - Repository data. For each connected repository: file hashes, extracted facts, a map of signatures and the generated documentation. Private source files are not stored. For public repositories, code fragments may be indexed so Ask AI can answer questions. - Usage data: page-view, visitor, referrer, country, browser and device counts per documentation site (counted when a page is served, with no cookies and no stored IP address or reader profile), product events from the DocUp website and app such as page views, clicks and sign-ups, and session recordings of how the website and app are used (all form fields are masked), Ask AI questions and answers with reader feedback, and generation logs recording the model, token counts and cost. - Billing data: customer and subscription identifiers and plan status. Card details are handled by Dodo Payments, not by DocUp. ## How we use it We use this data to generate, host and update your documentation, to answer reader questions, to enforce plan limits, to prevent abuse and to operate and improve the service. We do not sell personal data. ## Who processes it DocUp relies on these providers to run the service: - Cloudflare: hosting, DNS, object storage and bot verification - Supabase: database - Upstash: short-lived rate-limit and queue state - Trigger.dev: background jobs - Google Cloud (Vertex AI): language model processing of repository-derived content and reader questions - Dodo Payments: payments, as merchant of record - PostHog: product analytics for the DocUp website and app, sent through our own domain - Resend: transactional email - GitHub and Google: sign-in ## Cookies and local storage The app sets a session cookie so you stay signed in. Your theme choice is kept in your browser's local storage. The DocUp website and app keep an anonymous analytics identifier in local storage (not a cookie) and respect your browser's Do Not Track setting. Published documentation sites set no cookies for readers, and DocUp uses no advertising scripts or third-party tracking scripts on them. ## Retention and deletion If you uninstall the GitHub App or delete a repository, DocUp stops syncing it, purges its search indexes and deletes its data after a short grace period. If a repository changes from public to private, indexed code fragments are purged immediately and automatic publishing is paused. You can ask for your account to be deleted at any time. ## Unofficial documentation sites Anyone signed in can generate documentation for a public repository they do not own. Those sites are labelled unofficial and hidden from search engines. Repository owners can claim or request removal of such a site. ## Contact A support address is published here before launch. Until then, reach us through the project repository's issue tracker. --- # DocUp Terms of Service: Use, Unofficial Sites and Billing > The terms for using DocUp: your repositories and content, acceptable use, unofficial sites and takedowns, plans and billing, and availability. Source: https://docup.dev/terms Updated 2026-10-11. ## Using DocUp By creating an account or using DocUp you agree to these terms. You must be able to form a binding agreement and you are responsible for activity on your account. ## Your repositories and content You keep your rights in your repositories and in the documentation generated from them. You confirm that you have the right to connect each repository and to publish documentation derived from it. You give DocUp permission to read the repository, process it with the providers listed in the privacy policy, and host the resulting site. ## Acceptable use - Do not use DocUp to publish unlawful content, or content that infringes someone else's rights. - Do not attempt to access other users' data, bypass plan limits or quotas, or disrupt the service. - Do not use Ask AI or generation to send abusive or automated traffic. ## Unofficial sites, claims and takedowns Documentation generated for a public repository by someone who does not administer it is published as an unofficial site: labelled, hidden from search engines, and limited to one per repository. The repository's administrators can claim the site by installing the DocUp GitHub App, or ask for it to be removed. Removed repositories are blocked from being generated again as unofficial sites. ## Plans and billing Plans and limits are listed on the pricing page and may change for new subscriptions. Paid plans are billed monthly through Dodo Payments, our merchant of record. If you cancel, your plan stays active until the end of the paid period. If a payment fails, access continues for a short grace period before the account returns to the free plan. ## Availability DocUp is provided as is. We work to keep it available but do not promise uninterrupted service, and generated documentation can contain errors. Review generated pages before you publish them. ## Ending your use You can stop using DocUp and delete your account at any time. We may suspend or end accounts that break these terms. Deleting a project removes its published site. ## Liability To the extent the law allows, DocUp is not liable for indirect or consequential losses, and our total liability for any claim is limited to the amount you paid in the twelve months before it. ## Changes and contact We may update these terms and will note the date at the top of this page. Continued use means you accept the update. A support address is published here before launch. Until then, reach us through the project repository's issue tracker. --- # How to Verify AI-Written Docs Against Your Source Code > Check every command, flag, variable and link in AI-written documentation against your code. A manual checklist, and how DocUp automates it. Source: https://docup.dev/guides/verify-ai-written-docs AI writes documentation quickly. The risk is a command, flag or variable that reads well and does not exist. This is what to check, how to check it by hand, and how DocUp automates it. Updated 2026-10-12. ## Why AI-written docs go wrong A language model writes from patterns, so it can produce a plausible command, option or environment variable that your project does not have. Readers copy those lines into a terminal, and an invented flag costs them time and trust. A better prompt does not fix this. Checking every concrete statement against the source does. ## What to check - Commands and subcommands exist in your CLI. - Flags and options exist on the command they are shown with. - Environment variables and configuration keys are read somewhere in the code. - Install commands name your real package. - File paths, function names and other identifiers exist in the repository. - Links point to pages that exist. - Code citations point to lines that exist. ## How to check by hand - Search the source for every flag, variable and identifier the docs mention. A match proves it exists. No match is a defect. - Compare your CLI's own help output with the documented options, on a machine where you are happy to run it. - Run a link checker on every release. - Re-read a page whenever the code it describes changes. Note which source files each page covers so you know what to revisit. ## How DocUp checks it DocUp reads your GitHub repository as files and extracts facts from the code: CLI commands and their options, environment variable names, install commands and exported symbols. It does not install, build or execute anything, on any plan. Pages are written with markers that point at the source lines each statement rests on. A checker then compares the page with the extracted facts, and pages with defects go through a repair step. It looks for: - commands and flags the code does not define - identifiers, file paths and package names the repository does not contain - install commands that name the wrong package - links that do not resolve - line references that do not exist or cover too many lines - malformed Markdown and empty marketing words such as powerful, seamless and robust ## What automated checks cannot do A static check proves that something exists in the source. It cannot prove that an explanation is clear or complete, or that behaviour described in prose matches what the code does at run time. Read the draft before you publish it. How much can be checked also depends on what DocUp can extract from your repository. ## Checklist before you publish - Every command in the docs runs as written. - Every flag appears in the source or the CLI help. - Every environment variable is read by the code. - Every link opens. - Someone who did not write the code has read the page once. --- # DocUp vs Mintlify: Docs Written From Code or Maintained > A factual comparison of DocUp and Mintlify: where documentation starts, how AI is used, how drafts are reviewed, and which fits which project. Source: https://docup.dev/compare/mintlify Both tools produce hosted documentation sites, and both use AI. They start from different places. This page compares them using what each one publishes about itself. Updated 2026-10-12. ## The short version DocUp starts from your GitHub repository. It writes the first draft of user documentation from what the code does, then checks the draft against the code. Mintlify is a documentation platform where you write and maintain content, with an AI agent on its paid plans that can write and update pages. ## At a glance | | DocUp | Mintlify | | --- | --- | --- | | Where documentation starts | Your GitHub repository. DocUp plans and writes the pages. | Content you write and maintain in Mintlify. Its agent can draft from prompts, pull requests and other inputs. | | AI writing | Part of the product on the Free plan, which covers one project. | The agent is listed on the Pro and Enterprise plans. | | Review | Automated checks against facts extracted from your code, then your own review and edits. | By default the agent opens a pull request for each change so your team can review it. CLI checks confirm the docs build. | | Your repository | Read as files. Nothing is installed, built or executed. | The agent can read repositories connected through the Mintlify GitHub App. | | Hosting | A hosted docs site on a docup.dev address. | Hosted docs. A custom domain is listed on the Starter plan. | | Cost | A Free plan for one project. Paid plans are not available yet. See the pricing page for the planned plans. | A free Starter plan. See Mintlify's pricing page for current paid plans. | ## Where Mintlify is the better fit - You already have documentation and want to keep writing it yourself in a web editor. - You want an API playground or an MCP server for your docs. Mintlify lists both. - You want an AI agent that works from prompts, Slack threads or pull requests, not only from the repository. ## Where DocUp is the better fit - You have a repository and little or no user documentation, and want a first draft written from the code. - You want every command, flag and variable in the draft checked against your source. - You do not want a documentation tool to install, build or run your code. - You want to start free with a single project. ## Sources and accuracy Statements about Mintlify come from its public pricing page and agent documentation, read on 12 October 2026: https://www.mintlify.com/pricing and https://www.mintlify.com/docs/ai/agent. Products change, so check those pages before you decide. Mintlify is a trademark of its owner. DocUp is not affiliated with or endorsed by Mintlify.