Security
Built so AI can act without holding the keys
Elaichi exists because handing agents raw API keys is a governance nightmare. Here is how the platform keeps credentials, identity, and every tool call under control.
Credentials the AI never sees
Third-party credentials live in a dedicated vault service, encrypted at rest with AES-256-GCM. The control plane stores only credential configurations — the shape of what a connector needs — never secrets. Tools execute server-side with credentials resolved at call time; neither end users nor AI models ever see them.
Show-once, hashed tokens
Session, API, MCP, and invite tokens are stored as keyed hashes and shown exactly once at creation. Lost MCP URLs are rotated — old token revoked first — not left dangling. Rate limits apply on both the data plane and the control plane.
Bring your own key
Organizations on the Black plan wrap credential encryption with their own AWS KMS customer-managed keys via envelope encryption, so key custody stays with you.
Enterprise identity
SAML SP and OIDC RP implemented in-house — no third-party auth vendor in the login path. DNS-TXT-verified domains, enforced SSO (social login and magic links refused for enforced domains), JIT provisioning, SCIM v2 user and group sync, and group-to-role mappings.
Multi-factor authentication
TOTP MFA with single-use recovery codes. Once enabled, every login is held in a pending state until verified; five failed attempts destroy the pending session. TOTP secrets are encrypted at rest, recovery codes stored hashed.
Three-layer governance
Role-based access control with per-request permission evaluation, per-resource ACLs, and connector/tool restrictions enforced at connect, advertise, and execute time — the escape hatch is itself a permission.
Append-only audit
Every privileged action is logged — memberships, roles, connections, shares, MCP server lifecycle, and each tool call with tool, connection, status, and duration. Forward events to your Datadog with batched, retried delivery and a dead-letter queue.
Safe offboarding
Removing a member runs a preflight: personal connections referenced by shared toolboxes must be transferred or deleted before removal completes, and unreferenced connections are cleaned up — vault account included.
Questions about our security posture?
We're happy to walk your security team through the architecture in detail.