Softwr

Documentation · head to head

BookStack vs Sakai

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
Full reviewWebsite
Sakai logo

Sakai

LMS

Open source learning management system governed by the Apereo Foundation

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.; Sakai the zero licence fee is misleading: running Sakai needs Java operations, database administration and upgrade testing capacity, and universities that costed only the hardware have ended up paying a hosting partner anyway.
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, Sakai covers Course sites.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which BookStack and Sakai actually diverge.

Attributes where BookStack and Sakai differ
AttributeBookStackSakai
PlatformsWeb, Self-hosted, DockerWeb, Linux, iOS, Android
CategoryDocumentationLMS

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 Sakai

  • Course sites
  • Tests and Quizzes
  • Gradebook
  • Lessons
  • Assignments
  • Forums and messaging
  • LTI support
  • Self-hosting

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

Sakai

  • A university whose data protection policy or national regulation requires student coursework to stay on institution-controlled infrastructure inside a specific jurisdiction.not BookStack
  • An institution that has been repriced twice by a commercial LMS vendor after ownership changes and wants a platform with no owner to sell it.not BookStack
  • A university with an existing Java and Tomcat operations team, where the marginal cost of running one more Java application is genuinely low.not BookStack
  • A consortium of institutions sharing one deployment and one set of local integrations rather than each paying separate per-student licences.not 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.

Sakai

  • The zero licence fee is misleading: running Sakai needs Java operations, database administration and upgrade testing capacity, and universities that costed only the hardware have ended up paying a hosting partner anyway.
  • The third-party teaching tool ecosystem builds and tests for Canvas first, so Sakai adopters do their own LTI integration work and occasionally wait for a vendor to certify against a platform it does not prioritise.
  • Because governance is a foundation of member institutions rather than a company, a feature only gets built if some institution funds an engineer to build it, so roadmap commitments are weaker than a vendor contract provides.
  • The interface, while improved through the version 20 to 25 cycle, still reads as older than Canvas or Brightspace, and academic staff who have used a commercial LMS elsewhere notice it immediately.
  • Adoption is concentrated in specific regions and sectors, so the pool of people who have run Sakai in production is small, making it harder to hire an administrator than for Moodle or Canvas.

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

Sakai

Free
  • SakaiFree
    • Educational Community Licence, no licence fee
    • Full source on GitHub
    • Community support through Apereo lists and Jira
  • Commercial hosting and support$undefined/year
    • Provided by Apereo affiliates such as Longsight
    • Hosting, upgrades, backups and support
    • Quoted per institution, commonly by student headcount

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

  • You need course sites.
  • You want to start without paying.
  • You work on Web, Linux, iOS, Android.
  • You also want tests and quizzes.
Sakai review

Questions people ask

Is BookStack or Sakai better?
Neither clearly leads. BookStack starts at Free and Sakai at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or Sakai?
BookStack starts at Free and Sakai at Free.
Does BookStack or Sakai run on more platforms?
BookStack runs on Web, Self-hosted, Docker. Sakai runs on Web, Linux, 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 Sakai is typically brought in for.
What can BookStack do that Sakai cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. Sakai covers Course sites, Tests and Quizzes, Gradebook, Lessons.

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.

Sakai: Is Sakai still actively developed?

Yes. Version 25.0 shipped in 2025, 25.1 followed in November 2025, and further maintenance releases in the 25 line are planned, with commits continuing through 2026.

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.

Sakai: Who owns Sakai?

No company does. Governance sits with the Apereo Foundation, a membership organisation of institutions, and the code is under the Educational Community Licence.

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.

Sakai: What does it actually cost to run?

The software is free. The cost is Java hosting and staff, or a commercial hosting agreement with an Apereo affiliate such as Longsight, typically quoted by student headcount.

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.

Sakai: How does it compare to Moodle?

Moodle has a far larger plugin ecosystem and installed base; Sakai has a cleaner assessment and gradebook model and is more common in research-intensive universities. Moodle is easier to hire for.

Sakai: Can we migrate off it later?

Yes, but course content export fidelity through Common Cartridge is imperfect, so budget for manual rebuilding of assessments as you would leaving any LMS.

Share

Related pages

More on BookStack

More on Sakai

Keep looking

Other head to heads