Guardrails
Layered policy enforcement, PII protection, and output validation — running on every call, below 13ms total.
Guardrails run automatically inside the engine on every intent call. Layered policy enforcement, PII protection, bias detection, output validation, and audit logging — safety that developers don't route around because it isn't optional application code.
Built-in policies
PII Redaction & Masking
Detect and redact PII in inputs and outputs — mask, hash, or replace with typed placeholders.
Content Filtering
Block harmful, off-topic, or brand-unsafe content using layered classifiers.
Bias & Fairness Filters
Detect and flag outputs with demographic bias, with pre-built hiring/lending/clinical detectors.
Role-Based Output Policies
Define what each user role can see, ask, and receive — enforced at runtime.
Grounding Verification
Flag or block hallucinated claims that lack source attribution from retrieval.
Full Audit Logging
Every input, output, and guardrail decision is logged with a tamper-evident trail.
Three-phase enforcement
| Phase | Latency | What runs |
|---|---|---|
| Pre-filter | < 5ms | Fast synchronous checks before the model call — harmful inputs, PII in prompts |
| Async validator | ~30ms | Heavier checks in parallel with the model response — PII redaction, bias detection, grounding |
| Post-filter | < 8ms | Final review before the response returns — role-based masking, compliance metadata |
Guardrails run in parallel with your workload, not in front of it — the tiered architecture keeps fast checks synchronous and heavy compliance work asynchronous, so total policy overhead stays under 13ms.