Eclipse Dataspace Components (EDC)

P2P Platform

A comprehensive open-source framework providing the reference implementation of the Eclipse Dataspace Protocol (DSP), enabling developers and organizations to build and operate sovereign data connectors for participating in dataspaces. The core artifact is the Eclipse Dataspace Connector — a deployable software component that handles catalog publication, contract negotiation, policy enforcement, and data transfer on behalf of an organization. The framework is modular and extensible: a core module handles essential connector logic (TransferProcessManager, ProvisionManager, DataFlowManager, policy engine), an extensions layer adds technology- and cloud-specific implementations (Azure CosmosDB, AWS S3, GCP, Azure KeyVault), and protocol modules implement DSP and other communication standards. Widely adopted in European industrial data spaces including Catena-X (automotive), Gaia-X ecosystem, and cross-industry data sovereignty initiatives. Governed by the Eclipse Foundation with contributors from Fraunhofer, Microsoft, Bosch, BMW, Deutsche Telekom, SAP, and many others.

Community
Links
Visit Community

Details

License Permissive (Apache-2.0); https://github.com/eclipse-edc/Connector — Java; multiple repos in eclipse-edc org including Connector, Samples, MinimumViableDataspace, Virtual-Connector
Dev Status 🟢 Active
Dev Status Detail Released (production deployments in Catena-X and other industrial data spaces; active development; Apache-2.0; 406 stars on main Connector repo; ongoing cloud extension development)
Owner Eclipse Foundation (governance); primary contributors: Fraunhofer ISST, Microsoft, Bosch, SAP, BMW Group, Mercedes-Benz Tech Innovation, Deutsche Telekom, Amadeus, Google, AWS, ZF Friedrichshafen
Country Germany / Europe / Global (Eclipse Foundation global; primary adoption and funding in European industrial data space ecosystem; Fraunhofer ISST Dortmund Germany as major contributor)
Start Year 2021
Stack Java (primary — Connector core, extensions, protocol implementations); Gradle (build system); REST API (management interface); Docker (deployment)
Funding European Commission / Industry consortium (Gaia-X programme; Catena-X funding; IDSA member contributions from Fraunhofer, Microsoft, Bosch, BMW, Deutsche Telekom, SAP, Google, AWS, Amadeus, ZF Friedrichshafen)
Last Investigated Jul 1, 2026

Use Case Domains

Platform Evolution & Sovereignty

P2P Platform Attributes

Origins Industrial data sovereignty / Gaia-X (originally developed to provide an open-source reference implementation of IDS connector concepts for the Catena-X automotive data space; evolved into general-purpose data space framework; shaped by IDSA architecture principles and European data economy policy)
Database Pluggable (no mandatory database; extension modules available for Azure CosmosDB, Postgres, and others for contract state persistence; in-memory store available for testing)
Query Language REST API (management API for connector administration); SPARQL-compatible catalog queries via DSP/DCAT
Data Formats JSON-LD (primary message format via DSP); DCAT (catalog/asset metadata); ODRL (policy and contract terms); REST/JSON (management API); Protocol-specific formats via extension modules
Collaborative Live Editing N/A (data connector infrastructure; not an editing application)
Rich Text Editing N/A
Mobile Support N/A (server-side infrastructure; no mobile interface)
Web Support Yes (management UI available; REST management API accessible via web)
Native Apps N/A (server-side Java service; deployed as Docker container or JVM process)
Terms Free / Open source (Apache-2.0; no licensing fees; commercial support and managed connector services available from ecosystem vendors including Cofinity-X, Think-it, and others)
Funds Undisclosed (funded through European Commission data space programmes, IDSA member contributions, and corporate R&D investment from major contributors; no single public grant figure)
Based On Eclipse Dataspace Protocol / DSP (SD Pro — the specification EDC implements); IDS Reference Architecture Model (conceptual foundation); Gaia-X Trust Framework (trust layer); W3C DCAT + ODRL (semantic standards); EVM/blockchain bridging available via extensions
P2P Architecture Federated connector mesh (each organization runs its own connector instance; connectors communicate peer-to-peer via DSP for catalog queries, contract negotiation, and data transfer; no central broker required; decentralized by design — each connector is autonomous)
Development Tools Java SDK / Extension API (Service Provider Interface — SPI — for adding custom functionality via service loader mechanism); REST management API (for catalog, contract, and transfer management); Connector core libraries (TransferProcessManager, ProvisionManager, DataFlowManager, policy engine); MinimumViableDataspace sample (quick-start reference deployment); cloud extension modules (AWS S3, Azure Blob, GCP, CosmosDB, KeyVault); Docker images; Gradle build tooling; comprehensive GitHub documentation
Deployment Options Self-hosted (deploy as Docker container or JVM process on any cloud or on-premise infrastructure); multi-cloud (extension modules for AWS, Azure, GCP); Kubernetes-compatible; enterprise-grade scalability
Authentication & Identity IDS/DSP certificate-based (each connector participant requires a unique identifier and valid certificate for authentication; Identity Hub component for DID-based identity management; OAuth2/PKCE for management API; W3C DID support via extensions)
Storage Model Pluggable (no prescribed storage; contract state and asset metadata stored in configurable backends — in-memory for testing, Azure CosmosDB / Postgres for production; data assets themselves remain at source — connector manages access, not custody)
Interoperability Eclipse Dataspace Protocol (DSP) interoperability with all conformant connector implementations; Gaia-X Trust Framework; IDSA certification scheme; Catena-X ecosystem; cloud storage APIs (AWS S3, Azure Blob, GCP); future EVM/blockchain bridging via extensions
Social Graph No (data sovereignty infrastructure; social graph not a feature)