EUDI · An atlas of trust

Compare trust frameworks

Compare governance, registration, trusted lists and certificates across four test and pilot environments.

From difference to decision

Compare what matters to you

Choose environments, focus on a topic and open the evidence. Matching role names do not establish interoperability.

1. Choose 2–4 environments

4 environments · 6 topics

Documented differences. Open “Evidence and sources” for the full explanation. On narrow screens, scroll the table horizontally.
What to clarifyEU reference Reference implementation · testChecked Digdir Norwegian sandbox · testChecked Germany EUDI Hub · beta sandboxChecked WE BUILD European large-scale pilotChecked
Governance

Who publishes trust, and for which environment?

Reference services for testing

Evidence and sources: EU reference, Governance

The EUDI reference project provides development and interoperability services. Its TLP documentation explicitly excludes production use.

Digdir manages the sandbox

Evidence and sources: Digdir, Governance

Digdir manages the sandbox lists and registrar. Registration and trusted-list publication are separate steps; publication is described as manual.

EUDI Hub beta

Evidence and sources: Germany, Governance

EUDI Hub separates sandbox and live environments. This entry covers only the beta sandbox.

WP4 manages pilot trust

Evidence and sources: WE BUILD, Governance

The WP4 group performs the pilot ecosystem-authority and trusted-list-provider roles. The documentation separates this from later EU and Member State responsibilities.

Onboarding

Which registration path applies to your role?

Test RP service

Evidence and sources: EU reference, Onboarding

The reference RP service registers relying parties and issues test certificates. This demonstrates a workflow, not national production registration.

Different paths for RPs and issuers

Evidence and sources: Digdir, Onboarding

Relying parties can register through self-service. Issuers are currently directed to Digdir and must also register their signing certificate.

Account → organisation → use case

Evidence and sources: Germany, Onboarding

Create an account and organisation, configure issuance or requests, then create certificates.

The role determines the route

Evidence and sources: WE BUILD, Onboarding

Participants apply to lists matching their roles. Relying parties use a separate registry flow and are not individually listed on these trusted lists.

Trust documents

Which formats and signatures must your integration handle?

XML lists and JWT LoTEs

Evidence and sources: EU reference, Trust documents

The documentation links to test XML LoTL/TLs and six JWT LoTEs. Keep these separate from national production lists.

ETSI 119 612 + 119 602

Evidence and sources: Digdir, Trust documents

The sandbox uses an ETSI 119 612 XML list and role-based EUDIW lists under ETSI 119 602. The register does not replace these trust sources.

Signed LoTEs with history

Evidence and sources: Germany, Trust documents

The test portal publishes signed LoTEs for PID, wallet, registrar and both certificate-provider roles, with stable URLs and previous versions.

List of lists in JSON and XML

Evidence and sources: WE BUILD, Trust documents

A common list of trusted lists is published in JSON and XML. It points to participant lists for discovery within the pilot ecosystem.

Access certificates

Where is the key created, and how do you obtain the certificate?

Certificate and keypair in PKCS#12

Evidence and sources: EU reference, Access certificates

The RP service describes issuing an access certificate and keypair as PKCS#12 for relying-party authentication.

Submit CSR, retrieve certificate

Evidence and sources: Digdir, Access certificates

After registration, the participant can upload a CSR and retrieve an access certificate. The private key stays with the participant.

New certificates in the Hub

Evidence and sources: Germany, Access certificates

Create new access certificates in the Hub. Old certificates do not work in updated wallet apps.

Dedicated WRPAC onboarding

Evidence and sources: WE BUILD, Access certificates

The pilot describes dedicated onboarding for access-certificate providers (WRPAC). The provider role is entered on the relevant list.

Registration certificates

Is actual issuance described, or only a provider list?

Provider list, not proof of a full flow

Evidence and sources: EU reference, Registration certificates

The documentation publishes a test list of registration-certificate providers. The RP service documents access-certificate issuance; the list alone does not establish a complete registration-certificate flow.

Documented as planned

Evidence and sources: Digdir, Registration certificates

The capability overview describes registration-certificate issuance as planned. This is documented planning status, not a live availability check.

After use-case configuration

Evidence and sources: Germany, Registration certificates

Registration certificates follow use-case configuration. Previous configuration is not transferred automatically.

Separate WRPRC list and onboarding

Evidence and sources: WE BUILD, Registration certificates

Registration-certificate providers (WRPRC) have a separate list and onboarding. A list entry alone does not show which participants have received certificates.

Coverage limitations

What needs checking beyond registration and a list entry?

ARF is not implementation evidence

Evidence and sources: EU reference, Coverage limitations

This describes reference services. A feature described in the ARF is not necessarily implemented or available in each test environment.

Roles checked, not legal basis

Evidence and sources: Digdir, Coverage limitations

Digdir checks declared roles against the sandbox agreement, but says it does not verify the legal basis for declared issuance or data processing.

Test data require independent trust checks

Evidence and sources: Germany, Coverage limitations

The sandbox lists are test-only. The portal asks consumers to establish trust in its signing certificate independently; downloading it is not enough.

Pilot conditions, not production schemes

Evidence and sources: WE BUILD, Coverage limitations

This is a pilot. The blueprint explains that full production certification and qualification schemes cannot always be applied in the pilot environment.

These are documented differences between reference, sandbox and pilot environments. This table does not assess legal compliance, maturity or which solution is best. Confirm the requirements for your role with the environment’s operator.

Next step

Choose an environment, read the requirements for your role and follow its official onboarding guide before connecting.

Compare requirements across the four environments

Find an actor and explain the trust evidence for Norway and Digdir

Abid

How can we help you?

Our door is always open, so get in touch if you’d like a chat or a coffee. We’re located in Oslo, Trondheim, and Bergen.