GitBook

GitBook is a documentation platform where product and engineering teams write, review and publish docs sites with AI answers, priced per site and per user.

GitBook keeps a company's product documentation in one editor and turns it into a docs site that customers, developers and AI coding tools can all read. It replaces the scattered wiki pages and README files that fall behind once a product ships. GitBook INC. builds it and owns it outright, with no parent company behind it. Writers work in a block-based visual editor that also accepts Markdown, and live edits let several people change the same page while leaving comments. Where live edits are turned off, every change goes through a change request, and merge rules can hold publishing until each requested review is approved. Version history keeps earlier states of a page for comparison and rollback. Reusable content blocks and variables update every page that uses them, while tags and nested pages shape the table of contents. GitBook Agent drafts and revises pages, and readers get answers from AI Assistant in the search box or a chat sidebar. The usual owners are technical writers, developer relations staff and product managers responsible for public guides and API references. Engineering teams that keep documentation beside their code can tie a space to GitHub or GitLab with Git Sync. Companies writing only for paying customers or partners put the site behind authenticated access, signing readers in through Okta, Azure AD, Auth0 or AWS Cognito. Adaptive content then shows each reader the pages meant for them. For organisations with a security review to pass, SAML SSO and IP allowlisting are available. Migration is often the first job: the importer reads Markdown, HTML and Word files as well as Confluence and Notion spaces. Teams with an OpenAPI spec publish interactive API documentation next to their guides, and preview deployments show each edit in context before it goes live. After launch, insights on traffic, searches and page ratings point writers to the questions their docs still miss. Auto-updating translations follow the source text, so a multilingual site does not drift. Every published site also generates an MCP server, which lets a developer's coding assistant read the current docs instead of stale copies.