Platform

Runtime guardrails that hold while the AI runs.

Glacis sits in front of the actions your AI takes. The ones that cross a line you set are narrowed, held or refused while the action is live, and every covered decision leaves a signed record someone outside your company can check.

How the risk loop works

Decisions made while the action is live

Nobody ships a control that blocks everything. Glacis checks each action against the bounds you set and steps in only when one crosses them. The decision is made while the action is live, not in a queue someone reviews later.

  1. 01

    AI attempts an action

  2. 02

    Context and bounds

  3. 03 · Decision
    Allow Constrain Hold Deny
  4. 04

    Outcome reported

  5. 05

    Signed record

Allow: the action goes through unchanged. Constrain: it goes through with the risky part narrowed or redacted. Hold: it waits for a person. Deny: it’s refused, and the refusal is recorded.

Build versus buy

Nine things you don’t have to build

This is what sits between an agent that works and an agent anyone will let near production. Glacis runs all nine as a managed service, through every model swap and every new rule. None of it lands on your roadmap.

  1. 01Agent and workload identity
  2. 02Scoped credentials
  3. 03Network and tool boundaries
  4. 04Policy evaluationLive
  5. 05Classifier or model-based review
  6. 06Isolation
  7. 07Escalation
  8. 08Versioned evidenceLive
  9. 09Incident reconstructionLive

Policy evaluation, versioned evidence and incident reconstruction are in the product today. The other six stay the systems you already run, and Glacis works inside them. It doesn’t replace your identity provider, your cloud or your security program.

After guardrails

What the record is for

The record is for the questions that stall a pilot: the sign-off before an agent touches a real system, the security review that wants evidence instead of another policy document, and the question, months later, about one specific action. Guardrails come first, because outside review and risk transfer both need a record to work from.

  1. 01

    Guardrails, then evidence

    Put the boundary where the AI acts. A record of each covered decision builds as it runs, one record per governed action, so the covered set can be counted.

    Glacis

  2. 02

    Outside review

    An independent evaluator examines the controls and the record. Where a recognized certification applies, the record is one input to the assessor’s process.

    Independent evaluator · accredited assessor

  3. 03

    Risk transfer

    You can put a defined risk schedule to insurers, usually through a broker. Because each covered decision is one record, the exposure can be counted, and the count can be checked against the records without access to your systems. Underwriting, wording, pricing and claims are theirs to decide.

    Broker · underwriter · licensed insurer

Glacis is not a certifier or an insurer, and doesn’t guarantee certification, insurability, pricing or claims outcomes. Steps two and three are what others can do with the record, not services Glacis performs.

Try it on one real action: start free, or talk to us.