shouldiuse.io

Categories

VERDICT

GitBook Review

Depends

Should I use GitBook?

The knowledge layer for AI — docs platform for technical teams - gitbook.com

· 1 month ago

Buy if you're a technical team publishing polished public or API docs and can absorb per-site pricing. Skip it if you want a cheap internal wiki or run many doc sites on a budget.

Confidence

Medium. Based on ~40 public sources; most review snippets were truncated, so quote coverage is limited.

Ratings

  • Value for money
  • Ease of use
  • Feature depth
  • Support qualityNo direct support evidence found
  • Security posture

Pricing

$0

Free

ModelNot disclosed
Monthly feesNot disclosed
HardwareNot disclosed
Free tierYes
Premium and upPer-site (~$65/site reported)

Best for

  • Developer and API docs teams
  • Open-source project documentation
  • Docs-as-code teams using GitHub
  • Customer-facing knowledge bases

Not for

  • Solo writers wanting a cheap wiki
  • Teams publishing many doc sites on a budget
  • Non-technical teams needing simple internal notes
  • Buyers burned by per-site pricing models

Gotchas - check before you buy

high

~$65 per site reported; every extra doc site multiplies cost

high

New per-site pricing caused visible customer churn in Reddit threads

medium

AI Search is locked to Premium tier and above

medium

Old npm 'gitbook' CLI is vulnerable and abandoned; don't self-host it

Pros and cons

Pros

  • Strong reviews: 4.7/5 across 207 G2 ratings
  • Built-in AI search and AI agent for docs
  • Hosts 30,000 sites with sub-second content updates
  • Judged better value than ReadMe for API docs
  • Reviewers say it excels at organizing content

Cons

  • Per-site billing makes multi-site setups expensive
  • 2024–2025 pricing restructure pushed customers out
  • Two-year users left citing pricing surprises
  • Legacy open-source version carries known XSS CVEs

Sources & method

- 12 sources - Hosted product maintains a trust center and disclosure program; known CVEs affect the legacy open-source CLI, not the current SaaS.

official x2review x7security x2news x1
  • CVE-2017-16019 — XSS in legacy gitbook CLI, Affects old versions of the npm gitbook package; command-line tool, not the hosted product.
  • CVE-2019-19596 — XSS through GitBook 2.6.9, Medium-severity XSS in legacy GitBook through version 2.6.9.

Key stats

  • Value for money: 2/5

    Rating

  • $0

    Starting price

  • 12

    Sources

  • Analyzed

  • Value for money: 2/5. Per-site pricing; churn after restructure
  • Ease of use: 4/5. Praised editor, clean UI, strong organization
  • Feature depth: 4/5. AI search, AI agent, API docs support
  • Support quality. No direct support evidence found
  • Security posture: 3/5. Trust center exists; legacy CLI CVEs only
  • 4.7/5 G2 rating 207 reviews
  • $0 Starting price Free plan; paid per-site (~$65/site reported)
  • Yes Free tier For individuals
  • 30,000+ sites Scale Hosted docs sites, per Vercel case study

Pricing

Free

$0

  • For individuals
  • Basic publishing

Premium and up

Per-site (~$65/site reported)

  • AI Search included
  • Per-site billing scales with sites

Security

Hosted product maintains a trust center and disclosure program; known CVEs affect the legacy open-source CLI, not the current SaaS.

  • CVE-2017-16019 — XSS in legacy gitbook CLIAffects old versions of the npm gitbook package; command-line tool, not the hosted product.
  • CVE-2019-19596 — XSS through GitBook 2.6.9Medium-severity XSS in legacy GitBook through version 2.6.9.

Companies that use it

  • Trunk
  • Uber
Full analysis

Based on ~40 public sources; most review snippets were truncated, so quote coverage is limited.

Solid 4.7/5 docs tool for technical teams — but per-site pricing stings; skip it for cheap internal wikis.

Methodology

Based on ~40 public sources; most review snippets were truncated, so quote coverage is limited.

Read how a report is made.

Sources

  1. review
  2. review
  3. review
  4. review
  5. review
  6. review
  7. review
  8. official
  9. official
  10. news
  11. security
  12. Trust Center | GitBooksecurity.gitbook.com
    security

Add this review to your site

This check for GitBook says Depends.

Put the badge on your site.

Visitors see the independent review.

The link points here, and search engines follow it.

This is the badge visitors see on your site.

Paste one snippet. Keep the link as it is. A nofollow tag stops search engines from following it.

Rate this review

Anonymous. You can change your vote.

Loading votes…

Comments

One queue. No nested comments. Give a display name first. Limit: 200 words per comment and 7 comments per day. You can edit or delete yours.

Save a name to write a comment.

0 / 200 words

No comments yet.