Security Architecture
Isolation. Monitoring. Clear limits.
🛡️ Task Isolation Active
Tasks are isolated to reduce cross-request data exposure. Isolation scope and retention depend on the configured product tier and integration settings.
Model: Per-task isolation
Memory: Ephemeral by default
Cross-task access: Restricted
Memory: Ephemeral by default
Cross-task access: Restricted
⏱️ Rate Limiting Enabled
Rate limiting is applied to reduce abuse, automated scraping, and excessive request volume.
Controls: Burst + sustained limits
Enforcement: Per-IP / per-account (where available)
Enforcement: Per-IP / per-account (where available)
🚨 Abuse Detection Enabled
We monitor for patterns that suggest abuse or policy violations and may throttle, block, or suspend access.
Signals: Volume, repeated failures, policy flags
Actions: Throttle / suspend / terminate
Actions: Throttle / suspend / terminate
What security does not cover
- Compromised devices, weak passwords, or shared credentials on the customer side.
- Misconfiguration of third-party systems you connect.
- Data you choose to submit that is sensitive or regulated (see Privacy Policy warning).
Security Manifest
Public references to key security and company metadata.
GET /security.txt
GET /.well-known/company.json
GET /agents/registry.json
GET /.well-known/company.json
GET /agents/registry.json
Vulnerability Reporting
If you discover a security issue, report it to our security team. Please include steps to reproduce and impact.
Report Vulnerability