Comparison
Dossiers vs Hugo
The fastest general-purpose site generator, compared with a tool that only does specs — and does them out of the box.
Hugo is a remarkable piece of engineering: a single binary that renders thousands of pages per second and can be bent into almost any shape — blogs, marketing sites, documentation, portfolios. If you can express it in templates and taxonomies, Hugo can build it.
That generality is also its cost. Before Hugo shows your first document you pick a theme, write a config file, and learn its content model — and the things a spec library needs, like per-document status, an automatic index, or search, are yours to assemble from themes and plugins. Dossiers starts where that assembly ends: it assumes your repository is a stack of interlinked specifications and renders it as a finished product — index, metadata, cross-links, diagrams, and pull-request drafts included. dossiers serve ./specs is the whole setup.
At a glance
| Dossiers | Hugo | |
|---|---|---|
| Monthly cost | Free — MIT-licensed CLI | Free (Apache 2.0); free hosting tiers on GitHub Pages, Netlify, Vercel |
| Open source | Yes — MIT | Yes — Apache 2.0 |
| Where content lives | Markdown files in your Git repository | Markdown files in your Git repository |
| Authoring | Any editor or IDE; plain Markdown with YAML frontmatter | Any editor; Markdown plus Hugo shortcodes and templates |
| 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 |
| Full-text search | Full-text search in the hosted service; static builds use browser search | None built in — add a theme feature or third-party service |
| 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 | Low, though shortcodes and theme conventions are Hugo-specific |
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 Hugo if…
- You're building a blog, marketing site, or anything that isn't a document collection
- You want full control over layout, themes, and URL structure
- You need taxonomies, multilingual sites, or custom output formats
- You have the time — and the inclination — to maintain templates
Choose Dossiers if…
- Your content is specs, RFCs, ADRs, or policies — not a website with pages
- You want a useful site in minutes, with zero configuration or theme hunting
- Draft review in pull requests should be part of the site, not a separate setup
- You'd rather maintain documents than templates
The bottom line
Hugo is a toolkit; Dossiers is an appliance. If the goal is “our specs, published and searchable, today”, Dossiers gets you there without touching a template. If the goal is a bespoke website, Hugo is the better hammer.
Frequently asked questions
Can I use my existing Markdown files with Dossiers?
Mostly, yes. Dossiers reads plain Markdown with YAML frontmatter, so standard content carries over directly. Hugo-specific shortcodes won’t render and would need to be replaced with plain Markdown.
Does Dossiers support themes like Hugo does?
No — and that’s deliberate. Dossiers ships one carefully designed, responsive layout with automatic dark mode, so every spec repository looks consistent with zero decisions.
See it with your own specs
Point Dossiers at a folder of Markdown files — you'll have a site before the kettle boils.