Identity is the highest-trust category in security. We design like it.
Keel issues identities and holds the keys that sign them, so trust is the product. Here is how the platform is designed, and where our assurance program stands.
How Keel is built.
Your secrets stay in your cloud
KeelKey governs the vaults you already run and deploys in your cloud account. Keel's control plane never holds plaintext secrets.
Short-lived by default
Agents receive short-lived, scoped tokens and credentials on demand. No agent holds a long-lived secret.
Revocation in real time
Tokens, credentials and context access can be revoked together, and propagated to other systems through shared signals.
Quorum for sensitive operations
Key export, rotation, deletion and break-glass access can require approval from M of N people, executed through KeelKey.
Tamper-evident audit
A normalized, tamper-evident record across vaults, tokens and every context request, exportable to your SIEM.
Your content stays yours
In-VPC deployments of the Context Gateway sync only policy and metadata to Keel's control plane, never content.
Least privilege per agent
Scopes are narrowed per agent, task and purpose, and checked again at credential and context time.
Open, reviewable design
Built on published standards, so security teams can evaluate Keel against specifications they already know.
Where our assurance program stands.
We are early, and we would rather be exact than impressive. SOC 2 Type II and independent penetration testing are planned for the early stages of the program, and we will publish results here when they exist. Nothing on this site should be read as a certification Keel does not yet hold.
Questions for our security team?
Design partners get architecture documentation and direct access to a named Keel engineer.