Softwr

Documentation · head to head

BookStack vs Jitsu

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Full reviewWebsite
Jitsu logo

Jitsu

Developer Tools

Open source event pipeline that streams behavioural data to your own warehouse

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.; Jitsu jitsu is a pipeline, not a customer data platform, so identity resolution, audience building and reverse ETL are absent and a marketing team expecting Segment parity will be disappointed.
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Jitsu covers Event collection.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which BookStack and Jitsu actually diverge.

Attributes where BookStack and Jitsu differ
AttributeBookStackJitsu
Pricing modelOpen source, no licence feePer month by event volume
PlatformsWeb, Self-hosted, DockerWeb, Linux, Docker, Kubernetes, iOS, Android
CategoryDocumentationDeveloper Tools

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 Jitsu

  • Event collection
  • Warehouse destinations
  • Connector syncs
  • Transformations
  • Bundled ClickHouse
  • Event debugger
  • Self-hosting
  • Custom domains

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

Jitsu

  • A team paying five figures a year to a customer data platform when all it actually does is send events to Snowflakenot BookStack
  • An engineering group that needs event collection running inside its own VPC for data residency or security review reasonsnot BookStack
  • A product analytics setup that wants raw events in the warehouse as the source of truth rather than trapped in a vendor toolnot BookStack
  • A startup that needs first-party event collection on its own domain to reduce loss from tracker blocking without paying CDP pricesnot 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.

Jitsu

  • Jitsu is a pipeline, not a customer data platform, so identity resolution, audience building and reverse ETL are absent and a marketing team expecting Segment parity will be disappointed.
  • Connector sync frequency is deliberately tiered, with the free plan limited to manual runs and one daily sync, so anything approaching operational freshness requires the paid plan or self-hosting.
  • Self-hosting means you own the reliability of a system that drops data silently when misconfigured, and event loss is uniquely hard to notice because nothing errors, the numbers are just quietly lower.
  • The connector catalogue is far smaller than Fivetran or Airbyte, so if your requirement is pulling from many SaaS sources rather than pushing events, Jitsu is the wrong half of the problem.
  • It is a small company with a small commercial team, so enterprise procurement processes around security review, contractual SLAs and support escalation take longer than with an incumbent vendor.

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

Jitsu

Free
  • Open SourceFree
    • MIT licence
    • Self-host on any cloud
    • No usage limits
  • Cloud FreeFree
    • Unlimited captured events
    • 200,000 active events per month
    • Manual connector runs only
  • Business$99/month
    • 2,000,000 active events per month
    • $40 per additional million events
    • Hourly connector sync frequency
  • Enterprise$undefined/year
    • Custom event volume
    • One minute sync frequency
    • Unlimited active syncs

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 Jitsu if

  • You need event collection.
  • You want to start without paying.
  • You work on Web, Linux, Docker, Kubernetes, iOS, Android.
  • You also want warehouse destinations.
Jitsu review

Questions people ask

Is BookStack or Jitsu better?
Neither clearly leads. BookStack starts at Free and Jitsu at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Jitsu?
BookStack starts at Free and Jitsu at Free.
Does BookStack or Jitsu run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Jitsu runs on Web, Linux, Docker, Kubernetes, iOS, Android.
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 Jitsu is typically brought in for.
What can BookStack do that Jitsu cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Jitsu covers Event collection, Warehouse destinations, Connector syncs, Transformations.

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.

Jitsu: Is Jitsu the same as Jitsi?

No. Jitsu is an open source event data pipeline. Jitsi is an unrelated video conferencing project.

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.

Jitsu: Can I self-host for free?

Yes. The project is MIT licensed with no usage limits when self-hosted.

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.

Jitsu: How does the cost compare with Segment?

The Business plan is 99 US dollars a month for two million active events, where a per-tracked-user CDP typically costs orders of magnitude more at comparable volume.

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.

Jitsu: Does Jitsu do identity resolution?

No. It transports and transforms events; identity stitching and audiences are not part of the product.

Share

Related pages

More on BookStack

More on Jitsu

Keep looking

Other head to heads