Comparison
Dossiers vs Docusaurus
A React-powered framework for public product docs — versus a zero-config publisher for the specs behind the product.
Docusaurus, Meta’s MIT-licensed docs framework, is a great choice for public product documentation: versioned docs per release, internationalization, a blog, and MDX so you can embed live React components right in a page.
The price of that power is a toolchain. You run Node.js, manage npm dependencies, and customize in React — reasonable for a flagship docs site, heavy for the internal specs behind it. Dossiers is a single binary with no build pipeline to own: point it at a folder of Markdown and your team’s RFCs, design docs, and policies are a searchable website with drafts from open pull requests shown automatically.
At a glance
| Dossiers | Docusaurus | |
|---|---|---|
| Monthly cost | Free — MIT-licensed CLI | Free (MIT); free hosting tiers on GitHub Pages, Netlify, Vercel |
| Open source | Yes — MIT | Yes — MIT |
| Where content lives | Markdown files in your Git repository | Markdown/MDX files in your Git repository |
| Authoring | Any editor or IDE; plain Markdown with YAML frontmatter | Markdown/MDX; React and a Node.js toolchain for customization |
| Review & approval | Pull requests — drafts appear automatically next to published specs | Bring your own — e.g. deploy previews from your hosting provider |
| Version history | Full Git history of every document | Full Git history, plus per-release doc versioning |
| Full-text search | Full-text search in the hosted service; static builds use browser search | Via Algolia DocSearch (free for open source) or community plugins |
| Access control | Google Workspace domain or GitHub org (hosted); static sites can sit behind your own auth | None — output is public unless you add your own auth layer |
| Self-hosting | Yes — static output hosts anywhere, or run the CLI server | Yes — static output |
| Lock-in | None — plain Markdown files stay in your repo | Medium — MDX and React components tie content to Docusaurus |
Prices are rounded list prices as of July 2026 and change often — always check the vendor’s pricing page. Dossiers hosted-service pricing will be announced at launch.
Which one is for you?
Choose Docusaurus if…
- You're publishing public documentation for a product with an audience
- You need versioned docs that track product releases
- You want interactive MDX/React components inside pages
- You need internationalized documentation
Choose Dossiers if…
- The documents are internal specs, ADRs, and policies — not product docs
- You don't want a Node.js build pipeline for your spec repository
- Plain Markdown should stay plain — portable to any future tool
- Access control matters: internal docs shouldn’t be public by default
The bottom line
These tools solve different problems and coexist happily: many teams publish product docs with Docusaurus while their internal RFCs and design docs live in a Dossiers site. If you’re choosing for internal specs, the single binary without a JavaScript toolchain wins on total cost of ownership.
Frequently asked questions
Can Dossiers render MDX or React components?
No. Dossiers renders standard Markdown (with Mermaid and svgbob diagrams built in) and preliminary AsciiDoc. If your specs need live interactive components, Docusaurus is the better fit.
Is migration from Docusaurus possible?
Plain-Markdown pages move over directly. Pages that use MDX components need those components replaced with Markdown, code blocks, or diagrams.
See it with your own specs
Point Dossiers at a folder of Markdown files — you'll have a site before the kettle boils.