The Wiki.js alternative that is developed continuously.
Wiki.js looks good and keeps pages in Git. Version 2 still receives security updates; version 3, announced in 2021, has no date, and when asked about it in 2025 the maintainer answered “Sorry, no ETA.”. ThurWiki takes your Markdown pages and is developed continuously.
What Wiki.js users run into. And what ThurWiki changes about it.
Voices from public forums and reviews, some of them shortened. More reasons for switching stand on the migration page.
-
Version 3 keeps everyone waiting.
«In 2025 still waiting for V3.» – Wiki.js GitHub Discussions #4652, January 2025
ThurWiki: A product that is developed continuously, with somebody to talk to at ThurData. Operation, backup and updates are done by ThurData; you tell us what is missing.
-
A technical setup, hungry for resources.
Setting it up calls for technical knowledge, and Node.js with Postgres needs resources. – in substance, from user reviews
ThurWiki: Nothing to set up. A wiki of your own for your company, run in Switzerland, two-factor authentication included.
How the move out of Wiki.js works.
- Route
- The pages sit in Wiki.js as Markdown, and as files anyway with Git storage. Import them as an archive.
- Comes across
- Paths become the page tree, plus text, tables, images, links and labels.
- Check afterwards
- Save pages written in the Wiki.js HTML editor as Markdown first; create diagrams anew as a draw.io drawing.
Pages that quietly go stale no longer exist.
The most common ailment of a wiki is not the missing page but the wrong one: an instruction that has not been right for two years, and nobody notices. A review date turns that into an appointment.
- A name, a date, a rhythm. Per page a responsible person, a date and, if you want, a repetition: every 30 days, quarterly, half-yearly or yearly.
- The notice stands on the page, not only in a mailbox. Once the date is reached, everyone who opens the page sees it – including the engineer who needs the instruction right now. A reminder only one person gets does not help the reader.
- Confirming is one click. The responsible person is reminded and confirms right in the notice. With a repetition the next date counts from today – anyone confirming three months late is not immediately due again.
- Two overviews. “My reviews due” for the individual, and in the wiki administration all the reviews due across the wiki. The responsible person is an organisational note and not a right: they get no access they do not have anyway.
And back out again: as one PDF.
A wiki you cannot get out of is a trap – you know that, moving out of Wiki.js right now. That is why the exit lies open.
- One document out of many pages. Tick across spaces, up to 300 pages per export; each begins in the PDF on a new sheet, in the order of the page tree. You choose how large it prints: 45 to 100 per cent, for type and content at once.
- Just as the page looks. What is printed is the real view, not a second rendering: macros, charts, draw.io drawings and tables stand in the PDF as they do in the browser.
- With your rights, not with everybody’s. A page you are not allowed to read stops the export rather than quietly going missing. An export that drops pages would be worse than one that never arrives.
- And by machine. Through the API every page as Markdown, with attachments – for an archive or for the move to the next system.
ThurWiki and Wiki.js side by side.
| ThurWiki | Wiki.js | |
|---|---|---|
| A page tree as deep as you like | yes, as deep as you like | yes, through paths |
| Search inside PDF, Word and Excel attachments, tolerant of typing mistakes | attachments yes, including scans and archives; typing mistakes yes, and by meaning | attachments no; typing mistakes depending on the search module |
| An editor without markup | yes, a ribbon like Word’s | Markdown and WYSIWYG |
| Simultaneous editing | yes | no |
| Four-eyes approvals | yes, without an add-on | no |
| Invoices, tickets, issues and files from other systems on the page | yes, 41 connectors, from bexio, Odoo and Jira to Zabbix and Proxmox | no |
| SSO (OIDC, SAML) without a price per user | yes, included | yes |
| An AI assistant | yes, with your rights, without credits | no |
| Operation, backup and updates by the provider, data in Switzerland | yes, ThurData in Switzerland | yourself |
| Run it yourself (open source) | no, run by ThurData | yes, open source |
| Export chosen pages and whole branches as PDF | yes, chosen pages and whole branches as one PDF; every page as Markdown through the API | yes, Markdown through Git or file storage |
| A review date per page with a reminder | yes, a responsible person, a date, a repetition, a notice on the page | no |
| Price | per wiki, from CHF 4.90 a month | free, you run it |
As of September 2026, based on the makers’ public statements and on user reports, without warranty. We also write down where we are not ahead.
Questions from Wiki.js users
We write Markdown in Wiki.js. Can we carry on in ThurWiki?
The editor works with a ribbon. The import wizard reads Markdown files, and through the API every page goes in and out as Markdown. Anyone who would rather type than click will get along.
Does the Git connection stay?
Not as storage, but as a source: the macro “file from the repository” fetches files from Gogs, GitHub, GitLab or Bitbucket onto the page, instead of somebody typing them out. One click brings the page up to date, and every refresh appears in the history.
How much work is it?
Export the Markdown archive, import it, check the preview: for a few hundred pages about an afternoon, plus the follow-up work.
How do we stop pages going stale?
With a review date per page: a responsible person, a date and, if you want, a repetition (30 days up to yearly). Once the date is reached, a notice stands at the top of the page – visible to everyone who opens it, not only to the responsible person – and that person is notified. Confirming is one click in the notice; with a repetition the next date counts from today. Whoever administers the wiki sees all the reviews due in one place, and each person sees their own in the user menu.
How do we get back out of ThurWiki?
In the interface as PDF: you tick in the page tree what should come along – per row either the page alone or the page with all its sub-pages – across spaces, up to 300 pages in one document. What is printed is the view you see, so with macros, charts and drawings. Through the API, additionally every page as Markdown, with attachments. There is no bulk export of the whole wiki as an archive today; we would rather say so beforehand.
More alternatives pages: Confluence · MediaWiki · DokuWiki · XWiki · BookStack · Docmost · Outline · Notion · SharePoint
ThurWiki is a Wiki.js alternative for companies that want a continuously developed wiki without running it themselves: an editor like Word, Markdown import and every page as Markdown through the API, search into attachments, approvals, connectors, operation in Switzerland. Wiki.js migration through the Markdown export, with a preview.
Anyone wanting to replace Wiki.js or move away from it because version 3 keeps them waiting finds the route, the comparison and the trial import here.
Twenty of your Wiki.js pages in ThurWiki, before you decide.
We set up a demo wiki and import a slice of your collection, with a preview. You see search, macros and the editor working on your own content.