Glossary · EU Data Strategy Data Spaces (European Common Data Spaces)
EU initiative to create sectoral data sharing frameworks where European organizations can exchange data under common governance, technical standards, and sovereignty rules.
## What Data Spaces actually are
European Common Data Spaces are EU-coordinated, sector-specific frameworks for organizations to share data with each other under shared governance, technical interoperability standards, and European sovereignty constraints. They are *not* a single platform — they are a *model* for federated, sovereign data exchange that each sector adapts.
The concept was formalized in the **European Strategy for Data (2020)**, which proposed common data spaces in priority sectors: manufacturing, mobility, health, finance, energy, agriculture, public administration, skills, and Green Deal data. By 2026, several are operational or in late-stage rollout.
## Active Data Spaces (selected)
### Manufacturing — Catena-X / Manufacturing-X
- **Catena-X**: automotive industry data space (BMW, Mercedes, Volkswagen, Bosch, SAP and others). Operational since 2023 for supply chain transparency, CO2 tracking, battery passports.
- **Manufacturing-X**: broader industrial extension across discrete manufacturing.
### Health — European Health Data Space (EHDS)
EHDS regulation entered into force 2025. Two layers:
- **Primary use**: patient access to and portability of health records across borders.
- **Secondary use**: regulated reuse of health data for research, policy, regulatory purposes.
### Mobility
European mobility data space coordinates traffic, transport, and mobility-as-a-service data sharing under common rules.
### Finance — European Financial Data Space
In rollout, coordinated with Open Finance regulation. Aims to standardize financial data sharing under EU rules including DORA.
### Other sectors
Energy, agriculture, skills, public administration, Green Deal — at varying stages of design and rollout.
## What makes a Data Space *European*
Data Spaces share common architectural principles:
### 1. Federated, not centralized
Data stays with the organizations that produced it. Data Spaces define *how* it's shared, not *where* it's stored. This contrasts with US-style centralized data platforms.
### 2. Sovereignty by design
Data sharing operates under EU jurisdiction with EU-defined rules. Foreign access rights (CLOUD Act, etc.) are constrained by design.
### 3. Common technical standards
Shared interoperability protocols — often building on [GAIA-X](/en/glossary/gaia-x/) self-description standards and IDS (International Data Spaces) Reference Architecture.
### 4. Sectoral governance
Each Data Space has its own governance body (industry consortium, regulatory authority, or hybrid) defining sector-specific rules within the EU framework.
## Why Data Spaces matter
### 1. Unlocking data without surrendering sovereignty
European businesses sit on enormous datasets they could share for mutual benefit but won't, because trust frameworks don't exist. Data Spaces create those frameworks.
### 2. Strategic competitiveness
US and Chinese players have built data advantages through centralized platforms. Europe's bet is that federated, trusted data sharing produces equivalent or better aggregate value while preserving control.
### 3. Implementing the [Data Act](/en/glossary/data-act/)
Data Spaces are the practical implementation layer for many Data Act requirements around B2B data sharing and IoT data access.
### 4. AI training data
European AI labs need access to European data at scale. Data Spaces create governance for AI training data without violating GDPR or competitive concerns.
## What Data Spaces mean in practice
### For European businesses
If you're in automotive, manufacturing, health, or mobility, a Data Space likely already affects you or will. Participation may be voluntary, mandated, or competitively necessary depending on sector.
### For tech buyers
Vendors increasingly advertise "Data Space ready" capability. This is meaningful when the vendor implements relevant standards (IDS connectors, GAIA-X self-description, sector-specific protocols).
### For developers
Data Space standards are open and implementable. The Eclipse Dataspace Components project provides reference open-source connectors.
## Data Spaces vs other models
- **Centralized platforms** (US model): one party owns the data, others access on terms set by the owner
- **Open data**: data is freely available, no governance constraints
- **Data Spaces**: data sharing under negotiated, federated rules with sovereignty preservation
The Data Spaces model is novel — neither closed nor fully open, but governed.
## What 2026-2027 brings
- **EHDS rollout** continues toward 2027 full operation
- **Manufacturing-X expansion** beyond Catena-X
- **Sectoral data spaces in rollout** for finance, energy, agriculture
- **Cross-sector interoperability** initiatives
- **AI training Data Space** discussions following EU AI Act implementation
## Practical implications
Data Spaces remain relatively abstract for most European tech buyers today. But they form the structural foundation for how European data will be shared and monetized over the coming decade. Understanding them helps you:
- Recognize which vendors have credible sovereignty positioning
- Anticipate compliance requirements in regulated sectors
- Evaluate vendor claims about EU data strategy alignment
For everyday vendor selection, this is background context. For strategic technology decisions in regulated sectors, it's increasingly load-bearing.
Was this helpful?
Thanks for your feedback!