Most readiness conversations about Catena-X collapse three separate things into one word. Participation has an identity layer, a connectivity layer and a use case layer, and each is independently necessary — you can complete registration, receive your business partner number and be a verified participant while remaining unable to exchange a single record, because a verified identity with no connector is a name with no channel. The connector itself is also widely misunderstood: it negotiates access and usage policies between endpoints, and no data is processed or reviewed inside it. Your data does not go into Catena-X. It stays where it is, and the connector governs who may reach it. Understanding that distinction changes both the internal conversation and the honest answer to how ready you actually are. Talk to a solutions engineer about which layer is your real constraint.
Catena-X Participation Readiness for Suppliers
The three layers you need before anything moves, what a connector actually does and does not do, the release timetable that sets your deadline, and a readiness assessment that names the constraint honestly.
Three Layers, All Required
Sorting them out first prevents the most common failure in these programmes: declaring completion at layer one.
| Layer | What it consists of | What it requires from you | What you still cannot do |
|---|---|---|---|
| Identity | Registration, company information validated, then a business partner number issued as your digital identity. Three credentials complete it — membership, business partner number and framework agreement | Company data, a decision on which roles you want in the data space, and a certificate of conformity from an assessment body where the role requires one | Exchange any data at all. You are verified and inert |
| Connectivity | A dataspace connector — your technical access point for publishing, discovering and managing data offerings | Deployment and operation of at least one connector per legal entity. This is mandatory rather than recommended | Do anything useful with it, because the connector moves data it has no application to source |
| Use case | An application for the specific exchange you need, plus the underlying data at the granularity that application expects | Either an app integrating with your existing systems, or a standalone one. Many marketplace offerings bundle the connector with the application | Nothing — at this point you are actually participating |
What the Connector Actually Does
The single most useful thing to be able to explain internally, because it dissolves the objection that usually stalls these programmes.
The Release Timetable Is Your Deadline
Version lifecycles are published with end dates, which turns a vague intention into a dated plan.
| Release | Went live | Maintained until | What it means for you |
|---|---|---|---|
| Jupiter | October 2024 | Q4 2026 | Applications had roughly a year to certify against the following release. If you are being offered something built to this version, ask about its certification path |
| Saturn | November 2025 | Through 2027 | The current target for new deployments, with a support horizon long enough to justify implementation now rather than waiting |
The Path, Step by Step
Six stages. The first two are administrative, the third is technical, and the rest determine whether any of it produces value.
Two Integration Routes
The choice is genuinely open, and the right answer depends on what you already run rather than on which is more sophisticated.
The Readiness Checklist Nobody Sends You
Drawn from published pre-onboarding practice. Four of these are organisational rather than technical, which is why technically capable companies still stall.
Frequently Asked Questions
Three things, all required. An identity — registration, validation and a business partner number serving as your digital identity, completed by membership, business partner number and framework agreement credentials. Connectivity — at least one dataspace connector per legal entity, which is mandatory rather than optional. And a use case application with the underlying data behind it. Completing the first without the other two makes you a verified participant who cannot exchange anything.
No, and this is the point worth explaining internally. There is no central cloud storing data and no central authority routing it — exchange is peer-to-peer through each participant's own connector. The connector negotiates usage between endpoints by synchronising access and usage policies, and no data is processed or reviewed inside it. Data usage happens at the endpoints of the provider and consumer, not in transit.
At least one per legal entity is the mandatory baseline, since legal entities carry their own identifiers. But published guidance specifically recommends that a parent company provides a connector its subsidiaries can also use, to minimise effort and cost. For a group with several registered companies, clarifying that early materially changes the budget and the deployment plan.
Saturn went live in November 2025 and is maintained through 2027, which makes it the sensible target for new deployments. Jupiter launched in October 2024 and is maintained until the fourth quarter of 2026. When evaluating any application, ask which release it is certified against and when that release stops being maintained — a solution certified only to an expiring version is an unbudgeted migration.
Both routes are supported. Applications that integrate into existing infrastructure suit cases where the data already lives in a system that will stay the source of truth. Standalone or turnkey applications give faster direct access and are frequently the better first move, since they establish that the exchange works before you commit to deep integration. Many marketplace offerings bundle the connector with the use case application, which shortens a first deployment considerably.
Five things: get data processing agreements moving since legal review has its own lead time, allocate named internal people rather than a sponsor, complete technical pre-checks on infrastructure and hosting, decide which roles you want since some require a certificate of conformity from an assessment body, and assess your data granularity honestly. The first four appear on standard pre-onboarding checklists. The fifth does not, and it is the one that decides your timeline.
Not the technology. Identity and connectivity are bounded pieces of work with known shapes, published guidance and certified providers offering packaged onboarding. The constraint is almost always whether your material, carbon or traceability data exists at the granularity the use case requires — held per part number rather than per plant. That work touches every site and every part, cannot be outsourced, and is measured in months rather than weeks. Start free with three assets and get the granularity right first.
