Security & compliance
Compliance in Avera is not a report generated at the end; it's how the platform works. Records can't be silently changed, access is denied by default, and every action is attributable.
21 CFR Part 11 compliant, eIDAS Advanced, with a signing factor owned and verified inside Avera, independent of your identity provider.
Every mutation is recorded exactly once, in a register that can't be updated or deleted, enforced by the database, not by convention.
Who changed it, when, why, and whether an AI proposed it and who approved it.
Versions are never overwritten; what was signed stays byte-identical forever.
Deny-by-default permissions down to individual fields in individual states · separation of duties and endorsements on critical transitions · an Access Explorer that answers "who can do what, and why" from the same engine that enforces it · SSO via OIDC.
Tenant isolation enforced in the database itself, not application convention · hosted in Switzerland (AWS), Swiss company, GDPR by default, DPA available · encryption in transit and at rest.
Your model, your keys: AI never trains on your data · every AI suggestion is a proposal a named human approves · AI authorship permanently visible · external AI tools (MCP) pass the same gates.
When Avera staff assist, the access is time-bound, visible in your own settings, and revocable by you, with every action audited.
Complete export at any time; no lock-in by design.
When a tenant is deleted, everything is destroyed: verified, not promised.