Docgent
Install the agent skill
Home For agents Self-host Docs ↗
Self-host

Run your own Docgent.

Clone it and there's no other org's brands, access lists or document repos bundled in. Your documents, your infrastructure.

How it's structured

Docgent ships without brand data. brands/ is a git submodule (private by default) or any directory you point DOCGENT_BRANDS_DIR at. Each brand is a brand.yaml — id, name, repo, access, typography, palette, page — plus assets/, css/, doctypes/, fonts/.

Documents live in a separate git repo per brand. Studio, the CLI and agents all read and write it through the GitHub API. The repo is the database.

Brand config edits are filesystem writes. On a read-only serverless filesystem, edit the brands repo directly and redeploy — or run Studio somewhere writable.

Deploy shape

Studio

Next.js app. Deploy to Vercel or any Node host.

apps/studio

Render worker

WeasyPrint in a container. Needs native Pango/Cairo/HarfBuzz — it can't run serverless. Fly.io works well.

apps/render

Brands store

Your own repo or local directory. Point DOCGENT_BRANDS_DIR at it.

brands/ (submodule)

Documents

One git repo per brand. Studio and agents write to it via the GitHub API. You own the repo.

github.com/<org>/<brand>-documents

Get started

The README and HANDOVER.md cover the full setup — operational notes, known traps, and environment variables.

README on GitHub ↗ HANDOVER.md — operational notes ↗