GitBook started as a way to write books in Markdown. Then it became the default choice for open-source project documentation. Now it’s trying to be an enterprise documentation platform with AI features.

That evolution has been rocky. Pricing has changed multiple times, features have been gated behind higher tiers, and some long-time users feel abandoned. But GitBook still serves millions of documentation sites, and their new AI Agent (currently in beta) suggests the platform isn’t done evolving.
Here’s what GitBook actually delivers in 2026, who should use it, and whether the pricing makes sense.
Who Uses GitBook?
GitBook has positioned itself at the intersection of developer documentation and team knowledge bases. Their customer list spans:
- Open source projects using the free tier for public documentation
- Developer tools like Prisma, Supabase, and Kong
- Startups needing quick, professional-looking docs
- Enterprise teams managing internal documentation
The platform claims to host millions of documentation sites. Most are on the free tier (public open-source docs), while paying customers tend to be developer-focused companies who value Git-based workflows.
GitBook Pricing at a Glance
GitBook uses per-site pricing with additional user fees. This model confuses some teams because costs scale in two dimensions: more sites and more users.
| Plan | Price/Site | Extra Users | Key Features |
|---|---|---|---|
| Basic | $0/month | N/A (1 user) | Public docs only, basic customization |
| Premium | $65/month | $12/user/month | Custom domain, branding, AI Answers |
| Ultimate | $249/month | $12/user/month | Site sections, visitor auth, AI Assistant |
| Enterprise | Custom | Custom | SAML SSO, dedicated support, migration help |
14-day free trial on paid plans. No credit card required.
The jump from free to Premium is steep. You go from $0 to $65/month the moment you need a custom domain or a second team member. For detailed pricing breakdowns, see our complete GitBook pricing guide.
The Free Tier Reality
GitBook’s free tier is generous for open-source projects. You get unlimited traffic, public publishing, and the GitBook subdomain at no cost.
What’s included:
- Unlimited visitors
- Public documentation only
- Basic editor and customization
- Site insights
- Preview deployments
- Single user
What’s missing:
- No custom domain (yourproject.gitbook.io only)
- No custom branding, themes, or fonts
- No AI features whatsoever
- No team collaboration
- No visitor authentication
For solo developers or open-source maintainers who just need public documentation, the free tier works. But the restrictions push most professional teams to paid plans quickly.
Premium Plan ($65/month + $12/user)
The Premium tier unlocks the features most teams actually need.
What’s included:
- Custom domain support
- Custom logo, themes, and fonts
- AI Answers (reader-facing Q&A)
- Advanced site insights
- Site redirects
- Multiple team members
What’s still missing:
- No site sections for organizing large docs
- No visitor authentication
- No AI Assistant for content creation
- No cross-site search
- No GitBook Agent access
Real cost for a small team:
A 4-person documentation team on Premium pays:
- Premium site: $65/month
- 3 additional users: $36/month
- Total: $101/month (~$1,212/year)
Ultimate Plan ($249/month + $12/user)
GitBook’s top tier targets larger organizations with complex documentation needs.
What’s included:
- Site sections and groups
- Cross-documentation search
- Visitor authentication (Azure, Auth0, Okta)
- AI Assistant for content creation
- Adaptive content
- GitBook Agent (beta)
Still Enterprise-only:
- SAML SSO
- Dedicated support
- Migration assistance
Real cost:
An 8-person team on Ultimate pays:
- Ultimate site: $249/month
- 7 additional users: $84/month
- Total: $333/month (~$3,996/year)
The GitBook Agent
GitBook launched an AI agent to help with documentation workflows. It’s their answer to the “documentation maintenance” problem, and it’s worth examining what it actually does today versus what’s planned.
What GitBook Agent does today:
- Writes and edits documentation based on prompts
- Implements changes via change requests with explanations
- Follows your organization’s style guide automatically
- Accepts custom organization-level instructions
What’s coming (not yet available):
- Proactive monitoring of GitHub issues and Intercom conversations
- Automatic identification of documentation gaps
- Suggestions based on support conversation patterns
The limitations:
GitBook Agent is currently reactive, not proactive. It responds to your requests rather than independently identifying what needs updating. The proactive features (monitoring support conversations, spotting gaps) are roadmap items, not current capabilities.
The agent is only available on Pro (Premium) and Enterprise plans. Teams on the Basic tier don’t get AI features at all.
What GitBook Does Well
Git-based workflow: GitBook’s native GitHub and GitLab sync is excellent for developer teams. Documentation lives alongside code, pull requests trigger doc previews, and version control is built in. If your team already thinks in Git, GitBook feels natural.
Clean reading experience: GitBook documentation looks professional with minimal effort. The default theme is readable, navigation is intuitive, and mobile rendering works well. Readers can find what they need.
Fast search: The built-in search is quick and handles developer queries reasonably well. AI Answers (on paid plans) provides conversational responses based on your documentation content.
Collaboration features: Real-time editing, commenting, and change requests work smoothly. Distributed teams can work on documentation without stepping on each other.
Mature ecosystem: GitBook has been around since 2014. The platform is stable, well-documented (ironic if it wasn’t), and integrates with common developer tools.
What GitBook Doesn’t Do
Customer-facing help center: GitBook is documentation publishing, not customer self-service. There’s no embedded help widget, no customer portal, no feedback collection, and limited analytics on what customers actually search for. If you need a true help center, consider Help Scout or HelpDocs.
Support ticket analysis: GitBook plans to connect the Agent to Intercom (coming soon), but even then it will process individual conversations rather than analyzing patterns across thousands of tickets. You won’t get automated FAQ generation based on what customers actually ask repeatedly.
Codebase understanding: The agent doesn’t read your codebase to understand when button names change or features get deprecated. It can sync API docs from OpenAPI specs, but general product changes go unnoticed. Documentation drift happens silently until someone notices.
Cost-effective team scaling: The $12/user/month fee adds up. A 10-person team pays $108/month just for user seats before site costs. Mintlify and Docusaurus offer different models that might scale better.
Migration assistance (without Enterprise): Moving to GitBook from another platform requires manual effort unless you’re paying enterprise rates. There’s no one-click import from Zendesk, Intercom, or Help Scout.
The Pricing Complaints
GitBook has frustrated some users with pricing changes over the years. Common complaints include:
Forced upgrades: Some users report needing to upgrade to paid plans just to continue editing content that was previously accessible.
Feature gating: Capabilities that were once available have moved to higher tiers. Long-time users feel the free tier keeps shrinking.
Per-site costs: Organizations with multiple products need multiple sites, each requiring its own plan. Costs multiply quickly.
Unclear limits: AI feature usage limits aren’t always transparent, making it hard to predict costs.
These aren’t universal complaints, but they appear frequently enough in reviews to warrant attention during evaluation.
When GitBook Makes Sense
GitBook is a strong choice if:
- Your team uses Git-based workflows already
- You need professional-looking developer documentation
- Public-facing technical docs are your primary use case
- You have budget for $65-249/month per documentation site
- A mature, stable platform matters more than cutting-edge features
- You’re comfortable with manual content maintenance
When to Consider Alternatives
Look elsewhere if:
- Per-user and per-site fees make scaling expensive
- You need a customer-facing help center (not just developer docs)
- Automatic documentation updates matter to you
- You want AI that maintains content, not just creates it
- Budget is under $50/month
- You need deep support ticket analysis
For documentation that maintains itself, try Ferndesk. For developer documentation, compare Mintlify or Docusaurus. For help centers, consider HelpDocs or Document360. For a broader comparison, see our best help center software guide.
A Different Approach: Ferndesk
GitBook’s AI Agent is reactive. You ask it to write, and it writes. That’s useful, but it doesn’t solve the maintenance problem. Documentation still drifts out of sync when your product changes, and the Agent won’t notice unless you tell it to look.
Ferndesk takes a different approach.

