Manifesto · Sovereign Cloud

Hosted in Europe.
Controlled by Europeans.

Hosting
EU region Paris
Backups + logs in the same region
Parent company
Kopexa GmbH
Based in Germany · no US ownership
Code
KSPEC on GitHub
Open source under the Elastic License v2

5 pillars of real sovereignty

What makes a cloud sovereign. Truly.

Four legal properties, one technical. Each must be provable on its own, otherwise all that remains of the promise is sovereign washing. Here is every property with our status.

1. Parent company in the EU

Who legally controls the company? No US group, no US-investor controlling majority, no US listing.

Kopexa status

Kopexa GmbH, based in Germany. No US parent, no US controlling majority. No US law applicable.

2. Data residency in the EU

Data, backups, logs, metadata and all sub-processors must reside in the EU/EEA, with evidence.

Kopexa status

SaaS in the Paris region (EU). Backups + logs in the same region. Sub-processor list public at /legal/sub-processors.

3. Encryption sovereignty (BYOK)

If the provider holds the key, encryption protects nothing against authority access via the provider.

Kopexa status

Provider-managed keys by default. BYOK available in the on-premise setup, integrated with your KMS or HSM.

4. Authority access and legal recourse

Which law applies to a data request? CLOUD Act orders must be contractually excluded.

Kopexa status

No US law applicable to Kopexa (no US group in the ownership chain). DPA in self-service at avv.kopexa.com.

5. Code and contract transparency

Black-box providers are risky from a sovereignty perspective. Customers need publicly auditable evidence.

Kopexa status

KSPEC is open source under the Elastic License v2 on GitHub. DPA as self-service at avv.kopexa.com. Sub-processors public at /legal/sub-processors.

Who benefits

Three industries where sovereignty is non-negotiable.

Public authorities & public sector

BSIG Section 8a, IT-Grundschutz, the KRITIS regulation. A sovereign cloud is not a wish but an obligation. Following the DSK ruling, Microsoft 365 is restricted in several German federal states.

  • EU data residency per BSI Grundschutz++
  • No US law for sovereign government data
  • Audit trail per Section 8a (3) BSIG

Banks & financial services

DORA Articles 28-30 require a clear third-party risk assessment. For critical cloud services, BaFin supervision expects the sovereignty question to be answered explicitly.

  • DORA third-party risk covered
  • MaRisk AT 9 outsourcing compliant
  • BaFin notification requirement met

Healthcare & pharma

Patient data, study data and genomic data fall under GDPR Article 9 with elevated protection needs. US cloud solutions are hard to justify here, both to supervisory authorities and to patients.

  • Article 9 GDPR special category data
  • EHDS readiness
  • Penetration test reports per BSI

FAQ

Frequently asked questions about cloud sovereignty

Sovereignty with no compromise on functionality.

See the demo, the Sovereign Washing Guide, or the ISMS platform itself.