Skip to content
Request a demo

What your company knows.
Found, not hunted for.

ThurWiki is ThurData's company wiki: instructions, minutes, projects and everything that should not have to be asked for one person at a time. Written as in a word processor, connected to the systems you already use, run in Switzerland.

No control characters, no training: a ribbon like Word's, tables like Excel's Invoices, tickets, issues and files from your own systems – fetched, not typed out A wiki of its own per company, run in ThurData's Swiss data centre

See it for yourself – with your own content.

You do not judge a wiki by a list of features but by whether your own documentation gets better in it. Two routes there:

Demo access

A wiki of your own to try out, with the sample content of “Muster Elektro AG”: eight spaces, some forty pages with tables, charts, checklists and comments. You see the editor, the macros (ready-made building blocks such as a notice box or an invoice) and the AI assistant at work, and you create pages of your own.

Request demo access

Talk about moving

You have Confluence, another wiki or a drive full of instructions? We look at what is there and show you, on your own pages, how they look in ThurWiki, with a preview before anything is written.

How the migration works

In every wiki

Spaces and a page tree, as deep as you like An editor with a ribbon, tables, checklists 85 macros and 41 connectors (connections to your other programs) An AI assistant with voice input, image search, draw.io Voice notes: record meetings, with a transcript if you want one Versions, comments, approvals (changes visible only after review), simultaneous editing Your own users, groups, nine rights; sign-in with a second factor (a code from the phone). Signing in with your company account (SSO) in the Enterprise package

From CHF 4.90 a month, one price per wiki. Packages and prices.

Packages and prices.

One price per wiki, not per user. How many people write makes no difference. The packages differ in size; the only feature that depends on them is signing in with your company account.

Private

For a personal knowledge archive

CHF4.90

per month
or CHF 49.90 per year

  • 1 Spaces
  • 50 Pages
  • 5 Templates
  • 250 MB Storage
  • without SSO
Order

Verein

For clubs and small organisations

CHF9.90

per month
or CHF 99.90 per year

  • 5 Spaces
  • 300 Pages
  • 15 Templates
  • 2 GB Storage
  • without SSO
Order
Recommended

Business

For companies with several teams

CHF19.90

per month
or CHF 199.90 per year

  • 20 Spaces
  • 1500 Pages
  • 50 Templates
  • 10 GB Storage
  • without SSO
Order

Enterprise

For large organisations

CHF39.90

per month
or CHF 399.90 per year

  • 50 Spaces
  • 5000 Pages
  • 150 Templates
  • 50 GB Storage
  • SSO included
Order
Included in every package: all 85 macros, all 41 connectors, the AI assistant, draw.io, approvals, versions, a review date per page, two-factor authentication and security keys. No marketplace, no credits, no surcharge per user.
Enterprise package only: signing in with your company account (SSO over OpenID Connect or SAML 2.0) – there with no extra subscription and no price per user.

Rather try it first?

14 days free, with the scope of the Business package. No means of payment needed, upgradeable to a package at any time.

Try 14 days free

Prices in Swiss francs. Also in euros and US dollars in the shop. Run in Switzerland, cancellable monthly or annually; paying annually costs about as much as ten months. See all packages in the shop.

A page that is easy to keep current.

The most common ailment of documentation: it starts going out of date the day after it is written. ThurWiki fetches figures and data from the source instead of having somebody type them out, and brings them up to date with one click. And for what only a human can check, there is a review date per page: a name, a date, a reminder. You write down only what you know.

  • Tables you can actually use – sortable, with a search field and a running number, without editing the page.
  • Charts from your own figures – bars, lines and pie from one table, several series, without an extra tool.
  • Notice boxes in five colours: info, note, tip, warning, error. The reader sees from the colour what is at stake.
  • Checklists in the minutes – ticked off in the reading view. The macro tasks of a user gathers them from across the whole wiki.
  • Building blocks from your own systems – customer and invoices from bexio, issues from Jira, a file from the repository. Fetched from the source rather than typed out; up to date with one click, every refresh in the history.
  • Versions on every save, comparable and restorable, without the history getting lost.
