The Dataspace Management is the modernised portal of Eclipse Tractus-X. It lets an onboarding service provider (OSP) admit companies to a dataspace such as Catena-X and manage them afterwards:
Today’s portal is a monolith whose user interface owns orchestration and business rules, and a third party cannot use a capability without the portal UI. The Dataspace Management splits the portal into modules with clear interfaces and makes these interfaces the only way in. No single party runs the portal for all participants of a dataspace: every OSP runs its own installation, the CSP provides trust (OSP 2.0, decided on 28 Oct 2026).
| Priority | Quality goal | Motivation |
|---|---|---|
| 1 | Interoperability | Every capability is reachable through its documented interface (OpenAPI), by the UI of the OSP and by third parties. |
| 2 | Security and data protection | Sign-in without passwords through wallets; permissions per operation; no secrets in events; data minimisation per module. |
| 3 | Modifiability | One module per folder with its own interface and data, replaceable without touching the others; flows are data, not code. |
| 4 | Operability | One Helm chart per installation; every OSP decides which services it runs itself and which it uses from the CSP. |
| Role | Expectation |
|---|---|
| Onboarding service provider (OSP) | Runs and configures its own portal installation; reviews and onboards companies. |
| Core service provider (CSP) | Provides the trust list, company identifiers (BPN), the directory BPN → DID and discovery. |
| Company administrators and members | Register their company and manage people, technical users, connectors and subscriptions. |
| App and service providers | Publish offers and manage subscriptions. |
| Operators | Install, configure, monitor and upgrade the installation (see the admin guide). |
| Developers | Implement modules against the module specifications. |
This work is licensed under the CC-BY-4.0.