Solidus Relay vs the Indicio Proven Mediator

Indicio is the most production-ready DIDComm v2 mediator offering we know of.

Everything below is written on that footing.

What Indicio does better, and it is most things that matter commercially

• It ships as a deployable image in the Google Cloud Marketplace. Procurement, billing and deployment through a channel enterprises already trust. We have no marketplace listing.
• Real customers in regulated industries. Enterprise contracts across travel, banking and government. We have none, no customer, no pilot, no reference. That is not a gap we can argue around; it is the gap.
• Broader credential-format support, including SD-JWT, AnonCreds and mdoc, plus biometric binding.
• EUDI / eIDAS 2.0 alignment as a stated commercial posture. Solidus holds no status under any EU regulation, not certified, not qualified, not accredited.
• Support you can buy. Relay is beta with no SLA. If your risk register has a row for "who answers at 3am", that row disqualifies us today.

Where the architectures genuinely differ

One sourced distinction, and it is the only one worth building an argument on: the Indicio mediator is deployed into a cloud you run, single-cloud-deployable rather than a multi-tenant hosted service. That is a strength for anyone who wants the mediator inside their own boundary, and a cost for anyone who does not want to operate one.

Solidus Relay is the other shape: a multi-tenant hosted mediator with an operator plane over many agents, plus two things we have not seen offered elsewhere,

• credential-gated admission, fail-closed, distinguishing "verifier unreachable" from "credential invalid" (credential-gated mediation), and
• chain-anchored resolution of correspondents' did:solidus routing, with cached answers keeping their original block and timestamp rather than being re-stamped fresh (chain-anchored routing resolution).

Note the scope of the second: it resolves your correspondents' DIDs. The mediator's own identity is a did:key and is not chain-anchored, did:key vs did:solidus.

Choosing, stated plainly

Choose Indicio if this is production, if you need enterprise support, if you need AnonCreds or mdoc, if EU regulatory posture is part of your procurement, or if the mediator must sit in your own cloud.

Choose Solidus Relay if you are building on the Solidus identity stack, if credential-gated admission is something you would otherwise write yourself, and if beta is a risk you can carry.