Companies that use GitBook

Source: Analysis of job postings that mention GitBook (using the Bloomberry Jobs API)

My analysis shows that GitBook is overwhelmingly purchased and championed by documentation and knowledge management teams. Technical Writers represent 56% of roles mentioning GitBook, followed by Product Managers at 3% and various content specialists at 3% each. The remaining roles span diverse functions from Operations Directors to Solutions Engineers, suggesting GitBook crosses departmental boundaries once adopted. These teams prioritize creating scalable documentation systems, improving developer experience, and establishing single sources of truth for technical knowledge.

Day-to-day users are primarily technical writers and documentation specialists who create and maintain product documentation, API references, user guides, and knowledge bases. They work cross-functionally with engineering, product, and customer success teams to translate complex technical concepts into clear content. Many roles emphasize managing documentation in docs-as-code workflows using Markdown and GitHub, then publishing to GitBook for presentation. Several positions also mention creating video tutorials, release notes, and integration guides alongside written documentation.

The pain points I observed center on documentation chaos and scalability challenges. Companies describe needing to transform "scattered information from internal release messages, Slack conversations, and older documents into a consistent and professional set of platform documentation." Another posting seeks someone to "take ownership of our portal of documentation, leading its refactoring and improvement." A third emphasizes "ensuring our technical documentation is clear, accurate, and accessible to developers" to reduce support escalations. These phrases reveal organizations struggling with fragmented knowledge systems and recognizing documentation quality as critical to product adoption and customer self-service.

Source: Analysis of Linkedin bios of 9,350 companies that use GitBook

I noticed that GitBook users are overwhelmingly companies building technical infrastructure and tools for other businesses. These aren't consumer brands. They're creating platforms, APIs, security solutions, data pipelines, and developer tools. Many are in fintech (payment processors, lending platforms, crypto infrastructure), cybersecurity (AI security, privacy tools, threat detection), or DevOps and data infrastructure. They're solving complex technical problems that require detailed documentation.

These are predominantly early to mid-stage companies. I counted roughly 25 seed or Series A/B funded companies, many with 11-50 employees. The employee counts are telling: lots of 2-10 person teams and 11-50 person companies, with only a handful over 200 employees. Many list recent funding rounds between $1M and $30M. They're past the initial idea stage but still building, scaling their first major product, and likely creating their first proper documentation as they onboard customers and developers.

Source: Analysis of tech stacks from 9,350 companies that use GitBook

I noticed that GitBook users are predominantly modern, product-led companies that prioritize developer experience and documentation as a core part of their growth strategy. The massive correlation with tools like Framer, Webflow, and NextJS tells me these are companies building for technical audiences while maintaining design-forward public presences. They're likely SaaS companies, developer tools, or API-first businesses where clear documentation directly impacts product adoption.

The pairing of GitBook with Framer and Webflow is particularly revealing. These companies are investing heavily in their marketing sites and maintaining them separately from their documentation, which suggests they view docs as a distinct product experience rather than just another section of their website. The strong correlation with NextJS and Vercel Pro reinforces this, showing these teams favor modern JavaScript frameworks and serverless deployment. They're building fast, scalable web experiences and applying the same technical standards to their documentation infrastructure.

BetterUptime appearing 68 times more often than average is fascinating because it shows these companies treat documentation uptime as seriously as product uptime. When your docs go down and you're a developer-focused company, you're essentially offline to potential customers.