Softwr

Documentation · head to head

BookStack vs MySQL

BookStack logo

BookStack

Documentation

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

From
Free
Rated
-
MySQL logo

MySQL

Web Development

The world's most popular open source database

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.; MySQL hot online backup is not in the free Community Server; MySQL Enterprise Backup is a paid Enterprise Edition component
  • They diverge on capability: BookStack covers Shelves, books, chapters, pages, MySQL covers ACID compliance.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which BookStack and MySQL actually diverge.

Attributes where BookStack and MySQL differ
AttributeBookStackMySQL
Pricing modelOpen source, no licence feefreemium
PlatformsWeb, Self-hosted, DockerWindows, Macos, Linux, Unix
CategoryDocumentationWeb Development
FoundedUnknown1995

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 MySQL

  • ACID compliance
  • SQL support
  • Multi-version concurrency control
  • Replication
  • Partitioning
  • Stored procedures
  • Triggers
  • Views

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

MySQL

  • Web application backendnot BookStack
  • E-commerce platformsnot BookStack
  • Content management systemsnot BookStack
  • Data warehousingnot BookStack
  • Business applicationsnot 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.

MySQL

  • Hot online backup is not in the free Community Server; MySQL Enterprise Backup is a paid Enterprise Edition component
  • Transparent Data Encryption, data masking and de-identification are Enterprise Edition only
  • MySQL Enterprise Firewall, which guards against SQL injection, and MySQL Enterprise Audit are both paid components
  • External authentication against PAM or Windows Active Directory requires MySQL Enterprise Authentication
  • The thread pool ships as MySQL Enterprise Scalability rather than in the community build

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

MySQL

Free
  • Community EditionFree
    • Open source license
    • Full SQL support
    • InnoDB storage engine
  • Standard Edition$2000/year
    • Commercial license
    • Oracle Premier Support
    • MySQL Enterprise backup
  • Enterprise Edition$5000/year
    • Advanced security
    • MySQL Enterprise Monitor
    • High Availability

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

  • You need acid compliance.
  • You want to start without paying.
  • You work on Windows, Macos, Linux, Unix.
  • You also want sql support.

Questions people ask

Is BookStack or MySQL better?
Neither clearly leads. BookStack starts at Free and MySQL at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BookStack or MySQL?
BookStack starts at Free and MySQL at Free.
Does BookStack or MySQL run on more platforms?
BookStack runs on Web, Self-hosted, Docker. MySQL runs on Windows, Macos, Linux, Unix.
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 MySQL is typically brought in for.
What can BookStack do that MySQL cannot?
BookStack covers Shelves, books, chapters, pages, Dual editors, Granular permissions, Full text search. MySQL covers ACID compliance, SQL support, Multi-version concurrency control, Replication.

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.

MySQL: Does MySQL cost money?

MySQL is primarily open-source and free to use. Commercial editions and support services are available but pricing is not published on the main website.

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.

MySQL: How do I get MySQL pricing information?

For MySQL commercial editions and support pricing, customers can contact MySQL sales directly at +1-866-221-0634 or navigate to individual product pages.

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

Other head to heads