ArchitectureDeployment
The exit is the entry in reverse. Your pins and the keys you hold stay with you.
You operate the platforms, catalogues, resources and agents you already have. One kind of thing crosses between the two.
While you use Connect
Raidiam Connect
One governed record per entity and the authority that publishes it.
Hosts the Records Assistant: publishes its configuration and signs it with a key Raidiam holds. Deployment evidence
Signed statements. Connect publishes, your systems verify.
Your estate
Your platforms and gateways
Pin the anchor they trust and verify each statement.
Your agents and resources
One governed record each.
Your catalogue and identity system
Configured once. Nothing here moves.
Your private keys
In the design, the holder makes each key. Connect receives a signing request or a public key.
If you stop
Raidiam Connect
New statements stop being signed.
Hosts the Records Assistant: publishes its configuration and signs it with a key Raidiam holds. Deployment evidence
Every consumer sees that at its next resolve.
Your estate
Your platforms and gateways
What stays Their pins, and their derived clients until the statements expire.
Your agents and resources
What stays Their keys and configurations.
Your catalogue and identity system
What stays You operate them, as you did before.
Your private keys
What stays The holder keeps the private half.
On this showcase Raidiam's setup and deploy tools made every private key and keep a copy. The deploy puts each one into its holder's service. Deployment evidence
Your systems stay yours.
The four questions a risk committee asks.
-
Where does Connect run?
One tenant, at the hosts this estate names.
- Directory
- web.directory.showcase.raidiam.io
- Federation endpoints
- federation.directory.showcase.raidiam.io
- Authority
- authority.directory.showcase.raidiam.io
- Trust marks
- trustmark.directory.showcase.raidiam.io
- Keystore
- keystore.directory.showcase.raidiam.io
An estate like this one is one tenant of the service, or a dedicated tenant if you want one.
-
Who operates it?
Raidiam operates the tenant. You operate everything else.
- Governed records, authority and anchors
- Raidiam
- Your platforms, catalogue, resources and agents
- You
- Anchor, authority and hosted entity signing keys
- Raidiam, in a key management service
- Every other private key
- Its holder. On this showcase Raidiam's tools made each one and keep a copy.
-
Which region holds my records?
This tenant declares a GB trust framework.
- Trust framework organisation
- Raidiam
- Trust framework region
- GB
- Certificate subject country
- GB
Storage region is a deployment choice. This showcase declares none, so this page states none.
-
What happens while Connect is unreachable?
A platform decides on answers it already holds, until the window it set expires. An unresolved agent waits.
- A resolved statement is held for
- 300 seconds
- A mark status is held for
- 60 seconds
- Consumers acting on a mark they cannot re-check
- 4 of 10, for 300 seconds
Which of your platforms would resolve first, and what would you want to keep running if you stopped?
Ninety minutes, on the shape of your estate: which systems resolve first, which anchor each pins, and which key each party holds.