Skip to content
Request a demo

The Docmost alternative with operation, connectors and SSO at no price per head.

Docmost is young, lean and handsome. Anyone running it in-house maintains Postgres, Redis and updates themselves, and SSO exists only in the paid Enterprise edition. ThurWiki takes the Markdown export and brings operation and 41 connectors with it; SSO belongs to the Enterprise package.

What Docmost 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.

  1. SSO only at a surcharge.

    In Docmost, SSO exists only in the paid Enterprise edition. – from the maker’s own statement

    ThurWiki: Two-factor authentication and security keys in every package; OpenID Connect and SAML 2.0 in the Enterprise package, with no price per user.

  2. Operation in your own house.

    Run yourself, Postgres and Redis run alongside, and you do the updates yourself. – from the Docmost installation guide

    ThurWiki: Operation, backup and updates by ThurData in Switzerland, with somebody to talk to.

  3. Few connections to other systems.

    ThurWiki: 41 connectors: bexio, WHMCS, Abacus, Jira, Git, ticket systems, Jenkins, SonarQube, Zabbix, Proxmox, Nextcloud, Seafile, CRM, calendars, mailboxes, AI. The macros only read, with the rights of the wiki, and they are included in the price.

How the move out of Docmost works.

Route
Export spaces as a Markdown archive, then import. Attachments come along.
Comes across
Page tree, text, tables, images, task lists, links.
Check afterwards
Rights and groups; diagrams anew as a draw.io drawing.

The import in five steps

The import wizard: on the left the page tree of the source, on the right the page as it would look after the import – with a table and sections – below it the buttons to import the page and to import the page with its sub-pages.
The preview. Look first, then decide: before the last step nothing is written.

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.
A wiki page with a notice on a yellow background above the text: “This page should have been reviewed since 01.09.2026. Responsible: Rita Suter.”
Due, and everybody sees it. The notice stands above the content, for everyone who opens the page.
The “export pages as PDF” view: on the left the page tree with two boxes per row, one for the page alone, one for the page with all its sub-pages; on the right the chosen pages in document order and the “create PDF” button.
Tick what should come along. First box: that page only. Second: the page with everything beneath it.

And back out again: as one PDF.

A wiki you cannot get out of is a trap – you know that, moving out of Docmost 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 Docmost side by side.

ThurWikiDocmost
A page tree as deep as you likeyes, as deep as you likeyes
Search inside PDF, Word and Excel attachments, tolerant of typing mistakesattachments yes, including scans and archives; typing mistakes yes, and by meaningattachments depending on the edition; simple full-text search
An editor without markupyes, a ribbon like Word’syes
Simultaneous editingyesyes
Four-eyes approvalsyes, without an add-onno
Invoices, tickets, issues and files from other systems on the pageyes, 41 connectors, from bexio, Odoo and Jira to Zabbix and Proxmoxno
SSO (OIDC, SAML) without a price per useryes, includedEnterprise only, paid for
An AI assistantyes, with your rights, without creditsnot in the free edition
Operation, backup and updates by the provider, data in Switzerlandyes, ThurData in Switzerlandcloud at the maker or yourself
Run it yourself (open source)no, run by ThurDatayes, open source
Export chosen pages and whole branches as PDFyes, chosen pages and whole branches as one PDF; every page as Markdown through the APIyes, as a Markdown archive
A review date per page with a reminderyes, a responsible person, a date, a repetition, a notice on the pageno
Priceper wiki, from CHF 4.90 a monthfree; cloud and SSO are paid for

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 Docmost users

What do we gain over Docmost?

Operation and updates by us, SSO with no price per head, approvals, search into attachments, 85 macros, 41 connectors, AI that works with your rights, four languages. And somebody to talk to, with a name.

How do the pages come across?

Through the Docmost Markdown export as an archive, with a preview in ThurWiki, repeatable.

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 · Wiki.js · Outline · Notion · SharePoint

ThurWiki is a Docmost alternative for companies that want SSO with no price per head, operation in Switzerland and connections to bexio, Jira, Git and CRM. Docmost migration through the Markdown export, with a preview.

Anyone wanting to replace Docmost or move from Docmost to a managed company wiki finds the route and the comparison here.

Twenty of your Docmost 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.