GitBook

1. 1

   You create a space, write in GitBook's editor, and publish it as a site. The published site is fast, mobile-clean, and indexable by default, with built-in SEO on every plan including free. Custom domains arrive on Premium, along with deeper theming, and Ultimate adds custom subdirectories and fonts for teams who want the docs to be part of the main site rather than a subdomain of it.

2. 2

   Git Sync connects a space to a GitHub or GitLab repository so content lives as Markdown in version control. From there the workflow is the one engineers already have: branch a change, open a pull request, review it, merge it. Documentation edits and code changes can travel together, which is the only reliable mechanism anyone has found for keeping API docs accurate. OpenAPI specifications can be imported to generate reference documentation automatically.

3. 3

   Site variants and site sections handle versioning and structure: variants publish parallel versions of the same content (product versions, language variants), while sections on Ultimate split a site into distinct areas. Authenticated access on Ultimate gates content behind a login, which is how a single site serves public documentation and customer-only or partner-only material.

4. 4

   The AI layer works in three directions. Readers get an AI Assistant that answers from your documentation conversationally, capped at 500 answers a month on Premium and customisable and embeddable on Ultimate. Writers get AI search and AI writing assistance. And the GitBook Agent proactively scans documentation to detect content that has drifted out of date before a customer finds it. Beyond that, an MCP server (available even on the free tier) exposes documentation to Claude, ChatGPT, and other assistants directly, and AI Insights on Ultimate reports where both humans and AI agents fail to find an answer.

Per published site subscription plus a per-user charge above the included seats, with a free tier, and reader-facing AI metered as a monthly answer cap rather than a per-resolution charge.

Value assessment: GitBook prices documentation as infrastructure rather than as seats, and that is the right frame for judging it. A four-person team documenting one product pays $65 for the site plus $36 for three additional users, so roughly $101 a month on Premium: cheaper than Helpjuice's $249 floor, comparable to HelpDocs at $99, and with a docs-as-code workflow neither of them offers. The free tier is genuinely usable and includes an MCP server, which most competitors reserve for their top plan. Where the model turns against you is multiplicity and volume: several product documentation sites each carry a full site fee, and the reader-facing AI Assistant caps at 500 answers a month on Premium with the next tier nearly four times the price. Compared with the rest of this category, the AI shape is still friendlier than a meter: Help Scout charges $0.75 per resolution, Intercom bills per resolution and reaches roughly $1,106 a month for four agents, and Zendesk roughly $1,420, all of which rise as deflection succeeds. GitBook's cost rises in steps rather than continuously. For an engineering-led company documenting one product, this is very good value. For a support team documenting a service with non-technical writers, it is the wrong tool no matter what it costs.

Setup time

A published site in under an hour on the free tier. Git Sync configuration against an existing repository takes a few hours including deciding on the branch strategy, and importing an OpenAPI specification is quick once the spec is clean.

Learning curve

Low for engineers, who already know the branch-review-merge model and will find GitBook obvious. Noticeably higher for non-technical writers, who need to understand change requests, variants, and how their edits relate to the repository. That asymmetry is the single most important thing to test during evaluation.

Onboarding

Fully self-serve up to the $249 Ultimate tier, with a genuinely usable free plan as the trial. Only Enterprise requires a sales conversation, and it includes white-glove migration.

Migration notes

Markdown imports are straightforward and are the natural path from most existing documentation, and OpenAPI import handles API reference generation. Migrating from an editor-first tool like Zendesk Guide or Intercom Articles means converting content to Markdown, which is usually scriptable but rarely lossless on complex formatting. Configure redirects from old article URLs before cutover if the existing documentation has organic rankings. On the way out, content already lives as Markdown in your own repository if Git Sync is enabled, which is the most portable position of any product in this category.

Platforms

Web application and editorPublished documentation sitesGit Sync with GitHub and GitLabMCP serverEmbeddable AI Assistant (Ultimate)

API

Documented API for content and site management, an MCP server on every plan for AI assistant access, OpenAPI specification import, and Git-based programmatic content management.

Compliance

SOC 2ISO 27001GDPR

Data residency

Hosted infrastructure; regional residency options are handled through the Enterprise tier rather than published on the standard plans.

SSO

SAML-based single sign-on on higher tiers, plus GitHub and Google authentication on lower ones.

Security notes

Encryption in transit and at rest, SOC 2 and ISO 27001 attestations, authenticated content access on Ultimate, and access controls on spaces and sites. If Git Sync is enabled, a full copy of the documentation also exists in your own repository, which is a meaningful resilience property no other product here offers.

Channels

Email and in-product supportPriority support on higher tiersWhite-glove migration on Enterprise

Documentation

Extensive documentation at gitbook.com/docs, built on GitBook itself, which is the most honest demonstration of what the published product looks like.

Community

Active presence among developer and technical writing communities, and a large body of public documentation sites built on the platform serving as reference examples.

Founded

2014

Headquarters

Lyon, France, with a distributed team across Europe, Asia, and North America

Ownership

Venture-backed, lightly funded

Founders

Samy Pesse, Aaron O'Mullan

Employees

Approximately 35 to 44 (est. 2026)

Funding

Reported total funding of roughly $2M across three rounds, with investors including Fly Ventures and Point Nine Capital. The company operates at a scale much closer to bootstrapped than to a typical venture-backed SaaS vendor.

GitBook is the right documentation product for exactly one kind of company and the wrong one for everybody else, which is a compliment. If your product has an API, your engineers maintain the docs, and your public documentation deflects more tickets than any chatbot could, Git Sync with branch-review-merge is the only workflow that keeps that documentation accurate, and $65 per site plus $12 per user is a fair price for it. The free tier is genuinely usable, the MCP server is included on every plan when competitors reserve it for their top tier, and content synced to Git means your documentation is more portable than any hosted alternative. Weigh the per-site pricing if you have several documentation properties, and model the 500-answer monthly cap on the reader-facing AI Assistant, because the jump from $65 to $249 per site is the real pricing decision. If your writers are support agents rather than engineers, close this and look at HelpDocs.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.