Sovereignty and compliance
A sovereign data and AI platform for Europe: what GDPR, DORA, NIS2 and the EU AI Act ask of your lakehouse
European regulated organizations need more than an EU region. GDPR governs transfers and processing, DORA requires financial entities to manage ICT third-party risk and exit plans, NIS2 adds supply-chain security for critical sectors, and the EU AI Act asks for data governance and traceability for high-risk AI. A lakehouse that runs under EU jurisdiction, on open formats, with lineage and audit inside the EU, addresses all four.
Published . Last updated
On this page
Almost every data platform now offers an EU region. European regulators are increasingly clear that a region is not the same as sovereignty, especially when the provider's parent is outside the EU. This guide summarises what four EU frameworks ask of a data and AI platform and how to meet them with an open lakehouse operated under EU jurisdiction.
Is an EU region enough for European data sovereignty?
Residency is necessary but not sufficient. An EU region keeps data in the EU; it does not by itself remove exposure to non-EU legal process, such as the US CLOUD Act, when the provider has a non-EU parent. Regulated buyers therefore look at who operates the platform, where the control plane and logs live, and whether they can exit without losing their data.
What does each framework ask of a data and AI platform?
| Framework | Who it applies to | What it means for the platform |
|---|---|---|
| GDPR | Anyone processing personal data of people in the EU | Lawful transfers, purpose limitation, security, data subject rights, records of processing |
| DORA | EU financial entities and their critical ICT providers | ICT third-party risk management, register of information, exit strategies, resilience testing, incident reporting |
| NIS2 | Essential and important entities in critical sectors | Supply-chain security, incident handling, risk management measures |
| EU AI Act | Providers and deployers of AI systems, with stricter duties for high-risk uses | Data governance for training and inputs, logging, traceability, human oversight |
Two themes cut across them: control of the supply chain (who operates what, and can you leave) and evidence (lineage, logs and access records you can show a supervisor).
How does an open lakehouse address DORA's exit strategy requirement?
DORA expects financial entities to have credible exit plans for critical ICT services. Exit is hardest when data and logic are locked in proprietary formats. An open lakehouse keeps:
- Data in Apache Iceberg, readable by any Iceberg engine.
- Transformations as dbt code in your own Git repository.
- Semantic definitions as YAML in the same repository.
- Engines that are open source: Spark, Trino, Kafka, PostgreSQL.
Exiting means redeploying engines elsewhere, not migrating data out of a proprietary store.
What evidence do EU supervisors expect, and where does it come from?
| Evidence | Where it comes from in DataNature |
|---|---|
| Who accessed personal data | Atlas audit log of access, per user and group |
| How a figure was produced | Lineage from Bronze source to Gold metric; dbt run history |
| Which data trained or fed a model | Iceberg snapshots and experiment runs |
| Which controls protect personal data | Column masks and row filters per group, documented per engine |
| What an AI agent did | Voir action logs, with human approval for system changes |
| Where everything runs | Deployment in an EU sovereign cloud or your own EU data centre, control plane included |
Where can DataNature run in Europe?
DataNature runs on European sovereign infrastructure such as OVHcloud in France, in your own cloud account in an EU region, in your own data centre, or fully air-gapped. In each case the control plane, catalog, audit log, vector store and AI gateway run in the same place as the data. Models can be self-hosted on EU infrastructure or routed to an EU-hosted provider through the AI gateway.
How does this support the EU AI Act?
For high-risk AI systems, the Act emphasises data governance, record-keeping, transparency and human oversight. A governed lakehouse supplies the raw material: certified training data in Gold, reproducible snapshots, lineage, logged model versions, and agents that cannot act without approval. It does not replace your conformity assessment, but it makes the evidence available.
Frequently asked questions
Does DataNature support GDPR data subject requests?
The platform supports finding personal data through the catalog and lineage, and masking or deleting it in Iceberg tables; your processes define how requests are handled.
Can European banks use DataNature under DORA?
DataNature is designed to support DORA programmes with open formats for exit, in-EU operation and audit evidence. Each financial entity assesses its ICT providers under its own DORA framework.
Is DataNature an EU company?
DataNature is built by Dlytica, headquartered in Canada. For EU sovereignty, what matters is where the platform runs and who operates it; DataNature can be deployed and operated on EU infrastructure under EU jurisdiction.
Sources
- SoftwareSeni: DORA, NIS2 and the EU AI Act are making sovereign cloud mandatory for some workloads
- Elastisys: data residency vs data sovereignty
- DataNature: Europe region
- DataNature documentation: security overview
How does DataNature Atlas keep this secure and compliant?
Every rule in this article is enforced in one place, inside your jurisdiction. DataNature Atlas is the platform's governance module:
- Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
- Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
- Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
- Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
- Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.
These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.
Platform components in this article
Learn more about each DataNature product and module mentioned here.
See it on your own data.
Book a demoDemos and quotes are handled by Dlytica, the company behind DataNature.