Documentation · head to head
BookStack vs Scalar
BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- From
- Free
- Rated
- -
Scalar
Documentation
Open source API reference renderer and request client generated entirely from an OpenAPI document
- 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.; Scalar it documents only what an OpenAPI document can express, so guides, authentication walkthroughs and conceptual pages need a second tool and a second navigation.
- They diverge on capability: BookStack covers Shelves, books, chapters, pages, Scalar covers OpenAPI driven reference.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which BookStack and Scalar 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 Scalar
- OpenAPI driven reference
- Embedded API client
- Generated code samples
- Framework adapters
- Themeable renderer
- Self hostable
- Spec validation
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 Scalar
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Scalar
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Scalar
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Scalar
Scalar
- Replacing default Swagger UI on a public API without moving to a hosted documentation vendornot BookStack
- A framework that already emits an OpenAPI document and needs a reference page mounted on a routenot BookStack
- An internal API portal that must run inside a private network with no external callsnot BookStack
- A team that wants readers to make authenticated test calls without leaving the reference pagenot 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.
Scalar
- It documents only what an OpenAPI document can express, so guides, authentication walkthroughs and conceptual pages need a second tool and a second navigation.
- The output is only as good as the spec, so an API with thin descriptions and missing examples produces a thin reference and the tool cannot compensate.
- Deep visual customisation goes beyond the theme variables quickly, and matching an existing brand often means overriding styles against internal class names that can change.
- Running the embedded client against a production API invites readers to send real requests, which means rate limits, test accounts and CORS configuration become your problem.
- The open source renderer and the hosted platform advance at different rates, so a feature seen in a demo is not necessarily in the package you self host.
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
Scalar
Free- Open source rendererFree
- MIT licence, no fee for the renderer
- Embedded request client
- Framework adapters
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 Scalar if
- You need openapi driven reference.
- You want to start without paying.
- You work on Web, macOS, Windows, Linux.
- You also want embedded api client.
Questions people ask
- Is BookStack or Scalar better?
- Neither clearly leads. BookStack starts at Free and Scalar at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BookStack or Scalar?
- BookStack starts at Free and Scalar at Free.
- Does BookStack or Scalar run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. Scalar 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 Scalar is typically brought in for.
- What can BookStack do that Scalar cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Scalar covers OpenAPI driven reference, Embedded API client, Generated code samples, Framework adapters.
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.
Scalar: Can I use it without paying anything?
Yes. The renderer is open source and self hostable. The hosted platform is a separate paid product.
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.
Scalar: Does it replace a full documentation site?
No. It covers API reference. Guides and concepts need a general documentation generator alongside it.
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.
Scalar: Will my reference go out of date?
Only if your OpenAPI document does. The reference is generated, so there is no second copy to forget.
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.
Scalar: Does the embedded client send real requests?
Yes, from the reader browser. Plan for CORS, rate limits and a sandbox environment before publishing.
Scalar: What if my API has no OpenAPI document?
Then this is the wrong tool. Producing an accurate spec is the prerequisite, not an optional step.
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 Redocly
- BookStack vs ReadMe
- BookStack vs Fumadocs
- BookStack vs Starlight
- BookStack vs Paligo
- Scalar vs Nuclino
- Scalar vs Slab
- Scalar vs MkDocs
- Scalar vs GitBook
- Scalar vs Outline
- Scalar vs Docsify
- Scalar vs HelpDocs
- Scalar vs Read the Docs
- Scalar vs Doxygen
- Scalar vs Guidde
- Scalar vs Sphinx
- Scalar vs Archbee
- Scalar vs Adobe FrameMaker
- Scalar vs Antora
- Scalar vs Bump.sh
- Scalar vs Redocly
- Scalar vs ReadMe
- Scalar vs Fumadocs
- Scalar vs Starlight
- Scalar vs Paligo