So, what is Kaphera Cloud?
§6 of 6 · ~2 min read
The short answer
Kaphera Cloud closes the gap named in §1 by running the operations layer for everyone who does not want to become an infrastructure operator, and by handing the source-available stack (code you can read, audit, and run, with commercial-use restrictions) to everyone who does. It is a managed platform for deploying and operating EDC Connectors across European dataspaces. A small supplier with no IT team can join Catena-X in under a minute through the web console (the browser-based management UI). A systems integrator running six client projects can ship the same connector stack as code, in a day, and hand it off without a knowledge transfer.
Three offers in one platform
Managed
For the supplier with no IT team. Sign up at the web console, pick a plan, join the dataspace in under a minute. Kaphera runs the connector. Pricing scales with throughput. The managed plan costs less than the cloud bill you would pay to host the infrastructure yourself, before counting the engineering time to build and run it.
Self-hosted
For the systems integrator running six client deployments. The same source-available stack, deployed on their cloud, managed via Terraform (infrastructure-as-code). Same binary, different backend. Zero knowledge transfer required when they hand a project off.
Governance surface
For the consortium that defines the dataspace. A single integrated control surface for issuing credentials, defining policy templates, and auditing the dataspace their members participate in. EU-sovereign by construction.
What ships at GA (general availability)
The 1 October 2026 release covers three managed plans (shared, dedicated, enterprise), two connector profiles (MDS and Tractus-X / Catena-X), the full developer toolchain (CLI, Terraform provider and modules, web console), and the multi-tenant Digital Twin Registry that Catena-X requires for product-level data exchange. The MDS profile has been running in production since the soft launch earlier in the year, with more than 150 active connectors on the predecessor platform (Krypton). This is a GA built on a production track record, not a roadmap.
What it is not
- Not a data-storage product. Kaphera Cloud governs how data moves between organisations under what policies. The data itself stays with the participants.
- Not a Catena-X-only product. Tractus-X and MDS ship at GA, with additional dataspace profiles on the roadmap.
- Not v1-scoped to bring-your-own-cloud or compute-to-data. Bring-your-own-cloud is the next major capability after GA. Compute-to-data and the application layer come later.
That is the product. The rest of the vault is the proof.
Where to go from here
Pick the route that matches what you’re here to do.
- By persona →. Walk into the rest of the vault by archetype: participant, builder, governance authority, white-label partner.
- By topic →. Pick a goal: evaluating, onboarding, troubleshooting, selling.
- 02 · Product reference →. Engineer-grade reference for the twelve components and how they compose.
- 04 · Customer journeys →. Eight customer scenarios told from the customer’s point of view.
- Want to go deeper? Continue the chain →. Four further pages on the protocol stack, identity model, Kaphera architecture, and deployment.
Previous: ← §5 Why Europe is doing this