Security
The AI runs real operations. Trust comes before function.
The identity bridge is the most sensitive point of the system and gets the most rigorous design. See the controls.
Call signing
HMAC with timestamp and nonce on the webhook, preventing replay. The static Verification Key alone does not authenticate.
Key rotation
Verification Keys and webhook secrets rotatable from the dashboard, with history.
Proof of possession
The first user↔channel binding requires verification (OTP), with optional periodic re-verification.
Step-up on destructive operations
Sensitive tools require explicit user confirmation in the chat before executing.
Credentials in a vault
API keys and tokens in vault/KMS, write-only in the dashboard (masked display), never present in logs.
Full audit
Every operation logs the user, channel, tool, parameters, masked request/response, and the conversation snippet that triggered it.
Multi-tenant isolation
Data, credentials, and executions isolated per partner; administrative impersonation always audited.
Outbound IP allowlist
Published list of outbound IPs so you can restrict your firewall.
Dry-run
The playground lets you test conversations without running any real write operations.
Security you can audit.
Request our security material in a conversation with sales.
Talk to BIOS · WhatsApp