Softwr

Documentation · head to head

BookStack vs PocketBase

BookStack logo

BookStack

Documentation

Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure

From
Free
Rated
-
Full reviewWebsite
PocketBase logo

PocketBase

APIs

Open-source backend with REST API, real-time subscriptions and Admin UI

From
Free
Rated
-
Full reviewWebsite

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.; PocketBase requires technical expertise to deploy and maintain
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, PocketBase covers Real-time subscriptions.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and PocketBase actually diverge.

Attributes where BookStack and PocketBase differ
AttributeBookStackPocketBase
Pricing modelOpen source, no licence feeUnknown
PlatformsWeb, Self-hosted, DockerLinux, Windows, macOS, FreeBSD
CategoryDocumentationAPIs
FoundedUnknown2021

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
  • External authentication
  • Export
  • Audit log

Only in PocketBase

  • Real-time subscriptions
  • Admin UI
  • SQLite
  • Webhooks
  • File storage
  • Go support
  • Docker support
  • Self-hosted support

Both cover

  • REST API

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 PocketBase
  • Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot PocketBase
  • Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot PocketBase
  • Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot PocketBase

PocketBase

  • Embedded realtime database with REST APInot BookStack
  • Backend-as-a-service for single-file deploymentsnot BookStack
  • Rapid application development with email/OAuth2 authenticationnot BookStack
  • File storage and media attachment managementnot BookStack
  • Lightweight alternative to Firebase or traditional backend infrastructurenot BookStack
  • Go and JavaScript customisable application frameworknot 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.

PocketBase

  • Requires technical expertise to deploy and maintain
  • No built-in hosting provided
  • Community support only

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

PocketBase

Free

No published plan breakdown. See the PocketBase 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.
BookStack review

Choose PocketBase if

  • You need real-time subscriptions.
  • You want to start without paying.
  • You work on Linux, Windows, macOS, FreeBSD.
  • You also want admin ui.
PocketBase review

Questions people ask

Is BookStack or PocketBase better?
Neither clearly leads. BookStack starts at Free and PocketBase at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or PocketBase?
BookStack starts at Free and PocketBase at Free.
Does BookStack or PocketBase run on more platforms?
BookStack runs on Web, Self-hosted, Docker. PocketBase runs on Linux, Windows, macOS, FreeBSD.
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 PocketBase is typically brought in for.
What can BookStack do that PocketBase cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. PocketBase covers Real-time subscriptions, Admin UI, SQLite, Webhooks. Both handle REST API.

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.

PocketBase: How much does PocketBase cost?

PocketBase is completely free and open-source. It is a self-hosted backend solution with database, authentication, and file storage capabilities at no cost.

Source
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.

PocketBase: Is PocketBase open-source?

Yes, PocketBase is open-source software. You can download, modify, and deploy it yourself at no cost with no licensing restrictions.

Source
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.

Share

Related pages

More on BookStack

More on PocketBase

Keep looking

Other head to heads