Why Raidiam
Your estate has to trust agents someone else runs.
Raidiam builds the trust infrastructure that carries identity and authority across boundaries you do not control.
The problem
Every new relationship is another trust set up. Unless every party joins one trust model.
The answer
Every system asks the same seven questions. One governed record answers all seven.
Every system asks
-
Who is this agent?
AgentIts own federation identifier, and the keys that speak for it.
-
What software is it, and who built it?
ReleaseThe release behind it, signed by its publisher.
-
Is this running copy vouched for?
InstanceIts attester binds a key where it runs. On a workload it vouches for the binary too.
-
Who is accountable for it?
OperatorThe operator that runs it, named on the record.
-
What may it ask for?
EnvelopeThe authorization detail and grant types its authority permits.
-
What bounds it?
CeilingsRegistered on the record. The attested and granted ceilings narrow it.
-
Who vouches for it, and can they withdraw it?
AuthorityThe authority that signed it, which can withdraw it.
Why believe it
Raidiam already runs regulated trust frameworks in production.
The names and figures below are open banking and open finance. The same trust infrastructure now carries agents.
Trusted ecosystems Raidiam runs
- Open BankingBrasil
- Open Finance
- Central Bankof the U.A.E.
- ConnectID
- GetVerifiedNew Zealand
Published by Raidiam for Raidiam Connect in production. Five of eight ecosystems are named above, each with hundreds of entities. Open Banking Brasil holds thousands of registered client applications carrying non human identities. This showcase is a separate estate, counted on the estate page. Open the showcase estate page
Built on open standards
- OpenID Federation 1.0 (open standard)
- OAuth 2.0 (open standard)
- X.509 and mTLS (open standard)
- SPIFFE (open standard)
The trust model is a published specification, not a Raidiam protocol.
What stays yours
Your platforms, your approvals and your people stay yours.
Raidiam Connect holds
- The governed record
- The authority and the anchor
- The recognition of an external root
- The change history
You keep
- Your keysIn the self managed model you generate the key and keep the private half. Connect certifies the public half.See the four custody models
- Your decisions while Connect is unreachableA platform decides on answers it already holds, until the window it set expires. An unresolved agent waits.
- Your authorisation platforms, your APIs and your cloudsThey stay. Each one adds three checks and accepts attest_jwt_client_auth from an attested agent.
- Your catalogue and your approval process
- Your people
- Your attesters and your workload identity system
Which system in your estate decides whether to trust an agent, and where does it get that answer?
Ninety minutes, on the shape of your estate: which systems resolve first, which anchor each pins, and which key each party holds.