Security
Isolation is the architecture, not an afterthought
Every design decision below follows from one rule: nothing about your tenant — subscription, credentials, requests, or compute — is ever shared with another customer.
Tenant isolation
Each customer runs in a dedicated, network-isolated environment — never a shared process, never a shared queue behind other customers. There is no code path where one tenant's request can reach another tenant's environment.
Credential handling
You authenticate each agent (Codex, Claude Code, Gemini CLI, or Grok) yourself, via that provider's own sign-in flow, scoped to your isolated tenant environment. Adyrra never sees or stores your provider password — your session stays scoped to your tenant and is never shared with another customer.
No shared subscriptions
Your subscription is never pooled, rate-limited against other customers, or resold. The requests you send go through your own isolated environment, using your own login, against your own quota — the same as if you'd run the agent yourself.
Data handling
Nefin is a routing and orchestration layer, not a model provider — we don't train models on your prompts or completions. Request bodies pass through to your chosen CLI agent and back; we log operational metadata (timing, status codes) for reliability, not full conversation content.
Compliance status
We're an early-stage product. Formal certifications like SOC 2 or ISO 27001 aren't in place yet, but isolation-by-default has been the architecture from day one rather than something bolted on later. If a compliance report is a blocker for your evaluation, tell us — it helps us prioritize.
Reporting an issue
If you find a security issue, email info@adyrra.com with details — we'll respond directly.