Host Wiki.js without installing anything
A wiki that also writes its pages into a Git repository: documentation stays readable in the browser and versioned like code.
Starting at €8.99/month
Introduction
Wiki.js installed, updated and backed up by us, on a machine in France. A modern, fast wiki with a Markdown or visual editor, fine-grained permissions and built-in search. Ideal for documenting a team or an association. You install nothing and configure no server: the application is online a few minutes after you order, under your own name.
The plan that suits it is App Confort at €8.99/month incl. VAT — 4 GB of memory. Wiki.js is a Node.js application backed by PostgreSQL, and memory goes to three things: the rendering pipeline, which turns Markdown into HTML with syntax highlighting and diagram rendering; the full-text search index, kept current every time a page is saved; and Git synchronisation, which spawns real git processes to read and write the repository. A wiki of a few thousand pages with its images fits comfortably in this plan.
What gets replaced here is Confluence, a shared Notion page, or a folder of Word files nobody can find. What sets Wiki.js apart is its ability to write every page into a Git repository at the same time as into its database: the documentation becomes a tree of versioned Markdown files, readable outside the wiki and reusable elsewhere. It is also the safest import path: Markdown files dropped into the repository show up as pages. On the access side, sign-in can go through the company directory — LDAP and Active Directory, SAML, OpenID Connect — rather than yet another password.
What managed hosting changes
Two-way Git synchronisation
Every saved page is written into a Git repository, and a change pushed to the repository comes back into the wiki. Documentation then lives where the code it describes lives, with its commit history, and a backup that is readable without the software.
Four editors for one wiki
Markdown with live preview for those who write fast, a visual editor for those who would rather not, raw HTML for the odd case, AsciiDoc for technical documentation. The choice is per page, and a page can switch editors.
Permissions that follow the tree
Rules are written per path: public read on /public, write reserved to a group on /procedures, invisible elsewhere. So you can keep an open wiki and an internal section in one installation, without duplicating the tool.
Sign-in through the existing directory
LDAP and Active Directory, SAML, OpenID Connect, or the usual providers. Directory groups feed the wiki permissions: a departure is handled in one place, and nobody has an extra password to remember.
Why hand it over rather than install it
An engineering team that wants its docs in Git
Runbooks live next to the code, reviewed in a merge request, and stay readable in a browser for people who never open an editor. This is the most common reason for choosing Wiki.js over another wiki.
An association that elects a new committee every two years
How to register an event, where the keys to the hall are, which insurer to call: this knowledge is lost at every handover. Written down once, it passes on with the mandate.
A company with an Active Directory
Accounts come from the directory, groups decide what each person sees, and someone who leaves loses access without anyone touching the wiki. The administrator no longer keeps two lists.
A wiki in several languages
Pages are filed by language and the reader switches between them. Useful as soon as a team spans two countries, or public documentation has to exist in English too.
A knowledge base open to the public
Help articles are readable without an account, drafts and internal procedures stay locked, and search only surfaces to an anonymous visitor what is meant for them.
Hosted in France
In our own infrastructure in Nouvelle-Aquitaine, which we operate ourselves. Internal documentation describes your access, your suppliers and your procedures: it does not leave the country.
Frequently asked questions
Through the Git repository or file storage, which is the safest way in: any Markdown file dropped into the tree becomes a page, with its path and its title. Confluence exports to HTML or XML, Notion to Markdown; so conversion is needed, and that conversion deserves a proper tool — pandoc for HTML, Notion's own Markdown export for the rest. Budget a review of images and tables, the two places where exports degrade.
Everything, because everything can be written as files: with Git sync or local storage enabled, your pages exist permanently as Markdown files in a tree, with their commit history. It is a continuous export rather than an operation to launch. A page also prints to PDF from the browser, and the PostgreSQL database can be exported as it stands.
The stable release is version 2, and it offers a single theme: customisation goes through CSS injection, not an appearance editor. Version 3 has been announced for a long time; plan on 2 when deciding. Comments are rudimentary — this is not a review tool. The visual editor stays less predictable than Markdown on complex tables. And there is no offline mobile app.
App Confort, at €8.99/month incl. VAT. It provides 4 GB of memory where the application asks for 1 GB at minimum: the headroom serves the system, not the decor. You can change plan later without reinstalling.
Nothing. You choose the application, fill in the fields it asks for — often an email address and a name — and it goes online. Access arrives by email with the address and the credentials.