BookStack vs TYPO3

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 TYPO3 is

TYPO3 CMS is GPL-licensed open-source content-management software for self-managed PHP infrastructure. It supports Composer-based projects, relational databases, extensions and Long Term Support releases; free security support follows the current and preceding LTS lines, while older branches require migration or a paid Extended Long Term Support arrangement when offered.

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 TYPO3 is built to do

LTS releases

Provides defined support windows for current and preceding Long Term Support branches.

Composer projects

Manages core and extension dependencies in modern installation workflows.

Extension framework

Adds site and editorial functionality through system or third-party packages.

TypoScript configuration

Controls site rendering and behavior alongside PHP, templates and site configuration.

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

• Long-lived managed web platforms with explicit LTS and upgrade planning
• Teams versioning TYPO3 core and extensions through Composer
• Organizations able to own infrastructure, editorial training and extension governance

Skip TYPO3 if

• You want an all-inclusive hosted website builder without platform administration
• A required extension does not support a currently maintained LTS branch
• The organization cannot budget recurring upgrade projects or eligible ELTS coverage

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.

TYPO3: pros & cons

• LTS lifecycle: Current documentation defines regular LTS releases with bug and security support windows.
• Configuration flexibility: Composer projects can version core and extension dependencies.
• Database options: Current requirements document MySQL, MariaDB, PostgreSQL and SQLite support.
• Extension architecture: Core functionality can be expanded through system and third-party extensions.
• Infrastructure ownership: Web server, PHP, database, file permissions, deployment and backups remain customer responsibilities.
• Upgrade work: LTS transitions may change database structure, backend behavior, templates, CSS and system requirements.
• Extension lifecycle: Core support does not automatically guarantee maintenance or compatibility for every extension.
• Old-version cost: Branches outside free support require migration or eligible paid ELTS coverage.