"We have a citizen developer issue right now: giving [all 5,000 employees] access to Claude Code or Codex. How do we ensure that we have the minimum right things in place?"
🧑💻 You ⇔ 💻 Claude Code ⇔ Luthien ⇔ ☁️ Anthropic API | logs every request and response. ~5-15ms you can configure rules/policies to modify or block certain responses or requests: | |-- did it do what I asked? |-- did it follow CLAUDE.md? +-- did it do something suspicious?
Luthien can call a separate model to check whether each response follows your rules. Runs alongside normal requests, adding almost no delay. When Claude Code compacts or starts a new session, Luthien still remembers. Your rules stay enforced from first prompt to last.
Uses your existing Anthropic subscription via OAuth. Luthien never sees your API key and there are no extra charges.
|
Gateways
|
Guardrails
|
Post-hoc
Code Review
|
Luthien
|
|
|---|---|---|---|---|
| Live conversation observability | ✗ | ✗ | ✗ | ✓1 |
| Block in real-time | Partial2 | ✓ | ✗ | ✓ |
| Fully customizable: modify, insert or run arbitrary logic mid-stream | ✗ | ✗ | ✗ | ✓3 |
| Open source | Partial4 | Partial5 | ✗ | ✓6 |
| Org-wide multi-conversation context | ✗ | ✗ | Partial | ✓ |
litellm was compromised by a supply-chain attack.
litellm meant losing everything.
"""Anthropic-native request processing pipeline.
This module provides a dedicated processing pipeline for Anthropic API
requests, using the native Anthropic types throughout without converting
to OpenAI format. This preserves Anthropic-specific features like
extended thinking, tool use patterns, and prompt caching.
Span Hierarchy
--------------
The pipeline creates a structured span hierarchy for observability:
anthropic_transaction_processing (root)
├── process_request
├── process_response
│ ├── policy_execute
│ └── send_upstream (zero or more backend calls)
└── send_to_client (non-streaming)
"""
"You guys are solving a very important problem. It's a
no-brainer that companies would want a proxy that monitors and restricts Claude Code traffic. I heard from higher-ups at Capital One that they're considering such tooling."
"Enterprise AI usage monitoring is going to be
very important in the near future."
"I think the space of AI risk mitigations is large and full of tricky details, and I am excited about people exploring mitigations like external API-level monitors."
Doesn't make sense for labs to build provider-agnostic tooling.
We asked the smartest people we know to trial our product.
They're proactively proposing improvements.
Power is nothing without control.
Enter your email to download the memo.