# How GitBook serves 30,000 sites with sub-second content updates

DevFeed: [How GitBook serves 30,000 sites with sub-second content updates](<https://devfeed.tech/articles/how-gitbook-serves-30-000-sites-with-sub-second-content-updates-742.md>)

Original publisher: [Read original article](<https://vercel.com/blog/how-gitbook-serves-30000-sites-with-sub-second-content-updates>)

Author: Eric Dodds

Published: 2026-05-01T04:00:00Z

Content type: article

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Next.js](<https://devfeed.tech/topics/next-js.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [docs](<https://devfeed.tech/tags/docs.md>), [edge](<https://devfeed.tech/tags/edge.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [updates](<https://devfeed.tech/tags/updates.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

GitBook describes serving 30,000 documentation sites on Vercel with Next.js, using tag-based cache invalidation triggered by merge events to make affected content visible globally within 300 milliseconds.

## Source excerpt

GitBook on Vercel 30,000 documentation sites hosted on a single Vercel deployment 120 million monthly page views served from the edge 40,000 cache invalidations processed daily, each resolved in under 300ms 41% of all traffic now comes from AI crawlers and automated systems GitBook hosts 30,000 documentation sites on Vercel, serving 120 million page views every month. Companies like n8n, Nvidia, and Zoom trust the platform to keep their docs fast and current. For modern engineering teams and coding agents, documentation is as critical as the production code it describes, and GitBook sits at the center of that expectation. GitBook's publishing model mirrors how teams ship software: propose changes, review, and merge. With 30,000 independently managed sites each on its own update cadence, keeping content fast and fresh was a complicated engineering problem. Before migrating to Vercel, site editors would hit merge, visit the published site to validate, and see old version of the content. "One of our customers planned a large feature release, and on launch day, the docs lagged behind the rest of the product," says Steven Hall, Head of Engineering at GitBook. "That was the moment we really internalized that docs are as important as your code going to production." Making merge mean live at multi-tenant scale GitBook's published content frontend runs on Next.js and is open source. When Vercel's use cache directive became available, the team saw a solution to their speed problem: cache individual data-fetching functions rather than full page responses. That meant expensive API calls were deduplicated across requests, and cache behavior became visible directly in code rather than buried in external configuration. The harder problem was invalidation. In a multi-tenant system, a broad cache purge is expensive and wasteful. One team merging a typo fix shouldn't trigger revalidation for 29,999 other sites. GitBook already had a reliable signal for when content becomes stale: a m