Trust
Security
Last updated October 10, 2026
Keystone is built so AI tools only see what your scopes and keys allow. This page summarizes controls we operate today — not a certification claim.
Authentication
- Console sessions use an HttpOnly, Secure, SameSite=Lax cookie (not localStorage JWTs).
- Email one-time codes are rate-limited by IP and mailbox.
- Optional OIDC / SSO for organizations that configure it.
- Agent access uses workspace API keys or OAuth with PKCE for MCP clients.
Isolation
- Postgres Row Level Security separates tenant data.
- Team scopes and bound keys limit what each agent can recall.
- SharePoint Connect uses Sites.Selected-style grants — customers consent only the sites they choose.
- Private connector content fails closed (no silent org-wide ACL defaults).
Audit & governance
- Admin audit log in the console for sensitive actions.
- Conflicts and merges keep disputed facts visible instead of silent overwrites.
- Support tickets stay in your signed-in portal with mailbox-scoped email sync.
Infrastructure
- Hosted on Railway with private database networking for application services.
- Production refuses weak default session secrets at boot.
- API OpenAPI docs are disabled in production.
- Database backups are maintained for disaster recovery.
Subprocessors
See Subprocessors and the draft DPA. Report security issues to support@devcabi.net.
Roadmap honesty
We do not claim SOC 2 or ISO certification at this time. As the company formalizes, we will update this page rather than overstate controls.