Security

Built for serious data.

Per-agent isolation, encrypted credentials, and an honest take on where we are with compliance.

Our posture

Five things we take seriously.

Tenant data separation

Every workspace's data is scoped with row-level security, and each client can get its own environment or agent. Dedicated per-agent databases are available on Enterprise.

Credential vault

API keys, tokens, and OAuth secrets are encrypted at rest with envelope encryption, scoped to a single agent, and never written to logs.

Bring your own LLM and DB

Your OpenAI/Anthropic/Google keys go to your provider, not us. On Enterprise, bring your own Supabase project. Your data, your bill, your keys.

First-class identity

Native Clerk integration passes authenticated users through to the agent. SAML SSO and SCIM provisioning available on Enterprise.

Defense in depth

Per-agent budget caps, rate limits, output filtering, and prompt-injection guards. Audit logs on Enterprise.

Honest about what we don't have yet

We're not pretending to be SOC 2 certified before we are. The roadmap below is our actual current state.

Compliance roadmap

What's shipped, what's in progress.

We'd rather under-promise here than ship a fake badge. This is our real-time status.

  • Encryption at rest (AES-256) and in transit (TLS 1.3)
    Live
  • GDPR-compliant data processing addendum (DPA) available
    Live
  • Region selection (US, EU) on Business and Enterprise
    Live
  • Audit logs export (Enterprise)
    Live
  • SAML SSO via Clerk (Enterprise)
    Live
  • SOC 2 Type II — observation window underway, report Q3 2026
    In progress
  • HIPAA BAA — pilot customers Q3 2026
    In progress
  • ISO 27001 — planned 2027
    Planned
  • FedRAMP — planned 2027
    Planned

Need a security questionnaire, pen-test report, or NDA before signing? Email security@oaura.ai.

Have a security question?

Our security team is happy to walk you through architecture, isolation, and our compliance roadmap.