Documentation · head to head
BookStack vs Starlight
BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- From
- Free
- Rated
- -
Starlight
Documentation
Documentation site framework built on Astro that ships no JavaScript to the reader by default
- 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.; Starlight there is no editing interface, so every correction requires a git client, a Node install and a CI run, which puts documentation changes out of reach for anyone who does not already work in a repository.
- They diverge on capability: BookStack covers Shelves, books, chapters, pages, Starlight covers File based routing.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which BookStack and Starlight 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 Starlight
- File based routing
- Pagefind search
- Internationalisation
- Component overrides
- Zero client JavaScript
- Expressive Code blocks
- Auto generated sidebar
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 Starlight
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Starlight
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Starlight
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Starlight
Starlight
- A developer tool whose docs live in the same repository as the code and are reviewed in the same pull requestnot BookStack
- A team that already runs Astro for its marketing site and wants one build pipeline for bothnot BookStack
- Documentation that must be served from a CDN or an air gapped static host with no search backendnot BookStack
- A multilingual open source project that needs per locale content trees and untranslated page fallbacknot 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.
Starlight
- There is no editing interface, so every correction requires a git client, a Node install and a CI run, which puts documentation changes out of reach for anyone who does not already work in a repository.
- Starlight versions track Astro versions, so an Astro major release becomes a documentation site migration on someone else timeline rather than yours.
- Pagefind builds the whole search index at compile time, so build duration and index size grow with page count and large documentation sets pay for it on every deploy.
- There is no analytics, no feedback widget and no page level rating built in, so measuring which pages fail readers means wiring a third party script yourself.
- Component overrides are limited to the slots the theme exposes, and anything outside those slots means forking the theme and inheriting the merge burden on every upgrade.
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
Starlight
Free- Open sourceFree
- MIT licence
- All features included
- Self hosted on any static host
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 Starlight if
- You need file based routing.
- You want to start without paying.
- You work on Web, macOS, Windows, Linux.
- You also want pagefind search.
Questions people ask
- Is BookStack or Starlight better?
- Neither clearly leads. BookStack starts at Free and Starlight at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BookStack or Starlight?
- BookStack starts at Free and Starlight at Free.
- Does BookStack or Starlight run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. Starlight 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 Starlight is typically brought in for.
- What can BookStack do that Starlight cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Starlight covers File based routing, Pagefind search, Internationalisation, Component overrides.
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.
Starlight: Can a non technical writer publish a page without help?
No. There is no content management interface. Every change is a commit, a pull request and a build.
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.
Starlight: Do I need to know Astro to use it?
Not for basic use. Markdown files and a config file are enough until you want custom components, at which point Astro knowledge becomes mandatory.
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.
Starlight: Is search included or do I pay for it?
Included and free. Pagefind builds a static index at compile time. Algolia DocSearch is optional if you want hosted search instead.
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.
Starlight: What happens when Astro releases a major version?
Starlight follows it, and your site needs a migration. Read the upgrade guide before pinning a version for a long lived project.
Starlight: Can I self host with no external services?
Yes. The output is static HTML, CSS and a search index. Nothing calls out at runtime unless you add it.
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 VitePress
- BookStack vs Fumadocs
- BookStack vs Scalar
- BookStack vs Paligo
- BookStack vs Adobe RoboHelp
- Starlight vs Nuclino
- Starlight vs Slab
- Starlight vs MkDocs
- Starlight vs GitBook
- Starlight vs Outline
- Starlight vs Docsify
- Starlight vs HelpDocs
- Starlight vs Read the Docs
- Starlight vs Doxygen
- Starlight vs Guidde
- Starlight vs Sphinx
- Starlight vs Archbee
- Starlight vs Adobe FrameMaker
- Starlight vs Antora
- Starlight vs Bump.sh
- Starlight vs VitePress
- Starlight vs Fumadocs
- Starlight vs Scalar
- Starlight vs Paligo
- Starlight vs Adobe RoboHelp