GitBook earns its place when support writers and engineers need to edit the same docs without using the same tools. The tradeoff to test is what happens when the editor, your repo, and the published site all need to agree.
DocsAlot publishes this buyer guide and competes in documentation. The public accounts below are examples, not a measure of how often a problem occurs.
The repository isn't a byte-for-byte copy of the editor
GitBook offers two-way Git Sync. The vendor also publishes normalization examples, so some Markdown changes are expected rather than bugs. A June 2025 GitHub report described README and navigation conflicts in a mixed editor-and-repo workflow. The discussion suggested explicit content configuration, and the issue is now closed. It doesn't establish a current bug.
There was also a specific November 2, 2026 Git Sync incident in which some page content went missing. GitBook reported that it rolled back the change and restored affected spaces. Treat that as a reason to test recovery, not as an ongoing outage.
Separate design preferences from actual blockers
One G2 reviewer wanted more layout flexibility for visually rich pages and more prominent commit messages, while praising straightforward maintenance and rollback. A self-hosting discussion includes a team looking elsewhere after pricing changes affected its multiple custom-domain sites. That is one team, not a quote you can apply to your own setup.
Use GitBook's current pricing to price the exact number of sites and contributors you need. Don't assume collections, domains, or additional users map one-to-one to the line items in another vendor's plan.
Run a round trip before switching
- Import a small copy of your repo with its real navigation and image paths.
- Edit one page in GitBook and one in Git. Rename a folder and inspect both outputs. Distinguish formatting changes from missing content.
- Revert a change and verify links, images, and the published site recover. Repeat with the most visual page you publish.
If the editor makes it easier for non-engineers to contribute, GitBook may be worth the extra structure. If your team mostly reviews docs in Git and wants more control over the published design, start with the GitBook comparison and pricing breakdown. Test your own pages before moving the domain.