BookStack: Managed Hosting, Installation and Operations

BookStack is a free, open-source wiki platform based on PHP/Laravel, specifically developed for self-hosted knowledge management. Content is structured into shelves, books, chapters, and pages - a logical hierarchy that's easy to understand for non-technical users. BookStack is MIT-licensed, multilingual, and usable for teams of any size.

Typical use cases are IT documentation, process manuals, project knowledge, onboarding guides, or internal knowledge bases. Due to its intuitive interface, full-text search, and clear structure, BookStack is suitable for smaller teams as well as larger organizations that want a self-hosted, privacy-friendly wiki.

Traditional wikis often work only with 'pages' and categories. BookStack uses a book metaphor (Shelves → Books → Chapters → Pages) and offers a modern, WYSIWYG-oriented interface with optional Markdown, revision management, and image/file handling. This significantly lowers the entry barrier for business departments.

Both are possible. Via roles & permissions, you can determine whether the instance is only usable internally or whether certain content is publicly readable (guest role). There's a global 'Allow public viewing' option and fine-grained permission management at shelf/book/page level.

The standard is a WYSIWYG editor with live preview and comfortable formatting. Additionally, there's a dedicated Markdown editor for text-heavy workflows. Via the integrated diagrams.net connection, diagrams can be created and maintained directly in the editor.

Yes. Content in shelves, books, chapters, and pages is fully searchable, including various navigation and filter options. This makes BookStack very well suited as a central knowledge base, even with larger documentation collections.

Permissions are controlled via roles assigned to specific users. Roles define which actions (read, write, export, admin, etc.) are allowed. Additionally, there are object permissions on shelves/books/chapters/pages ('Everyone else', role-based rights) that are finely controllable and inherited.

Yes. Images are managed as media, files as 'Attachments' that can be attached to pages and linked in content. Access to attachments is tied to read permission of the associated page; downloads are thus automatically protected by the permission system.

Uploads can be stored locally (incl. 'Local secure'/'secure restricted') or e.g. in S3-compatible storage. Access is controlled via BookStack permissions; optionally, filenames can be hardened with random strings ('Enable higher security image uploads'). WZ-IT complements this with server hardening, TLS, backups, and monitoring.

Yes. Users can enable MFA; supported are TOTP-based apps (e.g., Google/Microsoft Authenticator) as well as backup codes. MFA secrets are stored encrypted and can be made mandatory at role level. WZ-IT recommends MFA especially for admin and power user roles.

BookStack supports LDAP, SAML 2.0, OpenID Connect, and various social/enterprise providers (e.g., AzureAD, Okta). This makes it easy to integrate into existing identity providers (Keycloak, Authentik, Azure AD, etc.). WZ-IT handles the complete SSO integration on request.

Yes. There are integrated login options for providers like Google, GitHub, Slack, AzureAD, Okta, GitLab, Discord, and more. You can control whether users are automatically registered and/or email addresses automatically confirmed.

Typical are: hardening of the Linux stack, current PHP/database versions, TLS/TLS termination via reverse proxy, restrictive file permissions, logging & monitoring, securing uploads, and sensible role/permission concepts. Additionally - as needed - VPN/zero-trust access, SSO/MFA, backup strategy, and coordinated deletion/retention rules.

Officially supported are MySQL ≥ 5.7 and MariaDB ≥ 10.2 as relational databases for all content and metadata. BookStack uses a single database per instance. WZ-IT plans the DB architecture (backups, possibly replication) according to your requirements.

For small to medium teams, a lean VM or small server usually suffices; the official demo runs e.g. with 1 CPU and 512 MB RAM. What matters is user count, concurrent access, and upload volume. WZ-IT does sizing (CPU/RAM/storage) with you based on real usage scenarios.

Typical: Requirements & architecture workshop, selection of operating variant (managed hosting or BYOI), installation (Linux, webserver, DB, PHP), security (TLS, hardening), configuration (branding, roles, email), backup/monitoring concept and documentation. Optionally followed by training and a support/maintenance contract, including SLAs.

Yes. We handle operations, updates, backups, monitoring and maintenance on infrastructure in Germany or the EU, or in your cloud or on-premises environment. 24/7 monitoring is separate from support coverage; response times, phone callbacks and backup scope follow the agreed service level.

In settings, you can customize name, logo, and registration options, plus you can override views, texts, icons, and CSS via the theme system. WZ-IT assists with setting up a CI-compliant look & feel (logo, colors, login/start page, possibly custom HTML head).

Yes. There's an official 'Subdirectory Setup' guide for Apache and Nginx. Important are a correctly set APP_URL in .env and appropriate rewrite/proxy rules. WZ-IT sets up subdirectory or subdomain setups including TLS for you.

