Skip to content
in/guard/out
in/guard/out

Compliance

Regulation meets the wire

The recurring themes across AI regulation – log what happened, minimize what you disclose, keep a human able to intervene, control what the system can do – are runtime properties. These pages map each framework’s obligations to the specific checks that support them.

The honest part, up front: no tool makes you compliant. Compliance is a property of your organization – its processes, contracts, and documentation – not of any component you install. What a guardrails proxy provides is technical measures and evidence that support the obligations below. Assess your own obligations with counsel.

Evidence beats attestation.

Every check records its verdict per request, every run keeps its trace – so when someone asks what your AI did and why, the answer is a query. We’re running a limited demo.