Skip to main content
Altrum follows each AI system through four steps: register it, assess it, protect it with guardrails, and govern its traffic. The first three work today. The fourth arrives with the AI Gateway.

​
The pieces

​
From assessment to guardrails

An assessment ends in a scope: the risks that apply, the controls that answer them, and the guardrails those controls map to. Submitting the assessment switches those guardrails on in your draft, set to Log only and with nothing chosen yet. The assistant then suggests settings from your answers, which you can add to the draft. You decide what goes live. Review the scope, set up every guardrail marked Needs your action, test the draft, and choose Complete Assessment. Your saved draft becomes the live version and the assessment closes. You can also configure guardrails without an assessment, at any time.

​
From guardrails to traffic

A live version is what Altrum enforces. Today you can test it against a sample message in the product. With the AI Gateway, every request an application sends for the AI system is checked against its live version before it reaches the model, and the answer is checked before it reaches the caller. If a check cannot be made, the request is not sent. A key attached to an AI system is checked against that AI system’s guardrails; any other key is checked against your organization’s. See Guardrails at runtime.

​
Who does what

Owners and admins manage the organization, its members and its AI systems. The owner of an AI system can run its assessment and configure its guardrails whatever their role. Every member can read AI systems, assessments and guardrails. See Members and roles for the full table.