Guardrails & Safety
Exogram + Lakera Guard
“Prompt injection defense. Not execution defense.”
What Lakera Guard Does
- •Lakera detects and blocks prompt injection attacks, PII leakage, and toxic content.
- •Real-time content filtering API for LLM inputs and outputs.
- •Protects the input surface — stopping malicious prompts before they reach the model.
- •Does not govern execution. Clean inputs can still produce harmful outputs.
What Exogram Does
- ▸Exogram protects the execution surface — stopping harmful actions before they reach your systems.
- ▸Prompt injection defense stops malicious inputs. Execution governance stops malicious actions.
- ▸A perfectly clean prompt can still generate a destructive tool call. Exogram catches it.
Key Differences
| Dimension | Lakera Guard | Exogram |
|---|---|---|
| Protection Surface | Input (prompts) | Output (actions) |
| What It Blocks | Malicious inputs | Malicious actions |
| Clean Input Risk | Assumes clean input = safe output | Validates regardless of input quality |
The Verdict
Use Lakera for input safety. Use Exogram because clean inputs don't guarantee safe actions. Both are needed.
Interception Latency Benchmark
Unlike standard LLM-based guardrails that invoke external APIs on every single tool execution, Exogram compiles policies to execute in-memory inside the client runtime.
Lakera Guard (LLM / API Check)~220.00 ms
Exogram Authority Runtime (In-Memory Intercept)0.07 ms
Is Lakera Guard vulnerable to execution drift?
Run a static analysis on your LLM pipeline below.
STATIC ANALYSIS
Frequently Asked Questions
Does Exogram detect prompt injection?
Exogram detects prompt injection patterns in tool call payloads as one of its 8 policy rules. But its primary function is execution governance, not input filtering. For comprehensive injection defense, use Lakera alongside Exogram.