Kaphera DSP Data Plane
A DSP-compliant data plane that handles the actual data transfer between EDC connectors. Currently upstream Eclipse EDC components, with a custom multi-tenant Rust replacement on the roadmap.
What it is
A DSP-compliant data plane component that handles the actual data transfer between EDC Connectors. Currently based on upstream Eclipse EDC data plane components, providing production-grade HTTP data plane capabilities from day one. A custom multi-tenant Rust data plane is on the roadmap, following the same pattern as the kaphera-digital-twin-registry, moving from single-tenant-per-participant to shared-process-with-isolation to reduce infrastructure cost at scale.
What it does for the customer
Handles the data transfer that is the entire point of data space participation. Once two connectors negotiate a data sharing agreement through the DSP protocol, the data plane executes the actual transfer: pulling data from the provider’s backend systems and delivering it to the consumer according to the agreed policy. Without a functioning data plane, a connector can negotiate agreements but cannot move data.
Who it serves
lars-hoffmann is the builder deploying connector infrastructure. The data plane is configured and managed by the kaphera-edc-operator as part of the connector lifecycle, so Lars never manages it directly. It just works.
thomas-brandt is the participant whose connectors use the data plane to exchange supply chain data with OEM customers. He never interacts with it; it is infrastructure managed on his behalf.
dirk-wassermann is the enterprise leader running connectors on private infrastructure. The data plane runs on his clusters, managed by the operator, with full source visibility.
Why this licence: GPL
Data transfer is compliance-critical infrastructure where interoperability depends on implementations staying aligned. GPL keeps derivative implementations open, matching the protective stance of the kaphera-digital-twin-registry. The current data plane ships upstream Eclipse EDC components (Apache 2.0 at source); the custom multi-tenant Rust replacement will carry the same GPL terms as the DTR.
How it relates to other artefacts
Managed by the kaphera-edc-operator as part of the connector lifecycle: deployed, configured, and scaled alongside the control plane. Relies on infrastructure from the kaphera-edc-enablement-operator (object storage, credentials). In the managed platform, data plane provisioning is part of the join flow orchestrated by the kaphera-cloud-managed-server. The [[kaphera-cli|kaphera CLI]] and kaphera-cloud-terraform-provider can configure data plane settings through the EDC Operator’s CRDs. The future multi-tenant data plane will follow the same architectural pattern as the kaphera-digital-twin-registry.
Related
- kaphera-edc-operator: the operator that manages this data plane as part of connector lifecycle.
- kaphera-edc-enablement-operator: the operator providing object storage and credentials the data plane depends on.
- kaphera-digital-twin-registry: the architectural pattern (multi-tenant, shared-process, Rust) the future data plane will follow.
- lars-hoffmann: the builder for whom the data plane is operator-managed infrastructure.
- thomas-brandt: the participant whose connectors actually move supply-chain data through this layer.