IT services / Guide

Knowledge bases and wikis: SharePoint, Confluence, OpenProject, BookStack, XWiki, Docmost…

What a knowledge base is for, the criteria that matter, and a comparison of proprietary and open source solutions, online or self-hosted. With a BookStack deployment on Docker and the rules for documentation that stays up to date.

IT services Guide All levels Published October 20, 2026 Translated November 20, 2026 20 min read Version française
Wooden shelves full of books in a library
Photo: Peter Herrmann on Unsplash

Before you start

In plain words

A knowledge base is the team's written memory. Without it, knowledge is in a few people's heads: when they're away or leave, everything stops. With it, the procedure for resetting the firewall, the guest Wi-Fi password or the steps for a newcomer are stored in the same place, like in a well-organised library: you know where to look, and you find it.

No prices are given here: offers change often. Information checked on 20 October 2026.

1. The different uses

The term "knowledge base" covers several needs. Identifying them avoids choosing an unsuitable tool.

Use What goes in it Readers Typical tools
Internal wiki Organisation, rules, directory of departments, onboarding The whole company SharePoint, Confluence, BookStack, XWiki
Technical documentation Architecture, operating procedures (runbooks), server configuration IT team, developers Confluence, BookStack, Wiki.js, Docmost
Support knowledge base Solutions to frequent incidents, FAQs for users Technicians and users Knowledge base built into the helpdesk software (GLPI, Zammad…), Confluence
Project documentation Minutes, decisions, specifications linked to tasks Project team OpenProject, Confluence with Jira, Notion
Personal notes Memos, links, homelab experiments Just you Obsidian, Joplin, BookStack, DokuWiki

A single source of truth

The worst scenario is having the same procedure in three places, in three different versions. Choose one main tool for documentation, and link to it from the others (ticket, project task, conversation).

2. What makes a knowledge base useful

Before comparing products, here are the criteria that really matter day to day.

Criterion Why it matters
Effective search If you can't find it in ten seconds, you stop looking. Search should cover page text, and ideally attachments (PDF, Word).
Clear structure Spaces, books, chapters or a tree: a readable hierarchy helps store and find things.
Pleasant editor A visual editor for everyone, Markdown for technicians. If writing is a chore, nobody writes.
Fine-grained access rights Some pages (sensitive procedures, HR) mustn't be visible to everyone.
Version history Knowing who changed what, comparing and rolling back.
Single sign-on (SSO) Signing in with the company account (Active Directory/LDAP, Entra ID, SAML, OpenID Connect) rather than yet another account. See identity management.
Page templates A procedure or minutes template gives consistent pages.
Export and reversibility Being able to get everything back (HTML, Markdown, PDF) the day you change tool.
Diagrams Built-in diagrams (draw.io/diagrams.net, Mermaid) for network architecture.

3. Proprietary solutions

Microsoft SharePoint

SharePoint is the document building block of Microsoft 365: team and communication sites, document libraries, pages, lists. If the company already uses Microsoft 365, it's already available, integrated with Teams (each Teams team has its SharePoint site) and OneDrive.

  • Strengths: Office integration (co-editing Word/Excel), rights based on Entra ID accounts, Microsoft Search, governance (sensitivity labels, retention), Copilot depending on licences.
  • Limits: excellent for storing documents, less natural for writing a wiki: SharePoint pages are designed more for internal communication. Permissions quickly become complex if they're not framed from the start.
  • On-premises: SharePoint Server Subscription Edition is still available and supported until at least 31 December 2035. SharePoint Server 2016 and 2019 have been out of support since 14 July 2026: a farm still on these versions must migrate.

SharePoint as a wiki

For wiki use, create a dedicated communication site, with navigation by main topic, and keep document libraries for files. Site pages are searchable and can serve as a simple knowledge base.

Atlassian Confluence

Confluence is the historical reference for the corporate wiki, widely used by technical teams, especially combined with Jira for task tracking.

  • Strengths: rich editor, spaces per team, many templates, macros, Jira integration, catalogue of extensions (Marketplace).
  • Limits: the offer is becoming exclusively online (Cloud). Atlassian ended the Server offer in February 2024, then announced the end of Data Center, its self-installed version:
Date Stage for Confluence/Jira Data Center
30 March 2026 End of sales of new licences
30 March 2028 End of sales to existing customers (including licence extensions)
28 March 2029 End of life: no more support or fixes, licences expired, instances read-only

Confluence installed on your own servers

