Authentic by proof, not by promise

Encryption made digital interactions private. The next step: making them provably authentic.

See it in production

Verimesh is in production in Swiss healthcare. Zero Trust says never trust, always verify. Inside one organisation it is clear what to verify against; across an organisational boundary it is not, and NIST's own example reaches for federation there. Vereign is built to establish trust across organisational boundaries, without a central broker.

HIN (Health Info Net)

800,000+

verified deliveries per month, across all of Swiss healthcare

See the HIN use case

Consent Architecture

EHDS Article 71 made secondary-use opt-out a legal right. Article 71(8) forecloses centralised registries. DKMS is the first structurally sound foundation for satisfying all five regulatory requirements end-to-end: person-scoped IDs, verifiable timestamped opt-out, reversibility without re-identification, cross-controller propagation, unlinkability.

Read the consent architecture thesis →

What breaks, and what becomes possible

Manual

Every cross-institutional verification in healthcare requires manual coordination: phone calls, faxes, portal logins. Verification between institutions, against each other's key event logs, is designed to replace that manual coordination.

CAQH Index 2023 · USD 30 billion annual administrative cost in US healthcare alone

Fragile

Banks depend on centralised trust chains for KYC and cross-institutional verification. When a single link fails, the entire chain breaks. Bilateral trust makes each verification independent and auditable.

EBA 2023 · EUR 6.5B annual ICT operational losses in European banking

O(n²)

39 European TSOs need 741 bilateral agreements under the current trust model. O(n) architecture means each new operator adds one relationship, not 38.

ENTSO-E analysis

What others say

I've spent 20 years building trust infrastructure. The biggest open question was always: who guarantees trust between organisations without becoming the bottleneck — and a target? Vereign has the answer.

Urs Fischer Urs Fischer Business Development & Innovation Manager, HIN, previously CEO, SwissSign

After nearly three decades of testing security assumptions, the fundamental flaw is clear: trust models based on perimeter defense break hard at the organizational walls. Vereign makes trust verifiable at the point of interaction where it's needed most.

Built for the trust gap

Product

The infrastructure layer for verified institutional exchange

Verimesh (formerly the Stargate project) is designed so that each organisation manages its own cryptographic identity and is verified against its own key event log, without a central certificate authority that every party must trust. Where a counterparty validates only X.509, as at HIN today, a bridge certificate authority connects the two. Mail and Data are the day-one editions, with Agent and Edge on the roadmap, deployed as Hub, Node, or Cloud. Verimesh is in production in Swiss healthcare.

Explore Verimesh →
Product

Verified delivery to any device, zero installation

SEAL: SEAL (Secure Edge Application Layer) delivers encrypted messages to any recipient on any device, with evidence each one arrived unaltered. By default there is no software to install and no account to create. Content is fragmented and distributed across an encrypted swarm so no single system holds the complete message.

Explore SEAL →
Perspective

Why the certificate authority model is broken

PKI and OAuth are correctly engineered for what they were designed for. They were not designed for multi-stakeholder, cross-institutional trust at scale. The Trust Architecture page explains the structural gap, and the mathematical case for why a different foundation is required.

Read the analysis →

One architecture. Eight regulated sectors.

Healthcare

In production

800,000+ verified deliveries per month across Swiss healthcare since April 2025

See the healthcare deployment →

Cybersecurity

In production

Verified delivery of sensitive security findings: penetration test reports carrying cryptographic evidence they arrived unaltered, via SEAL

See cybersecurity delivery →

Finance

Architecture validated

GLEIF-validated bilateral trust: designed for KYC, AML, and cross-institutional verification

Explore finance architecture →

Defence

Architecture validated

Designed for zero-trust bilateral verification in classified inter-agency data exchange

See defence verification →

Pharma

Architecture validated

Designed for verifiable chain of custody across clinical trial data and regulatory submissions

See pharma chain of custody →

Energy

Architecture validated

Designed for authenticated mesh networking between grid operators: O(n) trusted inter-TSO communication

See energy grid architecture →

Legal

Architecture validated

Designed for verifiable document provenance across borders. Secure client communication without apps or onboarding.

See legal document provenance →

Compliance

Architecture validated

Designed for auditable, attribution-complete records meeting DORA, GDPR, and NIS2 obligations: NIS2 enforcement begins June 2026

See compliance architecture →

Trust infrastructure as competitive advantage

Organisations that control their own trust infrastructure onboard partners faster, negotiate from strength, and operate across jurisdictions without third-party dependency. Dataspaces and cross-organisational workflows become viable when trust between organisations needs no shared broker. DKMS is the Certificate Authority at the Edge: each organisation becomes its own root of trust, mapping real organisational complexity into cryptographic infrastructure. It covers the organisations themselves, the roles and people acting within them, and the data they exchange, with its meaning intact, and the same model would extend to the agents that act for them.

See how the architecture works
30 years building cryptographic infrastructure Federal Cross of Merit on Ribbon 800,000+ verified deliveries in Swiss healthcare Open source, AGPLv3+ Meet the team →
Featured in the press
IPFS case study: 800,000 messages a month, secured for Swiss healthcare Play
Interview · IPFS · 65 min

IPFS case study: 800,000 messages a month, secured for Swiss healthcare

“There is no central point of compromise anymore. There is no database that can be hacked, because the data just doesn't exist, even in encrypted form, in one place anywhere. It only comes together at the edge device of the patient.”

Watch the 65-min interview →
Also featured in See all coverage →

Latest Insights

View all insights Subscribe to feed
Trusted by
Hin Ibm Dhi Redhat Ehda Cyberware Dkms alliance Daasi Vshn Dif

Ready to build trust infrastructure that scales?

Whether you are evaluating trust architecture for your organisation or exploring partnership opportunities, we will show you how the technology applies to your specific context.

Explore partnership opportunities See how this applies to your sector Book a 30-minute architecture review
Swiss Data Protection GDPR Compliant Open Source AGPLv3+ Swiss Hosting