Documentation · head to head
BookStack vs Fumadocs
BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- From
- Free
- Rated
- -
Fumadocs
Documentation
Documentation framework for Next.js that treats the docs site as an application rather than a static export
- From
- Free
- Rated
- -
The short version
- Each has a real cost: BookStack there is no vendor-hosted option at all, so you own the server, TLS certificates, database backups and upgrades, or you pay a third-party host that has no support relationship with the project and no ability to fix a bug.; Fumadocs it is a library rather than a finished theme, so the initial setup is meaningfully longer than a generator that ships a working site from one command.
- They diverge on capability: BookStack covers Shelves, books, chapters, pages, Fumadocs covers Next.js App Router native.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which BookStack and Fumadocs actually diverge.
Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated), category (Documentation).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in BookStack
- Shelves, books, chapters, pages
- Dual editors
- Granular permissions
- Full text search
- Page revisions
- REST API
- External authentication
- Export
Only in Fumadocs
- Next.js App Router native
- Multiple content sources
- OpenAPI page generation
- Built in search
- Headless and styled layers
- Type safe frontmatter
- Code and content colocation
What people use each for
The jobs each tool is most often brought in to do.
BookStack
- Running an internal knowledge base on infrastructure inside a network that cannot reach external SaaSnot Fumadocs
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Fumadocs
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Fumadocs
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Fumadocs
Fumadocs
- Documentation that must sit behind login and show different content to different customer plansnot BookStack
- A Next.js product team that wants docs to deploy in the same pipeline as the applicationnot BookStack
- API reference pages generated from an OpenAPI document alongside hand written guides in one navigation treenot BookStack
- A design system site where the component documentation must render the live components from the same codebasenot BookStack
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
BookStack
- There is no vendor-hosted option at all, so you own the server, TLS certificates, database backups and upgrades, or you pay a third-party host that has no support relationship with the project and no ability to fix a bug.
- The shelf, book, chapter, page hierarchy is fixed at four levels and cannot be reshaped, so migrating a deeply nested Confluence or MediaWiki space means flattening content by hand and losing the original structure.
- It requires PHP and MySQL or MariaDB, which is a stack many engineering teams no longer run, so adopting it usually means introducing a database and runtime nobody else in the organisation maintains.
- Development is concentrated on a single maintainer, which makes the bus factor a legitimate procurement question for anything the organisation intends to depend on for a decade.
- Content lives in the database rather than in files under version control, so there is no docs-as-code workflow, no review by pull request and no branch per release.
- Export is per page, chapter or book, so moving a large instance to another platform means writing a script against the REST API rather than copying a directory of Markdown.
Fumadocs
- It is a library rather than a finished theme, so the initial setup is meaningfully longer than a generator that ships a working site from one command.
- Maintenance is concentrated in a very small group, so an unresponsive week is a blocked upgrade and there is no support contract to escalate to.
- It only targets Next.js, so adopting it commits the documentation to that framework and a later migration means rewriting the site rather than swapping a theme.
- Breaking changes have arrived across minor versions during rapid development, so pinning versions and reading migration notes is a recurring cost rather than a one off.
- Running docs inside the application means docs traffic hits your application infrastructure and shares its failure modes, where a separate static site would have stayed up.
Pricing, plan by plan
BookStack
Free- BookStackFree
- MIT licence with no paid edition
- All features included, no seat limits
- Self-hosted on your own infrastructure
Fumadocs
Free- Open sourceFree
- MIT licence
- All packages included
- Self hosted or deployed with your Next.js application
Which should you pick?
Choose BookStack if
- You need shelves, books, chapters, pages.
- You want to start without paying.
- You work on Web, Self-hosted, Docker.
- You also want dual editors.
Choose Fumadocs if
- You need next.js app router native.
- You want to start without paying.
- You work on Web, macOS, Windows, Linux.
- You also want multiple content sources.
Questions people ask
- Is BookStack or Fumadocs better?
- Neither clearly leads. BookStack starts at Free and Fumadocs at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BookStack or Fumadocs?
- BookStack starts at Free and Fumadocs at Free.
- Does BookStack or Fumadocs run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. Fumadocs runs on Web, macOS, Windows, Linux.
- Can I use BookStack for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is BookStack best used for?
- BookStack is most often used for running an internal knowledge base on infrastructure inside a network that cannot reach external saas, documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki produces, replacing a confluence licence for a team that needs pages, permissions and search but none of the surrounding suite, publishing customer-facing manuals from the same instance as internal documentation using per-book permissions. Of those, running an internal knowledge base on infrastructure inside a network that cannot reach external saas and documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki produces are not what Fumadocs is typically brought in for.
- What can BookStack do that Fumadocs cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Fumadocs covers Next.js App Router native, Multiple content sources, OpenAPI page generation, Built in search.
Answered from the vendors’ own pages
BookStack: Is there a paid or hosted version?
No. BookStack is MIT-licensed with no commercial edition and no official hosted service. Third-party hosts exist but are unaffiliated with the project.
Fumadocs: Can I put documentation behind authentication?
Yes. Pages are Next.js server components, so the same session and authorisation checks the rest of the application uses apply.
BookStack: Can I nest pages more deeply?
No. Four levels is the design, not a limitation waiting to be fixed, and content that needs deeper nesting has to be restructured.
Fumadocs: Does it work outside Next.js?
No. The UI layer depends on the Next.js App Router.
BookStack: Does it support single sign-on?
Yes, through LDAP, SAML2 or OpenID Connect, with group to role mapping, and none of it is gated behind a paid tier because there is no paid tier.
Fumadocs: Can it generate pages from an OpenAPI spec?
Yes, including operation pages, schema rendering and an interactive request playground.
BookStack: How hard is it to migrate content in?
Straightforward for flat content through the REST API, awkward for deeply nested wikis, because the structure has to be collapsed to fit.
Fumadocs: Who maintains it and is that a risk?
A very small maintainer group. For a long lived commercial documentation set, treat the low bus factor as a real risk and budget for owning a fork.
Fumadocs: Do I still need a separate docs deployment?
No, and avoiding one is the main reason to choose it. The cost is that docs share your application uptime.
Related pages
Other head to heads
- BookStack vs Nuclino
- BookStack vs Slab
- BookStack vs MkDocs
- BookStack vs GitBook
- BookStack vs Outline
- BookStack vs Docsify
- BookStack vs HelpDocs
- BookStack vs Read the Docs
- BookStack vs Doxygen
- BookStack vs Guidde
- BookStack vs Sphinx
- BookStack vs Archbee
- BookStack vs Adobe FrameMaker
- BookStack vs Antora
- BookStack vs Bump.sh
- BookStack vs Scalar
- BookStack vs Starlight
- BookStack vs Redocly
- BookStack vs ReadMe
- BookStack vs VitePress
- Fumadocs vs Nuclino
- Fumadocs vs Slab
- Fumadocs vs MkDocs
- Fumadocs vs GitBook
- Fumadocs vs Outline
- Fumadocs vs Docsify
- Fumadocs vs HelpDocs
- Fumadocs vs Read the Docs
- Fumadocs vs Doxygen
- Fumadocs vs Guidde
- Fumadocs vs Sphinx
- Fumadocs vs Archbee
- Fumadocs vs Adobe FrameMaker
- Fumadocs vs Antora
- Fumadocs vs Bump.sh
- Fumadocs vs Scalar
- Fumadocs vs Starlight
- Fumadocs vs Redocly
- Fumadocs vs ReadMe
- Fumadocs vs VitePress