Ferndesk’s agent (Fern) connects to your GitHub repository and watches for changes. When you rename a feature or deprecate an endpoint, Fern flags every article that references it. The documentation stays accurate because Fern notices drift before your customers do.
Fern also reads your support conversations. Not individual tickets like GitBook plans to offer, but patterns across thousands. When the same question appears repeatedly, Fern drafts an FAQ and puts it in your review queue. You approve or edit, then publish.
A 5-person team on GitBook Premium pays $113/month. The same team on Ferndesk Startup pays $39/month and gets codebase sync and ticket analysis that GitBook doesn’t offer at any tier.
GitBook is the right choice for developer documentation with Git workflows and teams comfortable with manual maintenance. For customer-facing help centers that need to stay current automatically, try Ferndesk free.
Bottom Line
GitBook is a mature documentation platform that does developer docs well. The Git integration is excellent, the reading experience is clean, and the platform is stable. The new AI Agent shows GitBook is investing in automation.
But the pricing model is complex, costs scale in multiple dimensions, and some users feel nickel-and-dimed by tier restrictions. At $65-249/month per site plus $12/user, GitBook isn’t cheap. And for teams who need documentation that maintains itself rather than documentation they maintain, the proactive features are still “coming soon.”
For developer documentation teams with Git workflows and budget, GitBook remains a solid choice. For everyone else, the limitations add up.