Skip to content
Independently verified · Quarterly re-audit
EU VETTED
Curated collection

Docs & wikis without US sub-processors

European documentation and wiki tools verified to run with no US sub-processors — compared on ownership, hosting region, CLOUD Act exposure and sub-processor chain.

In short

The documentation and wiki tools listed here operate with no US sub-processors in the data path — an EU/EEA/Switzerland operator with no US parent and no US-incorporated processor. Knowledge bases concentrate a company's most sensitive internal text, so the search, AI-assist and attachment-storage sub-processors matter as much as the hosting region; each listing records the full chain.

Last verified June 2026 DISCLOSURE Some links on this site are affiliate links. We may earn a commission at no extra cost to you. Editorial signals and rankings are never influenced by affiliate relationships.

Docs and wikis without US sub-processors, as listed on this page, means the operating company is incorporated in the EU, EEA or Switzerland, holds no US parent in its ownership chain, and routes no documentation or knowledge-base data through a US-incorporated processor at any point in the stack. That is a chain of three facts — operator incorporation, ultimate ownership and the full sub-processor list — and all three must hold. A tool that is EU-hosted but owned by a US parent, or EU-owned but relying on a US-incorporated search engine or attachment-storage layer, does not clear the bar.

This page lists the documentation and wiki tools in our directory that meet this test, benchmarked on the criteria a buyer evaluates: hosting region, ownership signal, CLOUD Act exposure and the sub-processor chain. The distinction matters particularly for this category because knowledge bases hold a company's most sensitive long-form internal text, and the exposure often enters through layers that are secondary to the core editor. Every entry is sourced to the vendor's public sub-processor documentation and re-verified quarterly.

Why it matters

The CLOUD Act extends US government reach to data held by any company subject to US jurisdiction, regardless of where the servers physically sit. In documentation tools, the risk is that the core editor is EU-hosted and EU-owned — which can create a false sense of completeness — while exposure re-enters through the peripheral layers that make the tool useful: a full-text search index backed by a US-incorporated service, an AI-assist feature routing document text through a US foundation model API, or attachment storage sitting on an S3-compatible layer operated by a US-owned provider.

Each of those processors is separately reachable under the CLOUD Act, independently of where the primary application runs. A wiki concentrates your most sensitive internal text — strategic planning documents, incident post-mortems, internal credentials referenced in prose, customer notes — making the exposure profile of those peripheral layers more consequential than it would be in a lower-sensitivity category. This is why the directory records ownership and sub-processors as separate, evidenced signals, and why this page surfaces the full chain specifically for the documentation and wiki category.

How to choose

Start by assessing what data your knowledge base will actually hold. For regulated buyers — public sector, legal, finance, healthcare — any US-incorporated processor in the chain is typically a veto regardless of contractual safeguards, because the CLOUD Act operates independently of contract terms. The AI-assist layer deserves particular scrutiny: many EU-hosted wiki tools offer AI features that route document text through a US-incorporated model provider, which would reintroduce exposure. Check each profile explicitly for whether AI routing is EU-operated or can be disabled.

For self-hosting consideration: several EU-operated hosted wikis clear the bar without requiring self-hosting. Self-hosting gives full control over the chain but adds operational overhead — it is one valid route, not the only one. For small teams and solo founders, look for EU-owned hosted options with a short, verifiable sub-processor list. For enterprise procurement, combine this page with the certification filters (BSI C5, SecNumCloud, EUCS) to narrow to products satisfying both jurisdictional and security-audit requirements. Use the sort and filter controls on the listing above to narrow by hosting country, ownership or CLOUD Act exposure.

SWITCHING GUIDES

Switching from a US categories.docs_wikis tool?

Side-by-side European alternatives — same hosting, ownership and CLOUD Act checks — for the most-replaced categories.docs_wikis tools.

FAQ

Frequently asked questions

Why are sub-processors especially sensitive for a knowledge base?
A wiki concentrates internal documentation — strategy, incidents, credentials in prose, customer notes. The search index, any AI-assist feature and attachment storage all process that text, so a US-incorporated processor in one of those layers exposes the most sensitive corpus you hold. We record each one separately.
What counts as 'no US sub-processors' here?
An EU/EEA/Swiss operating company, no US parent, and no US-incorporated sub-processor in the data path — the directory's 'CLOUD Act exposure: none' bar, verified against public sub-processor lists and ownership records.
Do these tools offer AI features without US processors?
It varies. AI-assist often routes through a US-incorporated model provider, which would re-introduce exposure even on an EU-hosted tool. Where a listing offers AI, check the profile for whether the model layer is EU-operated or can be disabled.
Is self-hosting required to avoid US sub-processors?
No. Several EU-operated hosted wikis clear the bar without self-hosting. Self-hosting is one route to control the chain, but the hosted options here are verified on the same criteria — pick based on your operational capacity, not the assumption that hosted means exposed.
How often is this re-verified?
Quarterly, with a last-verified date on each listing; AI and search layers change often, so the chain is re-checked each audit.
Methodology

How we verified every listing here.

For each product we read the public DPA, sub-processors document, hosting region declaration, certifications, and corporate ownership records. Each is timestamped. Signals are editorial, re-verified quarterly. We never accept self-attestation.

Read methodology →