Europe and beyond · An atlas of trust

Switzerland — swiyu

swiyu separates technical identifiers from verified identity. The sandbox is testable; the official page says production infrastructure is not yet available.

Sandbox · production not yet available according to source · Documentation checked

swiyu — Registering in the Trust Infrastructure

swiyu

137

observed actor entries

All configured sources read

Counts cover entries in harvested sources, not unique organisations or all participants. An actor may occur more than once and have multiple roles. Missing data means unknown, not zero. Exported: .

From actor to source

Explore the actors

Filter by framework, country, role, environment and service type, or search names and identifiers. Choose an entry to see its trust chain and next step.

    137 source entries, showing 50. The same name may appear more than once; this is not a count of unique organisations.

    Each row is one source entry, not a unique organisation. An organisation listed in several sources appears once per source.

    Sources and coverage for this selection (1)

    Coverage refers to our configured sources, not every actor in the ecosystem. Recently fetched does not mean approved or cryptographically anchored.

    How the framework works

    Governance
    The described production model assigns identity checks before Trust Registry entry to the Federal Office of Justice. swiyu — Registering in the Trust Infrastructure
    Onboarding
    Start in the Service Portal, register the organisation and create a DID and keys for sandbox testing. Swiss Confederation — Sandbox: Practical Testing
    Trust documents
    The Base Registry stores DIDs and keys; it does not identify their real-world owner. The Trust Registry adds identity verification. swiyu — Registering in the Trust Infrastructure
    Access certificates
    The onboarding guide uses API subscriptions and access tokens. This does not document an EUDI access-certificate workflow. swiyu — Onboarding Base & Trust Registry
    Registration certificates
    Trust onboarding requires proof of DID-key control. Do not equate the registry entry with an EUDI registration certificate. swiyu — Onboarding Base & Trust Registry
    Coverage limitations
    The production description is prospective. Evaluate sandbox results separately from production identity checks and availability. swiyu — Registering in the Trust Infrastructure · Swiss Confederation — Sandbox: Practical Testing

    Data sources and freshness

    • swiyu integration · identity trust statementsRegister · Sandbox · Recently fetched · Entries: 137Last fetched: · Signature not checkedIdentity trust statements in the integration environment, not production registrations. Entity names are omitted because the register is self-registered and may contain names of natural persons; each occurrence is identified by its DID. Identity alone does not specify issuer or verifier role. JWT signatures, status lists and authorization are not validated.

    A verified signature alone does not establish legal trust or compatibility. The atlas shows publication and source references, not completed transactions.

    Next step

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

    Swiss Confederation — Sandbox: Practical Testing

    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.