Skip to content

Docs that keep up with your code.

Docup writes docs from your GitHub repository and updates them on every push.

Connect a repositoryRead Docup's own docs

It keeps up on its own

A push rewrites only the pages it touches.

Docup reads what changed, finds the pages written from those files, and leaves the others alone.

Every push, start to finish, without you.

Reading what changed, deciding what the docs need, updating the pages. On a live site, the pages you never edited go live by themselves.

Pages you edited are never overwritten.

A page you edited gets the update as a suggestion, with the changed lines. You accept it or you dismiss it.

From a repository to a draft.

Reading the repository

Docup reads the files it is allowed to. Lockfiles, .env files, keys, binaries and vendored folders are kept out before anything goes to the AI.

Planning the docs

It plans the pages the docs need, in folders: an overview, getting started, the guides, and reference only where the code has it.

Writing the pages

A writer drafts each page from the files that matter for it, and records which files. One page that fails never stops the others.

Saving the draft

The result is a private draft. Nothing is public until you publish it.

Readers get the answer

Find a page by what it is about.

Search finds a page by its title, its folder or its summary.

Answers come from your pages.

Ask AI answers from your published pages, with the pages it used linked.

A history of every push.

Each run shows what it read and what it did to each page.

This is how a published site looks: Docup's own documentation, written from Docup's own repository. Pages open without a reload.

docs.docup.dev
Search
Finds a page by its title, its folder or its summary.
Ask AI
Readers ask a question and get an answer written from your published pages, with the pages it used linked.
Dark mode
Light and dark, and you choose which one a first-time reader sees.
Your own domain
Serve the docs from a subdomain you own, like docs.acme.com.
Social images
A card for every page with its title and summary, or one image of your own.
Sitemap and robots.txt
Built from your published pages.
llms.txt and .md copies
An index for AI tools, and a Markdown copy of every page.
Crawler controls
Choose whether search engines and AI crawlers may read the docs.
Open docs.docup.dev

docs.docup.dev/llms.txt

# Docup Documentation: AI docs from your GitHub repo

> Learn how Docup turns a GitHub repository into a hosted documentation site: AI-written pages, a visual editor, one-click publishing, updates on every push, Ask AI for readers and cookie-free analytics.

## Docs
- [Overview](https://docs.docup.dev/index.md): Docup turns a GitHub repository into a hosted, searchable documentation site and keeps it up to date as your code changes.
- [Getting started](https://docs.docup.dev/getting-started.md): Sign in, connect a GitHub repository, choose an address and publish your first documentation site.

## Concepts
- [How Docup works](https://docs.docup.dev/concepts/how-it-works.md): How Docup reads a repository, plans pages, writes them, and keeps drafts, live pages and your own edits apart.
- [Drafts and live pages](https://docs.docup.dev/concepts/drafts-and-live.md): Why every change is a draft first, what readers see, and exactly what publishing copies to the live site.

AI tools read it too.

llms.txt is a plain-text index of your docs for AI tools: every page, its address and its summary. Every page also has a Markdown copy at its address ending in .md, and llms-full.txt carries all the docs in one file. You can turn them off in Settings.

Questions