BookStack vs MapTiler

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

MapTiler combines a proprietary hosted map service with APIs, map styles, global datasets and upload hosting. Its JavaScript SDK is public and BSD-licensed, but that license does not make MapTiler Cloud, built-in styles or map data open source. Cloud access requires authenticated requests, and plan rules govern commercial use, quotas, overage and attribution. The Free plan is limited to non-commercial use and R&D for commercial products, so public commercial launches need an appropriate paid agreement.

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

Interactive map SDK

Renders browser maps through a BSD-licensed SDK built on MapLibre GL JS.

Hosted maps and styles

Serves MapTiler styles, tiles and uploaded geospatial data from Cloud.

Location APIs

Provides authenticated mapping and location services through API requests.

Plan-based usage

Meters map sessions, searches, requests, processing and storage according to plan.

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

• Interactive web maps using MapLibre-compatible tooling and managed global map delivery
• Prototypes whose use genuinely fits the Free plan terms and quotas
• Commercial products after forecasting sessions, requests, storage and required support

Skip MapTiler if

• A commercial production launch is expected to remain on the Free plan
• The project cannot display required attribution or satisfy underlying data licenses
• Offline or self-hosted operation is mandatory but the applicable product and license have not been validated

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.

MapTiler: pros & cons

• Integrated web-map stack: Hosted tiles, styles, geocoding and other APIs connect through one account and key system.
• Open SDK code: MapTiler SDK JS is BSD-licensed and extends the open-source MapLibre GL JS renderer.
• Usage-based growth path: Free, Flex and Custom plans support prototypes through larger deployments.
• Attribution guidance: Official documentation explains required text, links and Free-plan logo treatment across media.
• Free is not a general commercial plan: Terms restrict it to non-commercial use and commercial-product research and development.
• Service and data remain licensed: Open SDK code does not grant unrestricted rights to hosted tiles, styles or datasets.
• Variable operating cost: Sessions, API requests, data processing, 3D use and storage can create separate charges or limits.
• Client keys need governance: Browser and mobile integrations expose API keys by design, so restrictions and monitoring are essential.