Multi-model access, policy that follows the payload, identity from your directory, and deployment in your own environment, up to a tier where nothing leaves it.
Join early accessYour payload catalog declares each type of business data, its schema and its sensitive fields. Policy is set per business line and data class, so the same model call is handled differently for payroll than for pipeline.
| Payload type | Business line | Policy |
|---|---|---|
| hr.employee_record | People | Isolated endpoints only; named fields redacted |
| finance.invoice | Finance | Never leaves your VPC |
| sales.opportunity | Sales | Any approved model; spend cap per team |
| comms.call_transcript | Customer success | Real-time endpoints; retention you control |
| unknown type | Any | Rejected. AtriumLLM never guesses. |
SSO with Entra ID, Okta or Google and SCIM user and group sync. Deprovisioned users lose access within one sync cycle.
Allowed models, sensitivity rules and budgets per user, group and business line, with cost reporting for chargeback.
Who sent which payload type to which model, when, and at what cost. Exportable. Every policy change is versioned, attributed and reversible.
Redact or block sensitive fields by name from your catalog, plus your own rules for client names, code and financial fields.
One deployment template, whether we host it or you do. Your cloud via Terraform or Helm, on-prem for full sovereignty, region-pinned per tenant, with egress allowlists.
We’re opening Enterprise with a small number of organizations, one business line at a time. Join early access and tell us where you’d start.