Wiki.js hosting: documentation that lives next to your code.

For technical teams that want to write documentation in Markdown and keep it with the code. Think of administrators who maintain runbooks and developers with internal guides. A team without a technical background can work with it too, but will get more from an editor that resembles a word processor, like the one in BookStack.

The pages can sit as files in a Git repository, and changes in the wiki and in the repository are carried over to each other. That gives your documentation the history and the review process of Git as well. Which repository you use, we discuss beforehand. It can be the Forgejo environment we also manage, or another.

Yes. You set per group who may read, write or manage pages, and you can shield whole parts of the wiki. One section can be visible to clients while the internal documentation stays behind it. Signing in can use an existing account, so you do not have to create separate users.

Because the pages are Markdown, they are easy to take along. If you use Git synchronisation, they already sit as files in your own repository, apart from our server. Otherwise we hand over an export of all pages and images. Markdown opens in almost any other system, so the content stays usable.