The problem
Why it matters.
Data in the cloud is often locked with keys the cloud provider holds. Regulated organizations need to control those keys themselves.
With Roost
How Roost handles it.
01
Cloud asksThe cloud service needs a key to open data.
02
Roost decidesPolicy, quorum and approvals apply to every request.
03
RecordEvery use is on record.
APPROVED
Your switchCut cloud access to your data at once.
What you get
In the console.
- External key store for cloud services
- Bring your own key without exposing it in plaintext
- One view of keys across clouds
- Access is yours to revoke
AxowlacmeRoostM
Keys
27keys
3rotating
0exportable
| Name | Purpose | Version | Quorum | Last used |
|---|---|---|---|---|
| release-signing | code-signing | v3 active | 2 of 3 | 2 min ago |
StatusArmed PolicyApproval required Born inROOST-26-0001 ExportNever | ||||
| data-key-eu | data-key | v2 active · v1 decrypt-only | 2 of 3 | 10 s ago |
| tls-www | tls | v1 active | 2 of 3 | 1 s ago |
| ca-intermediate | ca | v1 active | 2 of 3 | 3 days ago |
See Roost refuse an unapproved signature.
A 30-minute live demo with our engineers.