Documentation · head to head
BookStack vs Lit
BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- 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.; Lit smaller ecosystem compared to React or Vue
- They diverge on capability: BookStack covers Shelves, books, chapters, pages, Lit covers Reactive properties.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which BookStack and Lit actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).
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 Lit
- Reactive properties
- Tagged template literals
- Scoped styling with Shadow DOM
- Web Components standard
- Minimal bundle size
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 Lit
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Lit
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Lit
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Lit
Lit
- Building reusable component libraries across frameworksnot BookStack
- Creating design systems with scoped stylesnot BookStack
- Developing progressive web applications with minimal dependenciesnot 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.
Lit
- Smaller ecosystem compared to React or Vue
- Web Components adoption still growing in the industry
- Requires understanding of Shadow DOM concepts
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
Lit
FreeNo published plan breakdown. See the Lit review.
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 Lit if
- You need reactive properties.
- You want to start without paying.
- You work on Web, Node.js.
- You also want tagged template literals.
Questions people ask
- Is BookStack or Lit better?
- Neither clearly leads. BookStack starts at Free and Lit at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BookStack or Lit?
- BookStack starts at Free and Lit at Free.
- Does BookStack or Lit run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. Lit runs on Web, Node.js.
- 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 Lit is typically brought in for.
- What can BookStack do that Lit cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Lit covers Reactive properties, Tagged template literals, Scoped styling with Shadow DOM, Web Components standard.
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.
Lit: Is Lit free to use?
Yes, Lit is open source and completely free under the BSD 3-Clause license.
SourceBookStack: 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.
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.
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.
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 React
- BookStack vs Vue.js
- BookStack vs MUI
- BookStack vs SolidJS
- BookStack vs Bootstrap
- BookStack vs Preact
- BookStack vs shadcn/ui
- BookStack vs Chakra UI
- BookStack vs esbuild
- BookStack vs MySQL
- BookStack vs Docusaurus
- BookStack vs Radix UI
- BookStack vs Spring Boot
- BookStack vs Strikingly
- BookStack vs Svelte
- BookStack vs Turbopack
- BookStack vs TypeScript
- BookStack vs Wix
- Lit vs Nuclino
- Lit vs Slab
- Lit vs MkDocs
- Lit vs GitBook
- Lit vs Outline
- Lit vs Docsify
- Lit vs HelpDocs
- Lit vs Read the Docs
- Lit vs Doxygen
- Lit vs Guidde
- Lit vs Sphinx
- Lit vs Archbee
- Lit vs Adobe FrameMaker
- Lit vs Antora
- Lit vs Bump.sh
- Lit vs React
- Lit vs Vue.js
- Lit vs MUI
- Lit vs SolidJS
- Lit vs Bootstrap
- Lit vs Preact
- Lit vs shadcn/ui
- Lit vs Chakra UI
- Lit vs esbuild
- Lit vs MySQL
- Lit vs Docusaurus
- Lit vs Radix UI
- Lit vs Spring Boot
- Lit vs Strikingly
- Lit vs Svelte
- Lit vs Turbopack
- Lit vs TypeScript
- Lit vs Wix