Multiple instances on one server are easily possible as long as each installation uses its own database and directory. 'Multi-tenant' operation from a single installation is currently not officially supported. WZ-IT plans sensible separations with you (e.g., per business unit or security zone).

Approach: clean foundation (current PHP, OPcache, caching/sessions properly configured), optimized DB parameters, right storage choice for uploads, and monitoring bottlenecks. With growing load, app and DB layers can be separated and possibly horizontally scaled. WZ-IT accompanies capacity planning and performance tuning.

Before each update, database and upload directories should be backed up. The PHP/Composer version must also match the respective release. A staging system for tests and reading the 'Updating' notes for breaking changes is sensible. WZ-IT handles updates on request as a recurring maintenance service.

At minimum, regular (e.g., daily) database backups and file backups of uploads should be made, preferably versioned and offsite. The official docs describe which directories are relevant. WZ-IT defines intervals, retention times, and encryption with you - plus monitoring of backup jobs.

Yes. We perform regular restore tests (test restores to staging) and can develop a disaster recovery concept with you - such as restart in a second zone/region or on different infrastructure. This clarifies how quickly you can be operational again with BookStack in an emergency.

BookStack can export books, chapters, and pages as HTML, PDF, and plain text, provided the role has the 'Export content' right. This is suitable for handouts, audits, or archiving. For mass exports or integrations, the REST API can be used.

Yes. A REST API with token authentication is available. API rights are tied to a special role permission ('Access system API'), i.e., access respects the normal permissions system. WZ-IT integrates BookStack e.g. with portals, search solutions, or internal tools.

BookStack offers webhooks that send HTTP POST requests to external systems on events (e.g., Discord, Teams, HomeAssistant, n8n). This enables workflows like notifications, syncs, or triggers in third-party systems. WZ-IT helps with conception and implementation.

Emails are sent via a configured SMTP server. This includes user invitations, password resets, and optional notifications. WZ-IT handles connection to your mail gateway (incl. TLS, authentication) as needed and tests mail flows during commissioning.

There are export/import functions (e.g., 'Portable ZIP'), plus content can be imported via REST API or manually from Office/Markdown. A typical path: structure mapping, pilot migration of one area, then successive transfer of the most important content. WZ-IT supports with mapping, scripts, and cutover plan.

Pragmatic: Provide a small VM/server, install BookStack per official guide, basic configuration (branding, language, email), create 1-2 example books and test with a pilot team. WZ-IT handles installation, basic configuration, and training on request - or provides a hosted test instance.

Yes, if you value self-hosting, transparency, and cost control. BookStack offers a clear, reduced feature set for documentation and knowledge - without the marketplace ecosystem like Confluence, but MIT-licensed and easy to operate. WZ-IT supports you with evaluation, incl. proof-of-concept and migration plan.

Notion is a SaaS service with very flexible content, but without self-hosting. BookStack is clearly designed as a self-hosted documentation platform: traceable data model, clean export/API options, and full infrastructure control. For privacy-critical scenarios (e.g., EU-only), BookStack is often the more suitable choice.

When the focus is on file storage, office collaboration, or audit-proof document workflows, solutions like Nextcloud or DMS systems are better suited. BookStack excels at structured, text-centric documentation where knowledge should be linked and searchable. WZ-IT combines BookStack and Nextcloud in an overall solution if needed.

BookStack is a solid Confluence alternative as a self-hosted wiki with clear structure, if you can live with a more focused feature set. Typical: gather requirements, set up test instance, structure mapping, pilot migration, then staged move. WZ-IT accompanies conception, migration (API/export), and operations.

BookStack is comparatively resource-efficient; even the public demo runs on 1 CPU/512 MB RAM. For 50-100 users, we typically recommend a dedicated VM with sufficient RAM/CPU and reserved storage for uploads & backups. Exact sizes and operating costs we clarify in a sizing & infrastructure workshop.

SaaS wikis minimize operational effort but are less flexible regarding data location, integrations, and cost structure. BookStack requires own hosting but offers full control, open-source license, and good integration capability. If you want to outsource operations, WZ-IT can provide BookStack as a managed service.

BookStack can be part of a privacy-focused architecture. Relevant controls include data location, roles and permissions, MFA/SSO, logging, encryption, backups, retention and deletion policies. WZ-IT implements the agreed technical controls; legal assessment remains with the controller and its privacy advisers.

Technically it's mostly a content project: define structure, transfer important documents into page content (copy & paste, possibly Markdown conversion), upload supplementary files as attachments. For larger volumes, scripts or API-based imports can help. WZ-IT supports with structure design, migration scripts, and training of editors.

Typical: BookStack authenticates via Keycloak (OIDC or SAML2, group sync), Nextcloud remains the file/collab platform. BookStack references Nextcloud files or embeds selected documents as attachments. WZ-IT designs an architecture with you featuring shared roles, SSO, and unified permission model.