Documentation · head to head
BookStack vs Soketi
BookStack
Documentation
Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure
- From
- Free
- Rated
- -
Soketi
Developer Tools
Self-hosted, Pusher-compatible WebSockets server with a stalled maintenance record
- 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.; Soketi maintenance has effectively stalled: the maintainer has said time is severely limited, releases are infrequent, and the community has been discussing whether the project is abandoned, which means security fixes may not arrive.
- They diverge on capability: BookStack covers Shelves, books, chapters, pages, Soketi covers Pusher protocol compatibility.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which BookStack and Soketi actually diverge.
Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 Soketi
- Pusher protocol compatibility
- Presence and private channels
- Horizontal scaling
- App management backends
- Webhooks
- Prometheus metrics
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 Soketi
- Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki producesnot Soketi
- Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suitenot Soketi
- Publishing customer-facing manuals from the same instance as internal documentation using per-book permissionsnot Soketi
Soketi
- A Laravel application that already uses Echo and wants to stop paying a hosted realtime providernot BookStack
- Realtime notifications or presence indicators where data must not leave your own infrastructure for compliance reasonsnot BookStack
- A local or CI environment that needs a Pusher-compatible server without hitting a paid accountnot BookStack
- A high-connection-count application where hosted per-connection pricing has become the largest line in the infrastructure billnot 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.
Soketi
- Maintenance has effectively stalled: the maintainer has said time is severely limited, releases are infrequent, and the community has been discussing whether the project is abandoned, which means security fixes may not arrive.
- Dependency drift on Node and uWebSockets.js will eventually force you to fork or migrate, and that cost is unbudgeted at the point you adopt it.
- There is no commercial support to buy, so a production incident at three in the morning is entirely your problem with no escalation path.
- Scaling beyond a single node needs Redis and careful configuration, and getting presence channels correct across nodes is a genuine source of subtle bugs.
- It implements the Pusher protocol rather than tracking it, so any protocol feature Pusher adds later will not appear, and the compatibility guarantee slowly decays.
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
Soketi
Free- SoketiFree
- MIT licensed
- Unlimited connections subject to your own hardware
- No vendor billing
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 Soketi if
- You need pusher protocol compatibility.
- You want to start without paying.
- You work on Linux, macOS, Windows.
- You also want presence and private channels.
Questions people ask
- Is BookStack or Soketi better?
- Neither clearly leads. BookStack starts at Free and Soketi at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BookStack or Soketi?
- BookStack starts at Free and Soketi at Free.
- Does BookStack or Soketi run on more platforms?
- BookStack runs on Web, Self-hosted, Docker. Soketi runs on Linux, macOS, Windows.
- 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 Soketi is typically brought in for.
- What can BookStack do that Soketi cannot?
- BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Soketi covers Pusher protocol compatibility, Presence and private channels, Horizontal scaling, App management backends.
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.
Soketi: Is Soketi still maintained?
Barely. The maintainer has stated that available time is very limited and releases have been sparse; treat it as community-maintained.
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.
Soketi: Do I need to change my client code?
No. Pusher client SDKs and Laravel Echo work by changing the host, port and credentials.
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.
Soketi: What does it cost?
Nothing in licence fees. It is MIT licensed; you pay for the server it runs on.
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.
Soketi: What are people moving to?
Laravel Reverb for Laravel applications, and Sockudo, a Rust reimplementation, for others.
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 PartyKit
- BookStack vs Penpot
- BookStack vs Atlantis
- BookStack vs Coder
- BookStack vs Backstage
- BookStack vs Visual Studio Code
- BookStack vs GNU Emacs
- BookStack vs Bazel
- BookStack vs Eclipse IDE
- BookStack vs Pants Build
- BookStack vs Swagger UI
- BookStack vs Ansible
- BookStack vs Cody
- BookStack vs ConfigCat
- BookStack vs Cortex
- BookStack vs Dagger
- BookStack vs Deno
- BookStack vs Fig
- Soketi vs Nuclino
- Soketi vs Slab
- Soketi vs MkDocs
- Soketi vs GitBook
- Soketi vs Outline
- Soketi vs Docsify
- Soketi vs HelpDocs
- Soketi vs Read the Docs
- Soketi vs Doxygen
- Soketi vs Guidde
- Soketi vs Sphinx
- Soketi vs Archbee
- Soketi vs Adobe FrameMaker
- Soketi vs Antora
- Soketi vs Bump.sh
- Soketi vs PartyKit
- Soketi vs Penpot
- Soketi vs Atlantis
- Soketi vs Coder
- Soketi vs Backstage
- Soketi vs Visual Studio Code
- Soketi vs GNU Emacs
- Soketi vs Bazel
- Soketi vs Eclipse IDE
- Soketi vs Pants Build
- Soketi vs Swagger UI
- Soketi vs Ansible
- Soketi vs Cody
- Soketi vs ConfigCat
- Soketi vs Cortex
- Soketi vs Dagger
- Soketi vs Deno
- Soketi vs Fig