BookStack vs Selenium

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

Selenium is an Apache-2.0-licensed open-source browser-automation project comprising WebDriver language bindings, Selenium IDE and Selenium Grid. It controls supported browsers locally or remotely, but it does not itself provide hosted browsers, application-specific test cases, assertions or a complete test runner; teams assemble and operate those surrounding parts.

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

WebDriver

Controls supported browsers through native browser automation interfaces and language bindings.

Selenium Grid

Routes sessions to remote browser instances for parallel and cross-platform execution.

Selenium IDE

Records and replays browser actions through supported browser extensions.

WebDriver BiDi

Adds bidirectional browser events such as network, console and JavaScript error streams.

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

• Cross-browser web tests that need supported language bindings and direct browser control
• Teams building their own local or distributed browser-testing infrastructure
• Projects willing to combine Selenium with an assertion library and test runner

Skip Selenium if

• You expect a hosted browser and device cloud to be included
• The team cannot maintain browser drivers, Grid capacity, selectors and synchronization logic
• The primary requirement is native mobile-app automation rather than browser or mobile-web automation

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.

Selenium: pros & cons

• Standards-based control: WebDriver is a W3C Recommendation implemented with browser-specific drivers.
• Language options: Official downloads list bindings for Java, Python, C#, Ruby, JavaScript and Kotlin.
• Distributed execution: Grid routes WebDriver commands to remote browser instances and supports parallel, cross-platform testing.
• Record and playback: Selenium IDE records browser actions through Chrome, Firefox and Edge extensions.
• Infrastructure not included: Local browsers, remote Grid machines or a separate hosted provider must supply execution capacity.
• Test framework required: Selenium documentation states that assertions and broader test structure come from assertion libraries and test runners.
• Environment maintenance: Browser, driver, language binding and Grid compatibility must be managed across updates.
• UI-change sensitivity: Application locators, timing and workflows still require deliberate test design and maintenance.