CattleGrid

Why CattleGrid?

Prevent sensitive data leakage and stay compliant.

What CattleGrid Does

CattleGrid sits between your applications and AI providers. Every AI API request passes through it. Before anything reaches Anthropic, OpenAI, Mistral, or Google, CattleGrid inspects the content, enforces your rules, and either blocks the request, redacts the sensitive data, or lets it through – logged and audited. It retains none of your data. Inspect, redact, block, discard. That is the complete sequence.

What CattleGrid Does

CattleGrid sits between your applications and AI providers. Every AI API request passes through it. Before anything reaches Anthropic, OpenAI, Mistral, or Google, CattleGrid inspects the content, enforces your rules, and either blocks the request, redacts the sensitive data, or lets it through – logged and audited. It retains none of your data. Inspect, redact, block, discard. That is the complete sequence.

What it never does

CattleGrid does not inspect AI responses. What the AI generates travels directly back to your application with zero buffering and zero modification. CattleGrid does not store customer request content – it exists only during processing and is discarded when the request completes. There is no database of your prompts. There is no log of what your staff typed.

The only records retained are: usage metadata ( counts, latencies, status codes), violation summaries (rule triggered and action taken – not the content that triggered it), and configuration audit events.

This is not a policy position. It is an architectural constraint enforced at every layer.

Prevent sensitive data leakage

CattleGrid inspects the content of every outbound request against your configured inspection rules. Rules can match regex patterns (e.g. UK National Insurance numbers, credit card numbers, postcodes) or keyword blocklists (e.g. internal project names, customer identifiers). When a rule triggers, CattleGrid can: