In production
See it before you trust it
Don’t take a landing page’s word for it. Open the sites, fetch the llms.txt, view source.
The problem
Your API changed. How many files do you edit now?
Until one of them is wrong — and an agent confidently tells your customer how your API worked two versions ago.
You edit the files on the left. Everything on the right regenerates:
/v1/payments:
post: createPayment
Install the SDK and
create your first payment.
"template": "mint" }
▸ search index inlined
▸ Markdown mirror per page
no runtime · host anywhere
"create_payment",
"retrieve_payment",
"create_order" ] }
name: retidal-api
description: Create and
manage payments…
---
> Payments and orders
- /docs/quickstart.md
- /docs/api/payments.md
There’s no second pipeline to forget. All four artifacts come out of the same build, from the same source — keeping them in sync stops being a task on your list.
Docs as code
Catch the broken link in review, not in support
Every push builds. Every docs error lands as an annotation on the exact file and line, inside your pull request — your reviewer sees it, your users never do.
And when something does break, you’re not grepping prose: every error is a stable code with a documented cause and fix. You diagnose each mistake once, ever.
Static output
Your docs shouldn’t have a landlord
Every build writes plain HTML, CSS, and JavaScript to an output directory in your project — search index included, no external requests at runtime.
Put it on S3, nginx, Cloudflare, GitHub Pages. The output keeps serving from wherever you put it, with or without Reed.
Prefer not to depend on our builders at all? The compiler runs in your CI. MIT-licensed, all the way down.
Included
The chores that come with docs, already handled
PR preview deployments
Your reviewers click a URL, not a checkout. Every PR builds from its own head commit.
Builds that don’t need the network
Your CI stops failing because a registry had a bad day. After one prefetch, builds run fully offline.
Docs next to your code
Point a site at a subdirectory of your monorepo. Only pushes that touch it rebuild.
Errors you never diagnose twice
Stable DS-codes with documented fixes — searchable and linkable, not prose to grep.
Your brand without a fork
Three templates share one token contract. Restyle with CSS variables, keep getting updates.
Your domain, handled
A subdomain now, your own domain when you’re ready — certificates managed for you.
Migration
You already wrote your docs. Don’t write them again.
The Fern importer reads the files you have today: your content lands unchanged, your config is translated, and what it could not carry over is reported as a warning. Coming from Mintlify, the translation is manual — the differences are documented field by field.
Coming from Fern
Coming from Mintlify
Pricing
Three sites are included during Reed’s public beta
Checked on 4 August 2026: Fern Hobby is $0 with one site, Fern Team is $150 / mo with one site, Mintlify Starter is $0 with no AI credits, and Mintlify Pro is $450 / mo billed annually or $540 / mo billed monthly. Verify current prices before purchasing.
Reed is free during the public beta. Post-beta prices and plan limits have not been decided. The quotas listed here are the current limits, and Reed does not charge per seat during the beta.
AI features run on your key. Reed does not resell or meter model usage.
Your docs are already in the repo. Connect it.
Connect a repository and Reed builds the docs site, an MCP server, a Claude Skill, and llms.txt from it.