Product

Start here

If you have five minutes and want a single document that frames the product:

• kaphera-cloud-overview: mission, purpose, and the past/present/future arc. The shortest path to “what is this?”

If you have longer:

• product-brief: the master description, covering scope, goals, deployment tiers, what ships at GA on 1 October 2026, and what’s explicitly out of scope.
• pr-faq: the launch press release framed as Q&A. Reads as the public-facing narrative, with market context, competitive positioning, customer profiles, and common objections answered.

Reference

For looking things up rather than reading top-to-bottom:

• glossary: domain terms used across the vault. Dataspace, EDC, DSP, Catena-X, MDS, connector profiles, control plane vs data plane. Start here when a term in another note is unfamiliar.

Components

Kaphera Cloud is twelve open-source or source-available components. They are documented individually in the solutions index, grouped by role:

• 3 Operators: Kubernetes operators that manage the EDC stack and the platform infrastructure layer.
• 2 Applications: the Kaphera Cloud Server (REST API) and the self-hosted Console (UI).
• 2 Managed services: the globally-unified managed Server and Console for tenants on the shared and dedicated tiers.
• 3 Developer experience tools: the kaphera CLI, Terraform provider, and Terraform modules.
• 2 Enablement components: the multi-tenant Digital Twin Registry and the DSP-compliant data plane.

flowchart TB
  subgraph DX["Developer experience"]
    CLI["kaphera CLI"]
    TFP["Terraform provider"]
    TFM["Terraform modules"]
  end
  subgraph APP["Applications (self-hosted / BYOC)"]
    SRV["Cloud Server"]
    CON["Cloud Console"]
  end
  subgraph MAN["Managed services (cloud.kaphera.com)"]
    MSRV["Managed Server"]
    MCON["Managed Console"]
  end
  subgraph OPS["Operators"]
    EDC["EDC Operator"]
    ENA["EDC Enablement Operator"]
    KCO["Cloud Operator"]
  end
  subgraph ENB["Enablement"]
    DTR["Digital Twin Registry"]
    DSP["DSP Data Plane"]
  end
  DX --> APP
  DX --> MAN
  MAN --> APP
  APP --> OPS
  OPS --> ENB

For the full architecture breakdown — layer-by-layer narrative with the licensing rationale for each tier — see §9 · Kaphera Architecture.

Engineers evaluating the platform should start at index. Non-technical readers can skip this section; the brief and PR/FAQ above describe what these components do at a business level.

Where to go next

• By persona: who Kaphera Cloud is for, with a 1:1 mapping to the customer journeys.
• Customer journeys: eight scenarios, written from the customer’s point of view, covering awareness through scaling.
• FAQs: consolidated questions and answers across product, sales, and operational concerns.