BookStack vs OceanBase

What BookStack is

BookStack is an MIT-licensed, self-hosted documentation application built around shelves, books, optional chapters and pages. It provides role and content-level permissions, multiple enterprise authentication options and a permission-aware REST API, but the operator remains responsible for the PHP and database stack, upgrades, filesystem permissions, security configuration and complete database-plus-file backups.

What OceanBase is

OceanBase Database is an Apache-2.0 distributed relational database designed for transactional and analytical workloads. Community Edition provides MySQL mode, multitenancy, distributed transactions, replication and horizontal scaling; it is not a complete replacement for every MySQL feature. A single-node deployment is intended for evaluation and lacks distributed high availability, while the documented standard production topology starts with at least three suitably resourced hosts. Enterprise products, cloud service and commercial support are separate decisions.

What BookStack is built to do

Book hierarchy

Organizes page content within optional chapters, books and reusable bookshelves.

Roles and permissions

Combines system roles with content-level overrides and inherited controls.

Federated authentication

Documents OIDC, SAML 2.0 and LDAP configuration for self-hosted instances.

REST API

Provides token-authenticated JSON endpoints governed by the API user's permissions.

What OceanBase is built to do

Distributed SQL

Runs relational transactions across a Paxos-backed distributed architecture.

MySQL mode

Offers broad, but explicitly incomplete, compatibility with MySQL 5.7 behavior.

Multitenancy

Separates database tenants and their resources within an OceanBase cluster.

Flexible deployment

Supports standalone evaluation and multi-host production deployment through official tools.

Choose BookStack if

• Internal handbooks, runbooks and technical knowledge bases with a clear hierarchy
• Organizations needing self-hosting, role controls and supported identity integrations
• Teams that can automate upgrades, database and file backups, and restore drills

Skip BookStack if

• You need a vendor-operated SaaS with no infrastructure responsibility
• Your information model cannot fit shelves, books, chapters and pages
• You cannot preserve the database, uploads, configuration and original APP_KEY together

Choose OceanBase if

• High-scale transactional systems that need horizontal growth and replicated availability
• MySQL-origin applications after a representative compatibility and migration assessment
• Teams able to operate a three-or-more-host database cluster or procure managed service

Skip OceanBase if

• A simple single-node relational database meets the workload and recovery requirements
• The application assumes complete MySQL or Oracle compatibility without testing
• The team cannot staff cluster operations, monitoring, upgrades and restore drills

BookStack: pros & cons

• Predictable structure: Shelves, books, chapters and pages give teams a constrained documentation hierarchy.
• Granular access: Roles can be combined and overridden at shelf, book, chapter or page level.
• Authentication choices: Official administration docs cover OpenID Connect, SAML 2.0 and LDAP.
• Automation surface: The REST API covers content and administrative resources while enforcing the API user's roles and permissions.
• Self-hosting burden: PHP, MySQL or MariaDB, web-server configuration, updates and monitoring are operator responsibilities.
• Manual recovery design: There is no built-in full backup and restore; both database records and instance files must be protected.
• Key dependency: Restores need the original APP_KEY for encrypted features such as multi-factor credentials.
• Hierarchy trade-off: The book metaphor is approachable but may constrain teams needing free-form graphs or complex publishing workflows.

OceanBase: pros & cons

• Open core database: The main OceanBase Database repository is available under Apache License 2.0.
• Distributed architecture: Paxos-based replication, multitenancy and scale-out target high-availability transactional systems.
• MySQL migration path: Community Edition supports most MySQL 5.7 syntax and features plus selected MySQL 8.0 JSON functions.
• Deployment options: Official tooling covers quick standalone evaluation, standard clusters, containers and Kubernetes.
• Compatibility is partial: Unsupported syntax, functions, backup behavior and architectural differences require application-level testing.
• Meaningful production footprint: The documented standard cluster requires at least three hosts, each starting at 4 vCPU, 16 GB RAM and 100 GB SSD.
• Operational burden: Topology, tenants, storage, upgrades, observability, backup and recovery demand distributed-database expertise.
• Edition boundaries: Oracle mode, management features and expert support differ between Community, Enterprise and Cloud offerings.