Who: Roles in the Catena-X ecosystem
The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).
Overview of roles

Role Overview and Relationships
Detailed description of each role
Below, each role that a participant can assume in the Catena-X data spaces is described in detail, along with its assigned description, responsibilities, relationships, prerequisites, and complements. Please refer to Chapter What: Service Map for an overview of the Service Map.
Core Service Provider A
Role: Core Service Provider A (CSP-A)
Description/Responsibilities:
A CSP-A is responsible for deploying, operating, and maintaining Core Services A according to Catena-X standards. Core Services A provides common business functionalities for all data space participants (e.g., managing marketplace offers, semantic models, or searching for business partner information).
A CSP-A can operate various bundles of Core Services A, whereby the operation of an IAM and a marketplace is mandatory. Note that the synchronization of marketplace offers is at the discretion of a provider, who may submit and list its offer on multiple marketplaces. The CSP-A role can be taken on by multiple participants.
For smooth operations, the CSP-A must provide comprehensive technical documentation, along with first, second, and third-level support to facilitate integration with its services. Each CSP-A has freedom of choice regarding their business model towards their potential customersCustomer In the context of OSim, the receiver of produced goods from a supplier..
Relationships:
- A CSP-A must implement an IAM synchronization and must integrate with other CSP-As.
- A CSP-A must implement an IAM synchronization with an OSP.
- A CSP-A must integrate with the CSP-B to be able to offer and operate its services. This includes implementing IAM synchronization and integrating with required Core Services B.
- A CSP-A must use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service).
- A CSP-A must accept any certified solution that wants to be listed on its marketplace in accordance with its respective terms and conditions, without discriminating against individual organizations.
Prerequisites:
- A CSP-A and its services must be certified by a CAB.
- A CSP-A must accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs.
- A CSP-A must prove compliance with TISAX Level 3.
- A CSP-A must be registered to the Catena-X data space.
Current Limitations:
- Due to technical limitations, the CSP-A role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter Increase Decentralization of Core Services or can be requested during the conformity assessment.