Security
Security shown, not claimed
Elia runs autonomous LLM processes that touch your accounts. That is a real threat surface, so the gate sits in front of every request that needs it — and the design is written down, not just asserted on a landing page.
Identity
Per-user accounts with Argon2id password hashing. Short-lived JWT access tokens plus rotating refresh tokens, and a server-side session registry so any session can be revoked.
Authorization
Every route validates ownership of the resource it touches. The tenant id is derived from the session token — never from the request body or query string.
Secret isolation
Secrets are scoped per account and encrypted at rest (AES-256-GCM). System credentials never reach subprocesses; tool credentials are injected per worker.
Request hardening
CSRF protection on cookie flows, a strict CORS allow-list of first-party origins, per-user and per-IP rate limits, and brute-force lockout on login.
Agent containment
Shell execution runs inside a kernel-level sandbox. Worker output is scrubbed of secrets, and the browser tool blocks SSRF against metadata endpoints and private IPs.
Auditability
An append-only audit log records auth events, permission changes, every agent run, every tool call and every approval — keyed per user.
Per-user isolation, in practice
Each account gets its own workspace: its own agents, channels, tasks, skills, memory graph, cron jobs, secrets and run history. Isolation is physical — a separate workspace directory — rather than a column that every query must remember to filter.
One workspace per user
Own SQLite, vector store and key-value store per account. The strongest and simplest-to-audit model.
No cross-tenant reads
The data layer enforces the boundary. A direct request for another user's resource returns 403, not a filtered list.
Verifiable
Isolation is asserted by automated tests with two accounts, not by a marketing sentence.
Audit log
Every account has an activity record — signups and logins, agent creation and runs, task creation, session revocations. It is queryable from the dashboard and scoped to your tenant.
Questions
Security, answered
- Where is my data stored?
- In Local mode it stays on your machine — only account data is ever sent. In Cloud mode it is kept in the EU, in a workspace isolated to your account.
- Can an agent act without asking me?
- Only if you let it. Every agent runs at an autonomy level you choose — from Observe, which only watches and reports, to Act, which executes approved work on its own schedule and keeps proposing new work. You decide what gets approved, you can dial any agent back at any time, and every action is written to a log you can export.
- Are you ISO 27001 or SOC 2 certified?
- Not yet, and we do not display a seal we have not earned. Elia is designed against ISO/IEC 27001 and EN ISO/IEC 42001 controls, and a SOC 2 report is in preparation. Ask us for the current status before your procurement deadline.
- Which regulations is Elia built for?
- GDPR, EU data residency, the EU AI Act's Article 50 transparency obligations — in force since 2 August 2026 — NIS 2 and the Cyber Resilience Act.
- What happens to my data if I leave?
- Your workspace is a directory you own: agents, memory, tasks and transcripts. Take it with you, or keep running it offline.