# Documentation drafted from your repository

Docup reads your code, decides which pages the docs need, and writes each one. You review a complete draft instead of facing a blank page.

## From repository to draft

**Read the repository.** Docup downloads the files it needs and filters them first. Lockfiles, binaries, build output, .env files and keys are never read.

**Plan the pages.** A planner looks at the code and decides what the docs need: an overview, getting started, the main guides, and reference pages only when the code really has them.

**Write each page.** A writer reads the files that matter for each page and drafts it. If a page fails, Docup tries again, and you can retry it yourself.

**Review the draft.** The result is a private draft. Read it, edit it, and publish when you are happy.

**Only what the code confirms**: The writer is told to state only what it verified in your source, and to leave out what it cannot confirm.

**Protected by default**: Secrets and credential files are filtered out before anything reaches the AI, whatever else you set.

**Steer it**: Add instructions about your audience and tone, and list folders or patterns to ignore.

**A failed page does not stop the rest**: Every run shows which pages were written and which failed, with a retry for each.

[Pricing](https://docup.dev/pricing)