ARX II is here. Your company’s OS.

Security

Built to hold as little as possible.

ARX puts your company’s AI Operating System on each employee’s computer. The model runs under your account, your systems stay the systems of record, and Imperium keeps the smallest footprint that still lets us serve you.

Permission modes in Imperium OS, set per session

Protection by design

Access is granted from the person's own computer; Imperium holds no passwords or tokens

Nothing of yours to steal

Imperium never holds your passwords or sign-in tokens for the apps ARX connects to. Each person grants access from their own browser and can withdraw it in one click; your administrator can withdraw everyone's at once.

Your systems stay the systems of record; nothing is copied or warehoused

Your systems stay the system of record

When ARX reads from or writes to your accounting, email, calendar or CRM, it does so at the moment of use. We do not copy or warehouse the contents of those systems.

Financial actions are draft-only until a person approves them in your own system

Money never moves without a person

Financial actions are draft-only by design. Nothing posts to your ledger, pays a bill or sends an invoice until a person approves it in your own system.

Each person's assistant gets only the tools their role allows

Least privilege, per role

Each person’s OS gets only the tools their role allows. Policy is enforced on our side and again on the device, and takes effect within a minute of a change.

Every action records who, what, when and whether it succeeded, never the data

An audit trail, not a data trail

Every action against a connected system records who, what, when and whether it succeeded. It never records the arguments or the data returned.

Updates and the AI engine are hash-verified before they install; builds are signed and notarized

Verified software on every machine

Updates and the AI engine are cryptographically hash-verified before they install, and macOS builds are signed and notarized. The assistant cannot modify the application it runs in.

Answers your security team will ask for

How it's built

The security flow: intercepted on the device, adjudicated at the gateway, isolated in the data plane, governed from the control planeA laptop on a platform, the employee device. A path leads through a highlighted gate, the action gateway, to a building, the business systems. A database platform to the front is the data plane, joined to the device by a dashed line for seat-scoped claims. A server platform at the back is the control plane: signed policy comes down to the device, telemetry and audit evidence go back. signed policytelemetry and audit evidenceseat-scoped claimsEMPLOYEE DEVICEexperience plane, runtime, reasoning coreevery model call is intercepted before it leavesACTION GATEWAYpolicy re-derived on the serverBUSINESS SYSTEMSbrokered, guardedDATA PLANErow-level isolationCONTROL PLANEsigned policy and updates
Every model call is intercepted on the employee's own device. Every external action is adjudicated at the action gateway, where policy is re-derived on the server. The data plane is isolated row by row per seat. Signed policy comes down from the control plane; telemetry and audit evidence go back up. Customer content never transits it.

Keep up with how it is built.

Security notes in the newsletter: what changed in the controls, new attestations as they land, and what each audit found.

Unsubscribe in one click.

A small desktop computer on a plinth behind a velvet rope, two calm guards either side, a contented owner with his hands in his pockets, and a defeated burglar walking away with an empty bag.