Comparison
Dossiers vs GitBook
A polished hosted docs product with a browser editor — versus a Git-native publisher where the repository stays the source of truth.
GitBook is one of the most polished documentation products around: a clean WYSIWYG editor in the browser, AI-assisted search and answers, change requests, and publishing that just works. For customer-facing product docs written by mixed technical and non-technical teams, it’s a strong choice.
Architecturally, though, GitBook is the system of record — your content lives in its cloud, and Git Sync is a bridge to it, not the foundation. Dossiers inverts that: the repository is the record. Specs are Markdown files, review happens in pull requests with your normal tooling, and the website is just a rendered view you can host anywhere — including entirely on your own infrastructure, for free.
At a glance
| Dossiers | GitBook | |
|---|---|---|
| Monthly cost | CLI: free (MIT). Hosted service: TBD — free tier planned | Free for a single user; Premium ~$65/site/mo plus ~$12 per user/mo |
| Open source | Yes — MIT | No — proprietary SaaS |
| Where content lives | Markdown files in your Git repository | GitBook's cloud; two-way Git Sync available |
| Authoring | Any editor or IDE; plain Markdown with YAML frontmatter | WYSIWYG editor in the browser; Markdown via Git Sync |
| Review & approval | Pull requests — drafts appear automatically next to published specs | Change requests in GitBook's UI |
| Version history | Full Git history of every document | Revision history in-app; Git history when syncing |
| Full-text search | Full-text search in the hosted service; static builds use browser search | Yes — built in, with AI-powered answers |
| Access control | Google Workspace domain or GitHub org (hosted); static sites can sit behind your own auth | Visitor authentication and SSO on paid plans |
| Self-hosting | Yes — static output hosts anywhere, or run the CLI server | No |
| Lock-in | None — plain Markdown files stay in your repo | Medium — content is exportable via Git Sync, but workflow and features live in the platform |
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 GitBook if…
- Non-technical teammates should write in a WYSIWYG editor, not Markdown
- You want AI-assisted search and answers for customer-facing docs
- A fully managed platform is worth a per-site subscription to you
- You don't need self-hosting
Choose Dossiers if…
- Git should be the single source of truth, not a sync target
- Review belongs in pull requests with your existing code-review tooling
- You want open source and the option to self-host for free
- You're documenting internal specs, not customer-facing product docs
The bottom line
If you want a managed editor-first docs product and the repository is optional, GitBook is excellent. If the repository is the point — reviews, history, and portability through Git — Dossiers is built around exactly that, with a free MIT-licensed CLI instead of a per-site subscription.
Frequently asked questions
GitBook has Git Sync — isn’t that the same thing?
Git Sync mirrors content between GitBook and a repo, but editing, review, and permissions still happen in the platform. With Dossiers there is nothing to sync: the repository is the only copy, and the site renders whatever is merged.
Can I migrate from GitBook?
Yes — enable Git Sync or export to Markdown, then point Dossiers at the resulting files. Frontmatter metadata like status and authors can be added incrementally.
See it with your own specs
Point Dossiers at a folder of Markdown files — you'll have a site before the kettle boils.