Affinidi Messaging

Privacy-first communication for people, apps and agents.

A decentralised, end-to-end encrypted channel between trusted parties — built on DIDComm v2.1, with no PII exchanged to connect and mediators that route but never read.

DIDComm v2.1E2E EncryptedNo PII ExchangeSelf-Hostable Mediator
Where it fits

A decentralised, encrypted channel between trusted parties.

When people, businesses or AI agents need to communicate without leaking who they are, Affinidi Messaging carries the message — and any Verifiable Credentials — securely.

No PII to connect

Parties discover and connect through Decentralized Identifiers — no phone numbers, emails or accounts to exchange.

Mediators route, never read

Messages are end-to-end encrypted. Mediators relay the envelope but cannot see the content inside.

Open standards

Built on DIDComm v2.1 — decentralised, interoperable and free of proprietary lock-in.

Core capabilities

What Affinidi Messaging gives you.

A privacy-first channel plus the building blocks to embed and self-host it.

Affinidi Messaging

A privacy-first channel for people, businesses and AI agents to exchange messages and Verifiable Credentials securely.

  • DIDComm v2.1
  • End-to-end encrypted
  • VC exchange

DIDComm Client SDK

Embed encrypted messaging directly into your app with a client library that handles keys, envelopes and routing.

  • Client SDK
  • Key handling
  • Envelopes

DIDComm Mediator

Store-and-forward relay that routes encrypted messages between parties — self-hostable for full control.

  • Store & forward
  • Self-hostable
  • Routing

Meeting Place

A discovery layer so agents and apps can find and connect with each other without exchanging PII.

  • Discovery
  • No PII
  • Agent-ready
How it works

How a message moves between two DIDs.

The sender encrypts an envelope; the mediator routes and stores it without reading; the recipient decrypts it — end to end.

How teams use it

A communication layer that works the way you ship.

The same encrypted transport reduces data liability for compliance teams and drops cleanly into any product.

Built for compliance

No PII exchanged to connect, and content the mediator cannot read — a communication layer that reduces data liability by design.

  • No phone/email needed to connect
  • End-to-end encryption by default
  • Self-host the mediator for full control

Built for developers & platforms

Drop encrypted messaging into your product with a client SDK and an open, interoperable transport.

  • Client SDK handles keys and envelopes
  • DIDComm v2.1 — open and interoperable
  • Exchange Verifiable Credentials in-channel
For developers

Ship secure communication in hours, not months.

Install the SDK, connect to a mediator, send your first encrypted message — or run the whole thing yourself.

Ship in three steps

Install the SDK, connect to a mediator, and send your first encrypted message — with Dart and Rust libraries.

Read the quickstart →

Run your own mediator

Self-host the DIDComm mediator for complete control over routing and data residency.

Deploy a mediator →
Explore the suite

Part of Affinidi Elements.

Messaging pairs with the credential engine and the user-owned wallet to close the full trust loop.

Elements Services Available now

Issue, verify, request and manage Verifiable Credentials.

  • The credential layer for your apps
  • Issuance, Login, Verification, Iota
  • Build a production credential ecosystem
See product page
Affinidi Vault Available now

A user-owned digital wallet.

  • Credentials stay on the user device
  • Embed Vault into your own apps
  • Selective sharing with granular consent
See product page
Get started

Ready to build privacy-first communication?

Affinidi Messaging is in beta. Join the programme and start exchanging encrypted, verifiable messages between any parties.

Cookie Preferences

We use cookies to enhance your experience. You can manage your preferences below. For more information, read our Cookie Policy.

Strictly Necessary Always Active

These cookies are essential for core website functions such as security, session integrity, and cookie preference storage. They cannot be disabled.

  • _cf_bm: Distinguishes humans from bots (Cloudflare) · 30m
  • _cfuvid: Ensures secure browsing (Cloudflare) · Session
  • __hs_initial_opt_in: Prevents HubSpot's banner · 7 days
  • _gtm_debug: GTM debug mode (testing only) · Session
Analytics

These cookies help us understand how visitors interact with the site so we can improve content and performance. All data is aggregated and anonymous.

  • _ga, _gid, _gat: Google Analytics · Session – 2 years
  • __hstc, hubspotutk, __hssrc: HubSpot visitor tracking · 13 months
  • __hs_opt_out: HubSpot opt-out preference · 6 months
Marketing & Targeting

These cookies allow us and our partners to serve personalised ads and measure campaign performance.

  • _gcl_au, _gcl_dc: Google Ads conversion tracking · 90 days
  • IDE: Google Display Network personalisation · 1 year
  • _fbp: Meta / Facebook remarketing · 90 days
  • li_gc, _li_fat_id, bcookie: LinkedIn tracking · 1–24 months
  • guest_id, personalization_id: Twitter/X analytics · 2 years