GLACIS
glacis.io
What it is
GLACIS puts controls in the path of AI actions and creates signed records of covered decisions for external verification. When an action crosses configured bounds, it can be constrained, held for a person, or denied; other actions can pass through unchanged. Glacis says it operates nine production components as a managed service alongside the identity provider, cloud, and security systems a customer already uses. Records use OVERT, a published open format that implementers and reviewers can inspect, and can be checked in a browser without a Glacis account. The site says payloads remain in the customer’s environment and records contain hashes; omitting protected fields depends on deployment setup. A record check does not establish whether an action was correct, whether every event was captured, or whether a system is safe or compliant. GLACIS is available by API, web, and self-hosted deployment. Its Free account costs nothing, with no card required. The contact page describes a six-week evaluation for a workflow under review.
Spec sheet
- What it does
- Glacis places runtime controls in the path of AI actions and creates signed records of covered decisions for external verification.Read 4 Oct 2026 · glacis.io
- Support
- Glacis says it typically replies to contact requests within one business day and takes on a small number of managed deployments each quarter.Read 4 Oct 2026 · glacis.io
- Control decisions
- For actions that cross configured bounds, Glacis can constrain, hold for a person, or deny the action; it can also allow actions through unchanged.Read 4 Oct 2026 · glacis.io
- Data handling
- The site says payloads stay in the customer’s environment and records carry hashes; protected fields can be left out, depending on deployment setup.Read 4 Oct 2026 · glacis.io
- Deployment evaluation
- The contact page describes a six-week evaluation on the workflow a customer is reviewing.Read 4 Oct 2026 · glacis.io
- Evidence pack limitation
- Glacis does not offer automated evidence-pack export today; packs are assembled by hand for a particular review.Read 4 Oct 2026 · glacis.io
- Managed service
- Glacis says it runs nine production components as a managed service, while working with the identity provider, cloud, and security systems the customer already uses.Read 4 Oct 2026 · glacis.io
- Open standard
- OVERT is a published open record format that implementers and reviewers can inspect and use without a proprietary schema.Read 4 Oct 2026 · glacis.io
- Records
- Records are signed and use OVERT, an open record format; a verifier can check a record in a browser without a Glacis account.Read 4 Oct 2026 · glacis.io
- Security reporting
- The vulnerability disclosure policy says Glacis aims to acknowledge reports within three business days and provide an initial assessment within ten business days; it offers no bug bounty.Read 4 Oct 2026 · glacis.io
- Verification limits
- A record check does not establish whether an action was correct, every event was captured, or a system is safe or compliant.Read 4 Oct 2026 · glacis.io
- Who it serves
- The signup form lists AI sellers serving healthcare or other regulated buyers, healthcare AI overseers, AI-agent builders or operators, and people evaluating the product.Read 4 Oct 2026 · glacis.io
Plans and prices
Strong points and limits
Strong points
- Controls can constrain, hold, deny, or pass actions through.
- Signed records use the published OVERT format.
- Records can be verified in a browser without an account.
- API, self-hosted, and web options are listed.
- Free account costs nothing.
Limits
- Automated evidence-pack export is not offered today.
- Record checks do not establish correctness or full event capture.
- Protected-field omission depends on deployment setup.
- Managed deployments are limited to a small number each quarter.
Who it suits
GLACIS suits AI-agent builders and operators, AI sellers serving regulated buyers, and healthcare AI overseers seeking controls and verifiable decision records. It may also fit people evaluating those capabilities for a particular workflow.
Verdict
GLACIS specifies both its runtime controls and the limits of its signed records. The lack of automated evidence-pack export and the stated limits of verification matter for teams assessing review workflows.
Where Specifiction places it
- LLM Security Tools#9 of 317.8