A project page in ThurWiki: on the left the spaces and page tree, on the right master data in two columns, a warning, a sortable table of stages and a bar chart of planned and actual hours.
The project page “Gewerbepark Nord” from the demo wiki: columns, a warning, a sortable table, a chart, sub-pages and a drawing – all building blocks you insert rather than build.
85macros, from notice boxes to the invoice out of the accounts
41connectors: AI, Git, Jira, ticket systems, bexio, WHMCS, Abacus, CRM, monitoring, file stores, calendars, messaging
9rights, inherited from the user through the space down to the page
4interface languages: German, English, French, Italian

Writing without learning anything.

The editor works like a word processor: a ribbon with the tabs HOME, INSERT and TABLE, keyboard shortcuts and no markup – that is, no control characters such as == Title == that anyone would have to learn. Several people write on the same page at once, with visible cursors in their own colour. There is no conflict for anyone to resolve.

The editor with the HOME ribbon: undo, paragraph format, font, alignment, lists; below it the page
Editor. A ribbon as in a word processor; tables, boxes and charts are edited where they stand.
The macro chooser: on the left the groups with a count, on the right the macros as cards with descriptions, search at the top.
85 macros. With a search field, ordered by group, each with a question mark leading to its help.
The page
Checklists. Ticked off while reading, not in the editor, and the open items turn up again on the page of the person responsible.
The price list with a search field above the table;
Tables with a search. A search field per table hides what does not match. For everybody else the table stays as it was.

Content from your systems – fetched, not typed out.

41 connectors fetch content from the systems you use anyway and show it as a building block on the page. An invoice typed out by hand would be wrong after the first change, and nobody would notice. A fetched block shows the date of its state, and one click brings the latest.

A wiki page with the customer Muster Elektro AG from bexio: address, telephone, two outstanding invoices with a total, one project, below that the table of outstanding invoices with their status.
Customer from bexio. Master data, outstanding invoices and projects as a card, fetched from bexio rather than typed out.
  • Commercial: bexio, WHMCS, Abacus – contact, invoice, quotation, project, recorded hours, customer, services, tickets, records with their history.
  • Source code: Gogs, GitHub, Bitbucket, GitLab – issues, proposed changes (pull requests), a file from the repository, the latest changes.
  • Issues: Jira and the ticket systems Mantis, Redmine, Request Tracker, Zammad, YouTrack – an issue, a list, a project.
  • Operations and files: Zabbix (monitoring), Proxmox VE (virtual servers), Jenkins and SonarQube (software builds), Nextcloud and Seafile (file stores).
  • CRM: SuiteCRM, vtiger – customer, person, opportunity, case, notes.
  • Calendar, address book and messaging: appointments and contacts, e-mail mailbox, outgoing mail (SMTP), Telegram, WhatsApp.
  • Artificial intelligence: Claude, ChatGPT, Google Gemini and DeepSeek at the provider; LiteLLM, Ollama and Whisper in your own house too.
  • Search and images: web search, image search across nine archives with licence attribution, image generation.

All 41 connectors

Two principles for content from your systems

Access is read-only.

The wiki fetches content from your systems and writes nothing back to them. Access needs only the bare minimum of read rights.

The rights come from the wiki.

Whoever may see a page sees its content, even if they would have no access in the connected system. Whoever uses such a macro therefore decides, by choosing the space, who sees the content.

An assistant with your rights – and no more.

The AI assistant knows the page you have open. It drafts, summarises, translates, builds tables, searches the wiki, creates pages and finds images. If you like, you speak to it instead of typing. Four properties make it useful rather than dangerous:

  • It works with your rights. What you may not see, it does not see. What you may not change, it cannot change.
  • Anything that writes asks first. The “may write” tick box is yours, and you see every step it takes.
  • What it does stands under your name. It is your change; the assistant only typed it. Every one can be brought back.
  • A model in your own house for confidential company matters: for that the address of your server has to be entered, otherwise the access cannot be saved. That way no question ends up at an outside service by accident.

More about the AI assistant

The AI assistant window at the right-hand edge: the question about what to watch out for before a restart, below it the steps the assistant took – it searched and read two pages – the answer with the time and duration of the maintenance window, and at the foot the
The assistant beside the page – with a microphone for voice input.

Working together, with rules.

A wiki for everyone does not mean everyone may do everything. ThurWiki settles who reads, who writes and who approves – and says so when a page has changed while a suggestion was waiting for approval.

Nine rights, three levels

Read, comment, suggest, create pages, write, delete pages, review, administer, wiki administrator – inherited from the user through the space down to the page. The finer level wins.

