Skip to content

docs(enterprise): clarify which legacy guardrail callbacks are Enterprise-only#69

Open
Anai-Guo wants to merge 1 commit intoBerriAI:mainfrom
Anai-Guo:fix/enterprise-table-guardrails-clarification
Open

docs(enterprise): clarify which legacy guardrail callbacks are Enterprise-only#69
Anai-Guo wants to merge 1 commit intoBerriAI:mainfrom
Anai-Guo:fix/enterprise-table-guardrails-clarification

Conversation

@Anai-Guo
Copy link
Copy Markdown

@Anai-Guo Anai-Guo commented May 3, 2026

Closes BerriAI/litellm#27072

What

The OSS-vs-Enterprise comparison row for Guardrails in docs/enterprise.md previously read:

| Guardrails | Always-on / request-based | Key and team scoped guardrails |

This is misleading: while the guardrail framework itself is OSS, several of the built-in callback integrations advertised in the older guardrails docs (old_guardrails.md) actually require an Enterprise license — users who try to enable them on the OSS build are greeted with You must be a LiteLLM Enterprise user to use this feature.

Source-of-truth check

Looked at litellm/proxy/common_utils/callback_utils.py (callback name → implementation switch). The callbacks that import from litellm_enterprise.* and raise CommonProxyErrors.missing_enterprise_package are:

  • llmguard_moderations
  • llamaguard_moderations
  • hide_secrets
  • openai_moderations
  • google_text_moderation
  • lakera_prompt_injection
  • aporia_prompt_injection

presidio (PII masking) and detect_prompt_injection are OSS.

Change

Adds a footnote to the OSS column of the Guardrails row that lists the callback names that require Enterprise. Keeps the table layout intact and does not move any other docs.

Why this matters

Per the bug, users implement features against the comparison table believing them to be OSS, then only discover the licensing requirement at deploy time. The footnote turns the failure mode into a docs lookup.

🤖 Generated with Claude Code

@Anai-Guo Anai-Guo requested a review from a team May 3, 2026 04:17
@vercel
Copy link
Copy Markdown

vercel Bot commented May 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment May 3, 2026 4:19am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: misleading documentation: Trying to use Llm GuardYou must be a LiteLLM Enterprise user to use this feature.

1 participant