If your organisation uses Confluence Data Center, you need to decide before 2029: move to Atlassian's Cloud (with its offers for sensitive data), or migrate to another solution. The open source tools XWiki and Docmost offer Confluence imports, which makes them the most frequent destinations.

Notion

Notion mixes pages, databases and tasks in a very flexible interface. It's an excellent tool for a small team or personal use, but it's online only, hosted in the United States, and its flexibility can produce a messy workspace without filing rules. For sensitive data, read the cloud comparison on the question of sovereignty.

4. OpenProject: documentation serving the project

OpenProject isn't primarily a wiki: it's open source project management software (GPLv3 licence) (tasks, Gantt charts, agile boards, meetings, time tracking). It includes a wiki per project and a Documents module.

  • Since version 17.0 (January 2026), Documents support real-time collaborative editing (other participants' cursors, automatic saving, links to tasks). This feature needs a synchronisation server (Hocuspocus), included in the Cloud offer and the container installation, but not by default in the DEB/RPM package installation.
  • Integrations with Nextcloud and with SharePoint/OneDrive to link files to tasks.
  • Two editions: Community (open source, complete for most needs) and Enterprise (extra features, support). Available as Cloud or to install yourself.

Choose it if documentation is tied to projects (minutes, decisions, deliverables). For the IT team's general knowledge base, a real wiki remains more comfortable, and the two can coexist.

5. Open source alternatives to host yourself

Solution Licence Technology Organisation Strengths Limits
BookStack MIT PHP, MySQL/MariaDB Shelves, books, chapters, pages Very easy to get started, LDAP/SAML/OIDC included, fine-grained rights, PDF/HTML/Markdown export Fixed 4-level structure
Wiki.js AGPL-3.0 Node.js, PostgreSQL Free-form tree Native Markdown, Git synchronisation, nice rendering Version 2.5 stable but little development; 3.0 is still in beta, not recommended for production
XWiki LGPL-2.1 Java, SQL database Nested spaces and pages Very complete, structured applications, Confluence migration tool Heavier to install and administer; some extensions are paid
Docmost AGPL-3.0 (Community edition) Node.js, PostgreSQL Spaces and pages Modern interface close to Confluence/Notion, real-time collaborative editing, built-in diagrams SSO, MFA and Confluence import reserved for paid editions
Outline BSL 1.1 (source available, not an open source licence) Node.js, PostgreSQL Collections and documents Very fast, pleasant editor, Slack integration No local account with a password: sign-in through SSO or an emailed link; restrictive licence for commercial use as a service
Docs (La Suite numérique) MIT Python/Django, React Documents and subpages Real-time collaborative editing, export, designed for the French and German public administrations Closer to a shared document editor than a highly structured wiki
DokuWiki GPL-2.0 PHP, no database (text files) Namespaces Ultra-light, backed up by simply copying a folder, many plug-ins DokuWiki-specific syntax, dated interface
MediaWiki GPL-2.0 PHP, MySQL/MariaDB Pages and categories Wikipedia's engine, robust for very large volumes Designed for a public wiki, administration and permissions poorly suited to businesses

What "open source" means here

An open source licence (MIT, GPL, AGPL, LGPL) allows you to use, study, modify and redistribute the software. "Source-available" licences such as Outline's BSL show the code, but restrict some uses. For internal use, the difference is often minor; to offer the service to customers, read the licence.

6. What to choose?

Situation Recommended choice Why
Homelab, personal notes BookStack or DokuWiki Light, easy to back up, run in a small container
Small IT team, self-hosted BookStack The best balance of simplicity and features, SSO included in the open source version
Team used to Confluence or Notion Docmost or XWiki Similar interface, import from Confluence
Business already on Microsoft 365 SharePoint (and Loop for collaborative work) Already included in Microsoft 365, integrated with accounts and permissions
Developer team Wiki.js 2.5 with Git, or documentation in the code repository Documentation follows the code and its reviews
Project management with documentation OpenProject Tasks, meetings and documents in one place
Public sector, sovereignty requirement La Suite numérique's Docs, XWiki, BookStack hosted in Europe Open source software, controlled hosting
Large organisation, advanced needs Confluence Cloud, SharePoint or XWiki Governance, volume, vendor support

Test with real content

Before choosing, write three real pages in two or three tools: a procedure, minutes, an architecture page with a diagram. Have a colleague test the search. It tells you more than any comparison.

7. Example: BookStack with Docker Compose

BookStack is a good starting point for a team or a homelab. This example uses the image maintained by LinuxServer.io and MariaDB. If Docker Compose is new to you, start with the Docker Compose guide.

Step 1. Create the service folder:

mkdir -p /opt/bookstack && cd /opt/bookstack

Step 2. Generate the session encryption key:

docker run -it --rm --entrypoint /bin/bash \
  lscr.io/linuxserver/bookstack:latest appkey

The command shows a line starting with base64:. Copy all of it.

Step 3. Create the .env file, which holds the secrets, and protect it:

cat > .env <<'EOF'
APP_KEY=base64:paste-the-generated-key-here
DB_PASSWORD=a-long-unique-password
DB_ROOT_PASSWORD=another-long-password
EOF
chmod 600 .env

Step 4. Create the compose.yaml file:

services:
  bookstack:
    image: lscr.io/linuxserver/bookstack:latest
    container_name: bookstack
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - APP_URL=https://wiki.example.lan
      - APP_KEY=${APP_KEY}
      - DB_HOST=bookstack-db
      - DB_PORT=3306
      - DB_USERNAME=bookstack
      - DB_PASSWORD=${DB_PASSWORD}
      - DB_DATABASE=bookstack
    volumes:
      - ./config:/config
    ports:
      - 6875:80
    depends_on:
      - bookstack-db
    restart: unless-stopped

  bookstack-db:
    image: mariadb:11.8
    container_name: bookstack-db
    environment:
      - MARIADB_ROOT_PASSWORD=${DB_ROOT_PASSWORD}
      - MARIADB_DATABASE=bookstack
      - MARIADB_USER=bookstack
      - MARIADB_PASSWORD=${DB_PASSWORD}
    volumes:
      - ./db:/var/lib/mysql
    restart: unless-stopped

Adapt TZ to your time zone.

Step 5. Start and check:

docker compose up -d
docker compose logs -f bookstack

Step 6. Open http://server-address:6875. Log in with the default account admin@admin.com and the password password, then immediately change this account's address and password in My Account.

Things to set before opening the service

  • APP_URL must match exactly the address users will use, otherwise links and images will be broken.
  • Put BookStack behind a reverse proxy with HTTPS (Caddy, Traefik, Nginx Proxy Manager) and don't expose port 6875 on the internet.
  • Create a named account per user or connect the directory (LDAP, SAML or OIDC): no shared account.

Backup: you need to back up the database and the files (images, attachments in ./config). Example of a database backup:

docker exec bookstack-db sh -c 'mariadb-dump -u root -p"$MARIADB_ROOT_PASSWORD" bookstack' \
  > /opt/backups/bookstack-$(date +%F).sql

Then include the /opt/bookstack folder and the exports in your usual backup (see the 3-2-1 rule and Restic) and test a restore.

8. Keeping the documentation alive

The tool matters less than the habits. A knowledge base dies when nobody trusts it any more.

  1. Define a simple structure from the start, for example: Infrastructure, Network, Workstations, Applications, Emergency procedures, Onboarding and organisation.
  2. Use templates for recurring page types (procedure, server page, incident report).
  3. Name an owner for each page or section, responsible for keeping it up to date.
  4. Show a last-checked date and schedule a review (every six months for critical procedures).
  5. Write as you do: a finished intervention = the procedure updated. The incident ticket can link to the page.
  6. Never store passwords in the wiki: point to the team's password manager (see password managers).
  7. Plan for access during an outage: the procedure for restarting the server hosting the wiki mustn't live only… on that wiki. Keep an offline PDF export of the emergency procedures.
  8. Archive rather than delete obsolete pages, with a clear "Obsolete, replaced by…" notice.

Procedure page template, to adapt in any tool:

# [Procedure name]

Owner: spo · Last checked: 2026-10-20 · Level: L1 / L2

## Purpose
What the procedure achieves, in one sentence.

## When to use it
Symptoms or starting situation.

## Prerequisites
- Access needed (account, VPN, rights)
- Tools

## Steps
1. ...
2. ...

## Check
How to know it worked.

## Rollback
What to do if it goes wrong.

## Links
Tickets, diagrams, vendor documentation.

9. Checklist

Item Done?
The uses are identified (internal wiki, technical documentation, support, project). ☐
The chosen tool has been tested with real pages and a real search. ☐
Sign-in goes through the company directory (SSO), with rights by group. ☐
The structure and page templates are defined before opening it to users. ☐
Each section has an owner and a review date. ☐
No secret is stored in the pages. ☐
The database and the files are backed up, and a restore has been tested. ☐
The emergency procedures also exist offline. ☐
An exit route exists (full export possible). ☐
If you're on Confluence Data Center or SharePoint Server 2016/2019, the migration is planned. ☐

Read next