Approvals

Whoever may suggest but not write creates a suggestion with every save. The approver sees the comparison and decides. If the page has changed in the meantime, the wiki says so rather than quietly overwriting.

Comments and versions

Comments at the foot of the page or on a marked passage in the text, answered and marked done. Every save is a version: compare, restore, without loss.

Notifications

By e-mail, Telegram or WhatsApp, on mentions, on approvals waiting and on changes to watched pages. Gathered together, not twenty times a day.

A personal space

The notepad other users do not see. Once a note has turned into an instruction, you move the page into the right space – history and all. It is not meant for confidential matters: administrators can reach it, and if you leave it remains so that a successor can go through it.

Four languages

German, English, French, Italian – each person chooses their own interface language. The content stays as it was written.

ThurWiki at a glance.

KindA company wiki in the browser; one wiki per company with its own spaces, users, groups and access
StructureSpaces with a page tree, as deep as you like, re-sorted by dragging; a personal space per person; a recycle bin; an archive for finished spaces
EditorA ribbon with HOME, INSERT and TABLE; keyboard shortcuts; tables with cells that merge and split, sortable, filterable, numbered; simultaneous editing
Macros85 in 21 groups: notices, structure, content, content from outside, references, people, groupware, characters, e-mail, Nextcloud, Seafile, Git, software builds, operations, ticket system, Jira, bexio, WHMCS, Abacus, CRM; among them the voice note, recorded or uploaded, with a transcript if you want one
Connectors41: Claude, ChatGPT, Google Gemini, DeepSeek, LiteLLM, Ollama, Whisper, web search, image search, image generation, Gogs, GitHub, Bitbucket Cloud, Bitbucket Data Center, GitLab, Mantis, Redmine, Request Tracker, Zammad, YouTrack, Jira, Jenkins, SonarQube, Zabbix, Proxmox VE, Seafile, Nextcloud, bexio, WHMCS, Abacus, SuiteCRM, vtiger, calendar (CalDAV), address book (CardDAV), e-mail mailbox, outgoing mail (SMTP), Telegram, WhatsApp; data sources read-only
SearchTitles, text and the content of attached PDF, Word and Excel files; by sound and by meaning; only what you are allowed to see
ImagesImage search across nine archives with licence attribution, image generation, two image editors with a version history, draw.io on our own server
Working togetherSimultaneous editing, comments on the text, a version on every save, four-eyes approvals, notifications by e-mail, Telegram, WhatsApp
RightsNine rights, inherited user → space → page; rules on groups; a rights matrix per space
Sign-inUser name and password, two-factor per user, security keys (WebAuthn); in the Enterprise package additionally the company account by SSO over OpenID Connect and SAML 2.0 (Microsoft Entra ID, Google Workspace). On request, per account, only from particular internet addresses
Keeping it currentA review date per page with a responsible person and a repetition; when the date arrives, a notice stands on the page for every reader and the responsible person is reminded
ExportChosen pages and whole branches as one PDF (up to 300 pages, with tables, charts and drawings); every page as Markdown through the API
ImportConfluence (Cloud, Server and Data Center), MediaWiki, DokuWiki, XWiki, BookStack, a Notion export, a Markdown archive – step by step with a preview, repeatable
API36 endpoints, 257 actions; API keys as service accounts with rights of their own and their own log
SecurityIntrusion detection with blocks, brute-force protection, country restrictions, encrypted secrets, a log of every change
Languages · LocationGerman, English, French, Italian · Switzerland, ThurData's own infrastructure

Your knowledge stays in Switzerland.

ThurWiki runs on ThurData's own infrastructure in a former Swiss army bunker, with an uninterruptible power supply (UPS), emergency power and protection against electromagnetic pulses (EMP). Pages and attachments stay exclusively in Switzerland. ThurData is a Swiss company with no US parent; the US CLOUD Act (an American law giving US authorities access to data held by American providers, including abroad) does not apply. No tracking, and one contact with a name.

More about our data centre →

Who ThurWiki is built for.

A wiki pays off as soon as more than one person has to know the same thing. Three starting points we see every day:

You have Confluence.

And with it a subscription that grows more expensive with every user, add-ons for everything that is missing, and a provider subject to the US CLOUD Act. ThurWiki imports your spaces with a preview and converts the common macros.

