Solutions

Twelve components, grouped by the role each plays in the platform. The Operators manage the EDC stack and the multi-tenant boundary; the Applications expose the platform as a REST API and a self-hosted UI; the Managed services extend both with the SaaS-only capabilities that drive cloud.kaphera.com; the Developer experience tools wrap everything for terminal and infrastructure-as-code workflows; the Enablement components ship as standalone, ecosystem-grade infrastructure that any team can adopt independently.

graph TD
  CLI["kaphera CLI"]
  TFP["Terraform provider"]
  TFM["Terraform modules"]
  MS["Managed Server"]
  MC["Managed Console"]
  CS["Cloud Server"]
  CC["Cloud Console"]
  CO["Cloud Operator"]
  EE["EDC Enablement Op."]
  EO["EDC Operator"]
  DTR["Digital Twin Registry"]
  DSP["DSP Data Plane"]
  TFM --> TFP
  TFP --> CS
  TFP --> MS
  CLI --> CS
  CLI --> MS
  CLI --> CO
  CC --> CS
  MC --> MS
  MS --> CS
  CS --> CO
  CO --> EE
  EO --> EE
  EO --> DSP
  EO --> DTR

Operators

Kubernetes operators that turn declarative custom resources into running infrastructure. Together they form the engine of the platform: the EDC stack, the supporting services it depends on, and the organisational model that turns a cluster into a multi-tenant platform.

  • kaphera-edc-operator: manages the full lifecycle of EDC connectors (control plane, data plane, identity wallet, credential issuer). The Apache 2.0 open-source core every other artefact builds on.
  • kaphera-edc-enablement-operator: manages the supporting services every EDC deployment needs: PostgreSQL, Vault, NATS, Keycloak. Apache 2.0.
  • kaphera-cloud-operator: manages the Organisation CRD that creates the multi-tenant boundary (namespace, gateway, TLS, identity groups). Source-available — Elastic; the layer that turns infrastructure into a platform.

Applications

The deployable product surface for self-hosted and BYOC customers: the REST API and the web UI that ship with the platform.

  • kaphera-cloud-server: Axum REST API that exposes authenticated CRUD over the three operators’ CRDs. Source-available — Elastic; the BYOC product Kaphera deploys and manages in customer clusters.
  • kaphera-cloud-console: React/Next.js web app that adapts to whichever server it connects to via GET /capabilities. Source-available — Elastic; the graphical interface for non-CLI users.

Managed services

The globally-unified server and console behind cloud.kaphera.com. Same codebase as the self-hosted applications, but extended with the capabilities that only make sense in a multi-tenant SaaS: the data space directory, the join flow, billing, audit, cross-organisation discovery.

  • kaphera-cloud-managed-server: extends kaphera-cloud-server with directory, join orchestration, billing, audit. Source-available — proprietary; the SaaS differentiation.
  • kaphera-cloud-managed-console: the same console codebase as kaphera-cloud-console, connected to the managed server. Source-available — proprietary; where “login to data exchange in under a minute” lives.

Developer experience

How engineers actually drive the platform: terminal, declarative IaC, and the opinionated patterns that turn raw resources into deployable units.

  • kaphera CLI: Go/cobra CLI with three backends (kubernetes, server, cloud). Apache 2.0; over 95 commands across every resource type.
  • kaphera-cloud-terraform-provider: declarative Terraform resources covering every CRD and server endpoint, with the same three backends as the CLI. Apache 2.0.
  • kaphera-cloud-terraform-modules: opinionated, production-tested deployment patterns composed on top of the provider. Apache 2.0.

Enablement

Standalone components that any team can adopt without buying into the rest of the platform. Released to the ecosystem on more protective open-source terms because interoperability and shared correctness matter more than commercial control.

  • kaphera-digital-twin-registry: multi-tenant, AAS Part 2-compliant registry for digital twin metadata. GPL; the registry Catena-X requires for product-level data exchange.
  • kaphera-dsp-data-plane: DSP-compliant data plane that handles the actual data transfer between connectors. Currently upstream Eclipse EDC components; a multi-tenant Rust replacement is on the roadmap.

Where to go next