Skip to content
New to wikis?What is a wiki?
Request a demo

Your knowledge stays in Switzerland.

Confluence Cloud stores by region, Notion in the USA or, on the Enterprise plan, in the EU; both providers are based in the United States. ThurWiki runs on ThurData's own infrastructure in Switzerland, with a sign-in you can take seriously and a watchman that spots attacks early, reports them and fends them off.

A data centre in a bunker.

A former Swiss army bunker in Siegershausen, canton Thurgau: UPS, emergency power, EMP shielding, our own hardware. Pages, attachments, database and backups all sit in Switzerland. ThurData is a Swiss company with no US parent; the US CLOUD Act does not apply. No tracking, and one contact with a name.

More about our data centre →

Sign-in: paid per wiki, not per head.

  • OpenID Connect and SAML 2.0 with Microsoft Entra ID, Google Workspace or your own company login, included in the Enterprise package – with no extra subscription and no price per user. Signing in with a password remains available alongside it, as a lifeline should the login service fail; when somebody leaves, the wiki administrator therefore also locks the account in the wiki. SSO grants no rights; those stay in the wiki.
  • Two-factor authentication with any authenticator app, switched on per user.
  • Security keys (WebAuthn): YubiKey, Windows Hello, Touch ID, bound to the address of the wiki. A phishing form gets nothing.
  • Lock-out after failed attempts, temporary rather than permanent: a permanent lock would be an invitation to paralyse other people's accounts.
  • Access only from particular addresses. Per account, the administrator records individual addresses or whole networks; with no entry, "from anywhere" applies. The restriction also applies to the platform administrator – the check deliberately comes before his exception. And it lets nobody lock himself out: anyone who would set his own rules so that his own address falls outside is refused.
The SSO settings: protocol, provider, identifier, redirect address, test the connection.
Setting up SSO in the administration, tested with one button.
The security picture: rejected requests, blocked addresses, anomalies, recent events.
The picture. What the watchman has seen.

A watchman that sees distributed attacks.

  • Spotting. Unknown accounts, rejected requests, patterns in what is typed, attempts from many addresses at once where each one on its own looks harmless.
  • Fending off. Blocking addresses temporarily, declaring hijacked sessions invalid.
  • Country restrictions when a wiki should only be reachable from certain countries.
  • Reporting. The wiki administrator sees the picture in the administration and is notified.

What holds on the inside.

The tenant never comes from the requestAlways from the session or the API key. That way even a mistake in a single function opens no other company's wiki.
API keys tied to a locationA key is a service account and gets the same address list as a person – checked on every call, not only at sign-in. If a key suddenly turns up from a foreign network, the watchman reports it.
Secrets encryptedConnector keys, passwords, API keys: stored encrypted, never shown again.
A log with namesEvery change to pages, rights, users and access, with person, time and origin. Including what API keys and the AI do.
Search gives nothing awayWhat somebody may not see does not appear, not even as a title.
AI with your rightsThe assistant sees what you see and writes only with permission; a model in your own house is possible.
Versions and backupsA complete history per page, a recycle bin, backups of the whole installation.

Questions about security and data protection

Where does the data sit, and who can reach it?

In Switzerland, on infrastructure owned by ThurData GmbH in a former Swiss army bunker in Siegershausen, canton Thurgau. ThurData is a Swiss company with no US parent and no rented cloud; the US CLOUD Act does not apply. Requests from foreign authorities go through Swiss authorities and Swiss courts. Technically, the administrators of the installation can reach it; organisationally only to fix a fault and at your request, logged, under a data processing agreement governed by Swiss data protection law.

What does signing in with our company account cost?

It belongs to the Enterprise package. There, OpenID Connect and SAML 2.0 with Microsoft Entra ID, Google Workspace or your own company login are included – with no extra subscription and no price per user. The difference from Confluence lies in how it is billed: there, SAML SSO requires the additional Atlassian Guard subscription, charged per user; with us the Enterprise package costs CHF 39.90 a month for the whole wiki, however many people work in it. Two-factor authentication and security keys (WebAuthn) are part of every package.

What does the intrusion detection do?

A watchman counts unusual behaviour: unknown accounts, rejected requests, patterns in what is typed, distributed attempts from many addresses. It blocks addresses temporarily, invalidates hijacked sessions and reports what it sees. Accounts are locked temporarily after failed attempts, not permanently. A wiki can be restricted to particular countries of origin.

Can we decide where somebody is allowed to sign in from?

Yes, per account. The administrator records individual addresses or whole networks; with no entry, signing in is allowed from anywhere. The same applies to API keys – a key is a service account and gets the same list. For a person it is checked at sign-in, for a key on every single call. The restriction also applies to the platform administrator; the check deliberately comes before his exception. And it lets nobody lock himself out: anyone who would set his own rules so that his own address falls outside is refused, and every refused sign-in appears in the log.

What about the AI and our data?

The assistant sees what the signed-in person sees, and writes only with permission. Only what you hand to a provider goes to it, and only to the access you chose. For confidential company matters, a model in your own house; for that the address of your server has to be entered, without it the access cannot be saved.

AdministrationRights, groups, users, API keys AI assistantYour rights, your key, your model The data centreThe bunker in Siegershausen

Wiki hosting in Switzerland: ThurWiki runs on ThurData GmbH's own infrastructure in a former army bunker in Siegershausen, as a Swiss company with no US parent, with two-factor sign-in and WebAuthn security keys in every package, SSO over OpenID Connect and SAML 2.0 (Microsoft Entra ID, Google Workspace) in the Enterprise package, intrusion detection with country restrictions, encrypted secrets and a log that records names. Data processing under Swiss data protection law.

Questions about data protection? Give us a call.

We answer them before you order a wiki. On request, with our data processing agreement to read through.

Request a demo +41 71 571 68 40