Security Across Every API
Pulse is a growing hub of APIs — Neural DB, EVE BuildOS, and more on the way. These are the security principles that apply platform-wide, plus notes specific to each product below.
API-Key Tenant Isolation
Every API key is namespaced at the storage layer, not just checked at the request layer — one key can never read or write another tenant's data, across every module.
Prompt-Injection & PII Defense
Every natural-language request passes through an intent-scanning security layer that detects injection patterns and automatically redacts sensitive PII before processing.
Per-Plan Rate Limiting
Request limits are enforced per API key based on your plan, protecting the platform (and your own usage) from runaway or abusive traffic.
Immutable Audit Trail
Every operation is assigned a trace ID and logged — queryable so you always know exactly what happened, when, and from which key.
Encrypted in Transit
All traffic to and from Pulse APIs is served over TLS, end to end.
Product-Specific Notes
Neural DB
- •Each tenant's tables live in a fully separate storage namespace, keyed to your API key.
- •Schema changes proposed via natural language always require explicit confirmation before anything is written.
EVE BuildOS
- •Developer profile and twin data is scoped to your authenticated account.
- •Embeddable bot configurations do not expose underlying API keys to end users.
Bug Bounty Program
Are you a security researcher? Help us maintain the highest security standards. Responsible disclosures of critical vulnerabilities are met with exclusive rewards.
Found a vulnerability?
Submit your detailed PoC (Proof of Concept) directly to our security team.
contact@evorozen.comQuestions About Our Architecture?
Evaluating Pulse for your team and need more detail on how data isolation, encryption, or a specific API works? Reach out directly.
Contact Us