Migrating from Confluence →

You have MediaWiki, DokuWiki or XWiki.

And nobody outside IT writes in it, because you have to know the markup. ThurWiki takes the existing pages and gives your team an editor it can operate from the first day.

Migrating from MediaWiki & co. →

You have a shared drive and a lot of Word files.

Instructions in folders, minutes in mailboxes, the knowledge in people's heads. ThurWiki brings it into one place, with search that reaches into the attachments, templates for everything that recurs, and an assistant that helps with the writing.

What the wiki can do →

Frequent questions about ThurWiki

Is ThurWiki an alternative to Confluence?

Yes. ThurWiki covers what companies use Confluence for: spaces with a page tree, an editor with a ribbon, macros for notices, columns, tables of contents and tasks, versions, comments, approvals and fine-grained rights. On top of that comes what Confluence can only do with add-ons: content from bexio, WHMCS, Abacus, Git, CRM and calendars directly on the page. Existing Confluence content is imported with a preview.

Does my team have to learn a wiki syntax?

No. The editor works like a word processor: a ribbon with the tabs HOME, INSERT and TABLE, keyboard shortcuts, tables with cells that merge and split. There is no markup anybody would have to know.

What does “content from other systems” mean?

A macro fetches content from a connected system and shows it on the page: an invoice from bexio, a ticket from WHMCS, an issue from Jira, a file from the Git repository. The content is fetched from the source rather than typed out; one click brings it up to date, and every refresh appears in the history. Access is read-only; the wiki writes nothing back into other systems.

Does the AI see everything in the wiki?

No. The assistant works with the rights of the signed-in person: what they may not see, it does not see. Anything that writes asks first, and what it does appears in the history under their name. For confidential company matters a model can be set up in your own house, so that no question goes outside.

Can we bring our existing content across?

Yes. ThurWiki imports from Confluence (Cloud, Server and Data Center), MediaWiki, DokuWiki, XWiki, BookStack and Notion as well as from Markdown files, step by step with a preview. Nothing is written before the last step, and a run can be repeated without pages appearing twice.

Who may see and change what?

Nine rights, inherited from the user through the space down to the page, from read through suggest to administer. Rules can be written onto groups rather than onto people. Whoever may only suggest creates a suggestion with every save, which somebody then approves.

Where does our data sit?

In Switzerland, on ThurData's own infrastructure in a former Swiss army bunker. Every company has its own wiki with its own spaces, users and access. draw.io for drawings and the thumbnails of the image search also run over our own server, not over outside services.

What does ThurWiki cost?

There are four packages, from the personal knowledge archive at CHF 4.90 a month to the Enterprise package at CHF 39.90. They differ in size (spaces, pages, templates, storage), not in features, with the single exception of signing in with your company account, which belongs to the Enterprise package; you pay per wiki, not per user. Fourteen days can be tried free of charge.

ThurWiki is a company wiki and a knowledge base for Swiss SMEs, organisations and IT providers: instructions, minutes, projects, regulations and things to look up, all in one place, written in an editor that works like a word processor – without wiki syntax, without training.

As an alternative to Confluence, MediaWiki, DokuWiki, XWiki, BookStack and Notion, ThurWiki brings 85 macros and 41 connectors with it: invoices from bexio, customers and tickets from WHMCS, records from Abacus, issues from Jira and ticket systems such as Redmine or Zammad, files from Gogs, GitHub, Bitbucket and GitLab, the state of the servers from Zabbix and Proxmox, files from Nextcloud and Seafile, contacts from SuiteCRM and vtiger, appointments and addresses from CalDAV and CardDAV, messages from the mailbox. An AI assistant with voice input works with the rights of the signed-in person; meetings and voice notes are recorded and, on request, transcribed; the image search finds subjects with licence attribution, and draw.io draws in our own house. Existing content comes in through an import with a preview.

ThurWiki is run on ThurData GmbH's own infrastructure in Switzerland: a Swiss provider, a Swiss data centre in a former army bunker, Swiss jurisdiction. With two-factor sign-in, SSO over Microsoft Entra ID and Google Workspace in the Enterprise package, intrusion detection and a complete log of every change.

Documentation people are happy to keep current.

A wiki of your own for your company, with sample content to try out. We set it up for you and show you, on your own content, what the move would look like.