What we're opening
Development updates
Follow on SubstackWe publish open-source progress as posts on Substack. When we publish our first one, it will appear here.
We're opening the operational stack, piece by piece.
The Eclipse Dataspace Components underpin production systems from automotive supply chains to road-safety data. Development runs on goodwill: fragmented and under-resourced. When core services of an open ecosystem run as proprietary black boxes, the sovereignty the ecosystem promises stops at the infrastructure layer.
We're building Kaphera's EDC operational layer as open source from day one — not retrofitted, not partial. kubo, our Kubernetes operator framework, is public today. The EDC runtimes and the operator suite built on top of them open in 2027, under that same unconditional license. Work funded by an ecosystem lands upstream in its open-source foundation, under foundation governance — no Kaphera gatekeeping. The platform earns its business through operational excellence, not lock-in.
Our team holds EDC Core Committer status at the Eclipse Foundation. We shape the protocol at the source and feed that knowledge back into the platform.
The operator suite goes open source in 2027.
We announce the date in the new year.
Who maintains it
The question data space operators ask is not what the license says. It's who is accountable for this in five years.
Kaphera is steward-owned by construction: mission separated from profit, returns capped, no governance rights attached to capital. The components stay maintained because the structure requires it, not because we promise it. How Kaphera is governed →
kubo
An opinionated Kubernetes operator framework for building strongly typed reconcile pipelines in Rust. Batteries included.
Kaphera EDC
The actual EDC runtimes — control plane, identity hub, issuer service. Enterprise-grade and dataspace-agnostic: not a reference implementation, the software a connector runs in production.
EDC Operator Suite
Runs the full lifecycle of an EDC connector as declarative Kubernetes resources — control plane through credential issuance, the infrastructure it depends on, and the steps of actually joining a dataspace. What used to take weeks and a slide deck becomes a spec.
Self-service layer
Orchestrates the operators so a governance authority can define profiles and a participant can request membership without writing infrastructure definitions.