What is the difference between MATTR and Trinsic?

They sit on opposite sides of the same transaction. MATTR provides infrastructure for issuing, holding, and verifying verifiable credentials, with deep support for selective disclosure formats, BBS signatures, and the OpenID4VC protocols that government wallet programs specify. Trinsic provides one API for accepting identity that already exists, routing a user to a mobile driving licence, a national eID, a bank identity scheme, or a reusable identity network. If you are minting credentials, look at MATTR. If you are consuming them, look at Trinsic.

Trinsic scores higher on most dimensions but MATTR has the higher overall score. Why?

Trinsic scores higher on seven of the ten dimensions we grade, including developer experience, lifecycle, and pricing transparency, while MATTR carries the higher overall at 4.2 against 3.9. Our overall score is an editorial judgment rather than an average of the ten, and it reflects MATTR's standards depth and its production government and enterprise deployments, which the individual dimensions do not capture on their own. If your project is an acceptance integration rather than an issuance program, the dimension scores are the more useful read.

Does Trinsic still sell a decentralized identity platform?

Not the one it was known for. On 12 December 2024 Trinsic sold Trinsic Ecosystems, the self-sovereign identity platform it launched in 2019, to Dentity, and refocused on its Identity Acceptance Network. If you want issuance, wallet, and credential infrastructure, that product now sits with Dentity, and Trinsic is the acceptance layer in front of credentials other parties issue. This matters when Trinsic appears on a decentralized identity shortlist, because the company you would buy from today is not selling the platform that put it on that list.

Can you self-host either of them?

Neither offers a full self-hosted stack. MATTR is a SaaS platform, and Trinsic is SaaS only, which our profile of it notes sits awkwardly with self-sovereign ideals. If self-hosting is a hard requirement, look at open tooling in the decentralized identity category instead. Both are also quote-based or usage-based rather than publishing enterprise rates you can plan against.

MATTR vs Trinsic

The honest comparison

MATTR and Trinsic are both filed under decentralized identity and both work with verifiable credentials, which is where the resemblance ends. MATTR, founded in 2019 in Auckland, builds the issuer and verifier side: decentralized identifiers, selective disclosure formats, BBS signatures, and the OpenID4VC protocols that government wallet programs mandate. Trinsic, founded the same year in Salt Lake City, went the other way, and a reader shortlisting it as a decentralized identity vendor needs the reason. On 12 December 2024 Trinsic sold its self-sovereign identity platform, Trinsic Ecosystems, to Dentity and put its resources behind identity acceptance instead. The issuance and credential-infrastructure product it was known for is now Dentity's. What Trinsic sells today is one API for accepting identity that already exists, routing a user to a mobile driving licence, a national eID, a bank identity scheme, or a reusable identity network.

The matrix needs a word of explanation, because it reads against the totals. Trinsic scores higher than MATTR on seven of ten dimensions, including developer experience, lifecycle, and pricing transparency, while MATTR holds the higher overall score, 4.2 against 3.9. Our overall is an editorial judgment rather than an average, and it reflects MATTR's standards depth and its production government and enterprise deployments. If you are integrating rather than issuing, the dimension scores are the more useful signal.

Both carry the category's problem. Credential adoption depends on issuers and verifiers existing in your market, and coverage is uneven by region, so real Trinsic coverage varies by country. Neither offers a full self-hosted stack. MATTR's governance and lifecycle tooling is thinner than a mature IAM suite, and Trinsic no longer holds the SSI platform assets it divested in 2024, so confirm current scope in writing before you build against it.

When MATTR wins

You are the issuer: a government agency, a regulator, a university, or an enterprise minting credentials others will verify
Privacy-preserving selective disclosure is a requirement, so a holder can prove age without revealing a date of birth
A wallet program in your jurisdiction specifies OpenID4VC issuance and presentation, and you need an implementation that already does it
Standards conformance will be audited, and "we called an API" is not an acceptable answer to the auditor

When Trinsic wins

You are the acceptor: you want to verify users faster with identity they already hold, and you are not issuing anything
One integration across many credential types and issuers is worth more to you than control of the underlying DID method
Reusable verification is a conversion problem, and removing a document upload from onboarding is the goal
You want developer-first documentation and usage-based pricing rather than a standards conversation

Pricing

Both are sales-led. MATTR is quote-based platform pricing. Trinsic is usage-based, typically per verification, with developer access and custom enterprise plans, and it scores higher on pricing transparency in our rubric. The larger cost on the MATTR side is the program around the platform: credential design, governance, and the verifier relationships that make an issued credential worth holding. On the Trinsic side the variable is coverage, because in a market where few users hold an accepted digital ID they fall back to a document check you also pay for. Model both in the TCO calculator.

Verdict

Choose MATTR if you are issuing credentials and standards conformance is a requirement rather than a preference. Choose Trinsic if you are accepting identity and want one integration instead of a research project. If neither fits, Microsoft Entra Verified ID is the incumbent option and walt.id the self-hosted one. If the job is really document-based identity checking rather than reusable credentials, compare Jumio vs Onfido instead, since that is the fallback you pay for wherever digital ID coverage is thin. See also our guide to reusable identity and KYC with verifiable credentials and the shortlist at best verifiable credential platforms.