Security Architecture: Isolation, Encryption, and Audit at Every Layer
Rilo isolates every organization's data, encrypts credentials, and logs every action — by default, not by configuration.
Jump to Architecture ↓Security Architecture
Org Isolation
Strict org-level isolation: your data is never mixed with other customers' data, and access failures default to blocking — not leaking.
Technical details
All data is partitioned by org_id (132-bit entropy). Org mapping lookup failures return HTTP 500 — fail-closed, never fail-open. Cross-org data leakage is architecturally impossible: the system errors out rather than returning data from the wrong tenant.
Encryption
All data encrypted at rest and in transit. Credentials stored in AWS Secrets Manager with per-org secret references, never in plaintext.
Credential Handling
Rilo uses invite flows and self-registration to acquire credentials — never OAuth redirects during task execution. Credentials are scoped per org and never shared.
Audit Logging
Tool executions and credential access are logged with org context. Structured audit trails support compliance review and incident investigation.
Browser Session Isolation
Browser sessions are never reused across orgs. Each task gets an isolated session with circuit-breaker protection for provider failover.
Compliance Status
We are actively pursuing SOC 2 Type II certification; audit scope is finalized and evidence collection is underway with a target completion window of H2 2026 — we have not yet achieved certification. GDPR-aligned data handling is implemented at the architecture level (org-isolated storage, data-residency-compatible design, deletion workflows) — a formal DPA is in preparation, targeting completion ahead of the SOC 2 report. All status labels reflect current progress — we never claim certifications we have not achieved.
Data Flow & Isolation
Every task flows through isolated execution contexts with strict org boundaries at every layer.
┌─────────────────────────────────────────────────────────────┐
│ Customer Request │
│ (Slack / Email / Webhook) │
└──────────────────────┬──────────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────┐
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────────┐ │
│ │ Signature │──▶│ Org Lookup │──▶│ Fail-Closed │ │
│ │ Validation │ │ (org_id) │ │ Tenant Gate │ │
│ └──────────────┘ └──────────────┘ └──────┬───────────┘ │
│ Ingress Layer │ │
└────────────────────────────────────────────────┼─────────────┘
│
▼ │
┌────────────────────────────────────────────────┼─────────────┐
│ Planning & Execution │ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │
│ │ Planner │──▶│ Node │──▶│ Tool │ │ │
│ │ (LLM) │ │ Runner │ │ Executor │ │ │
│ └──────────┘ └──────────┘ └────┬─────┘ │ │
│ │ │ │
│ ┌───────────────────────────┘ │ │
│ ▼ │ │
│ ┌──────────────┐ ┌──────────────────────┐ │ │
│ │ Isolated │ │ Org-Scoped │ │ │
│ │ Browser │ │ Memory Store │ │ │
│ │ Session │ │ (Encrypted) │ │ │
│ └──────────────┘ └──────────────────────┘ │ │
│ All scoped to org_id ─────────────────┘ │
└──────────────────────────────────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────┐
│ Audit Log │
│ Key actions recorded with org-scoped context │
└──────────────────────────────────────────────────────────────┘Need More Details?
Request a security questionnaire response or architecture whitepaper for your compliance review.