Head to head · Content moderation · October 2026 research run

Llama Guard 4 vs NVIDIA NeMo Guardrails

NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Llama Guard 4's 52.3 (D), and leads in 6 of 7 scored categories. Both do content moderation.

Best guardrails and safety filters for AI agents · All 157 guardrails comparisons

Which one, for what

Llama Guard 4 D

Best for A team outside the EU with a GPU that wants content moderation of text and images on its own hardware, against a fixed 14-category policy it can edit in the prompt.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Weights last changed on 29 April 2025, with no changelog, version tags or stated deprecation policy

NVIDIA NeMo Guardrails BB

Best for Teams that want to compose several checks (their own, NVIDIA's and third-party APIs) behind one OpenAI-compatible endpoint.

Ahead on

  • Reliability, 75 against 38
  • Schema & documentation, 79 against 52
  • Security & auth, 62 against 53
  • Payments & pricing, 90 against 68
  • Maintenance & community, 70 against 28
  • Transparency & trust, 72 against 59

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community NVIDIA NeMo Guardrails +42

Llama Guard 4 28

Read for an open-weight model. The weights and model card were last changed on 29 April 2025, more than 17 months ago (0 of 30). No model revision since, and no successor or retirement announced that we found. Stability earns part of the line under the model reading (8 of 20). Meta staff answered Hugging Face threads in April and May 2025. Threads opened since June 2025, including one of 20 October 2026, have no Meta reply on 4 November, two pull requests from January and August 2026 are still open, and GitHub issue 108 on missed threats in Italian was forwarded on 28 May 2025 with nothing after (6 of 25). transformers, vLLM and SGLang load it per the Hugging Face page on 8 October, and Meta's cookbook has a notebook (10 of 15). PurpleLlama had commits on 29 September, 12 October and 30 October 2026, all type-check or benchmark-dataset housekeeping, with tests passing and lint failing on 29 September per the 8 October check (4 of 10). 0 + 8 + 6 + 10 + 4 = 28. The 20-point line is read for a model (notice periods and churn), as for muse-spark-open.

NVIDIA NeMo Guardrails 70

0.24.1 on 16 September 2026, 46 days before the check, with no release since in the repository's tags (20). Two releases in the 90 days from 3 August, 0.24.0 on 25 August and 0.24.1, with 0.23.0 on 1 July outside (10 of 20, our batch rule for two). 71 commits on develop since 0.24.1, the last on 30 October, are unreleased. Issues get triage labels, but about a dozen opened in August read needs triage, per the 1 October check, not re-read on 1 November (15 of 25). Current package on PyPI, per the 1 October check (15). CI on three operating systems and supported runtimes stated (10). 20+10+15+15+10 = 70.

Reliability NVIDIA NeMo Guardrails +37

Llama Guard 4 38

Scored on the local-software lines, since the owner runs the model. Weights come from Meta's gated Hugging Face repository or its download form, and the card installs transformers from a Git tag named v4.51.3-LlamaGuard-preview. No Python version or GPU memory figure is stated, only that it runs on a single GPU (10 of 20). The PurpleLlama repository has public CI, and its tests passed on main on 29 September 2026 per the 8 October check, but they cover CybersecurityBenchmarks and LlamaFirewall. Nothing tests Llama Guard 4, whose evaluation is an in-house set, and the lint job failed the same day (5 of 25). Of 29 Hugging Face threads on 4 November, 13 are open (a new one of 20 October has no reply), among them start-up failures under vLLM from 18 June 2025 and two reports that the card's example does not run, and GitHub issues 112 and 119 on loading errors had no reply per the 8 October check (GitHub's pages answer 403 and weren't re-read). Activity is low (8 of 25). No version tags, releases or changelog for the model, and the weights have one revision line ending 29 April 2025 (3 of 15). Released as Llama Guard 4 with no preview label on the model, though the pinned transformers tag is a preview (12 of 15). 10 + 5 + 8 + 3 + 12 = 38.

NVIDIA NeMo Guardrails 75

Local framework reading. Installs from PyPI as nemoguardrails, pyproject on develop states Python 3.10 to 3.13 (20). The README carries passing badges for tests on Linux, Windows and macOS and for lint on the develop branch, per the 1 October check, not re-read on 1 November (25). About 140 open issues and 80 to 100 open pull requests, with bug reports from August 2026 still labelled needs triage beside others already triaged, per the 1 October check, not re-read on 1 November (15 of 25). The changelog follows Keep a Changelog and marks breaking items, six of them in 0.24.0 (15). Version 0.24.1, not 1.0, and develop now reads 0.25.0-rc1, unreleased (0).

Schema & documentation NVIDIA NeMo Guardrails +27

Llama Guard 4 52

Read for a model the owner serves. There is no specification of its own. The contract is chat_template.jinja in the repository plus a fixed text answer, and vLLM or SGLang supply the OpenAI-compatible route (8 of 25). No llms.txt for the Llama docs, and dev.meta.ai/llms.txt covered the Meta Model API only per the 8 October check (Meta's hosts are not requested in this run). The model card is Markdown on GitHub (5 of 10). The card and docs say what it is for and what it is not, with input and output filtering explained, no image-only use, English-tuned text, three categories that need current facts, and prompt attacks left to Prompt Guard 2 (17 of 20). Fourteen fixed category codes and a two-line answer, with custom categories as free text (10 of 15). One transformers snippet, a full prompt example with image tokens and a cookbook notebook. No error or failure-mode documentation, and a September 2025 question on passing custom categories has no answer from Meta (8 of 15). Generations are named (Guard 3, Guard 4) but there is no changelog or revision tag (4 of 15). 8 + 5 + 17 + 10 + 8 + 4 = 52.

NVIDIA NeMo Guardrails 79

Framework reading. Rail configuration is typed in Python and validated on load, and the server speaks the OpenAI chat-completions shape. The repository holds a Fern OpenAPI file, generated at docs build time since 23 October 2026, but no published OpenAPI document for /v1/checks was found in the docs (15 of 25). The docs serve llms.txt at docs.nvidia.com/nemo/guardrails/llms.txt, with a 681-line index of Markdown pages for the latest version and one per release from 0.22.0 (10). The docs describe each rail type and the built-in and third-party rails, and 0.24.0 added IORails, which runs input and output rails without the Colang runtime (15 of 20). YAML configuration with typed models, though Colang 1 and Colang 2 coexist (12 of 15). An examples tree in the repository and per-rail guides, little on error responses (12 of 15). Semver releases and a dated changelog (15). 15+10+15+12+12+15 = 79.

Payments & pricing NVIDIA NeMo Guardrails +22

Llama Guard 4 68

Self-hosted rule, with one departure. Nothing to buy from Meta, and the licence allows commercial use at no charge (20). Free to run with no card (20). The rule would give 20 for use without sign-up, but the weights sit behind a form reviewed by hand that asks for a legal name and date of birth, and two threads in May and June 2026 report rejections, so an agent cannot get access alone (5 of 20). No payment protocol (0). DeepInfra's hosted copy cost $0.18 per 1M tokens per the 8 October check and needs its own account; Hugging Face lists it as the one live provider on 4 November. 20 + 20 + 5 + 0 = 45. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

NVIDIA NeMo Guardrails 90

Apache-2.0 package you run yourself with nothing to buy from the project, so 20 for pricing, 20 for a free start and 20 for keyless use. No payment protocol (0). The NemoGuard models it can call are priced separately by NVIDIA. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Transparency & trust NVIDIA NeMo Guardrails +13

Llama Guard 4 59

Weights are downloadable under the Llama 4 Community Licence, which is clear but not an OSI licence. It carries attribution and naming conditions, an acceptable use policy, and no grant for multimodal models to individuals or companies based in the European Union (17 of 30). Inputs stay on the owner's hardware. No privacy statement covers the model, the access form's details go to Meta under its general privacy policy, and training data is described only in outline (20 of 30). No deprecation policy or dates. The docs say Guard 4 replaces Guard 3 8B and 11B and that Guard 3 1B stays useful on edge devices (5 of 20). Weights carry no telemetry, but we found no statement either way and downloads go through Hugging Face (10 of 20). 17 + 20 + 5 + 10 = 52. Licence and use-policy text read in the PurpleLlama clone (Llama-Guard4/12B/LICENSE and USE_POLICY.md); the dev.meta.ai copies per the 8 October check.

NVIDIA NeMo Guardrails 72

Apache-2.0 with a third-party licence file (30). The telemetry page lists what's sent (version, configuration, which capabilities are switched on, deployment type) and what isn't (prompts, completions, messages, keys, endpoints). We didn't read the code to confirm it (25 of 30). Breaking items are marked per release, but there's no deprecation policy with dates (12 of 20). Telemetry with heartbeats every 10 minutes is on by default, opt-out with NEMO_GUARDRAILS_NO_USAGE_STATS=1, DO_NOT_TRACK=1 or a do_not_track file, and off in CI (15 of 20).

Security & auth NVIDIA NeMo Guardrails +9

Llama Guard 4 53

Read as software the owner runs. No account is needed to run it. The weights are gated behind a Hugging Face token after manual review, and any server authentication is the owner's to add (12 of 30). A classifier with no write actions (15 of 20). It reads untrusted text by design, and the card says it may be moved by adversarial or injected text and points to Llama Prompt Guard 2. No mitigation guidance beyond that (8 of 15). No call log of its own. Visibility depends on the serving stack (5 of 15). PurpleLlama's CONTRIBUTING.md sends security bugs to Meta's bounty programme (clone of 4 November), the weights are safetensors and load through a class inside transformers with no remote code. No security.txt on dev.meta.ai per the 8 October check, and no SECURITY.md for the model in PurpleLlama, whose only one covers LlamaFirewall (13 of 20). 12 + 15 + 8 + 5 + 13 = 53.

NVIDIA NeMo Guardrails 62

Framework reading. No auth of its own, and SECURITY.md says authentication, authorisation, TLS and rate limiting are the deployer's job. Provider keys come from the environment (10 of 30). Tool-input and tool-output rails can block a tool call, but there's no human approval hook, and the LLM-judged tool_safety_check is only on develop since 29 September 2026 (12 of 20). Jailbreak heuristics and model, injection detection and content-safety rails, documented (15). OpenTelemetry tracing to your own backend, opt-in (12 of 15). Disclosure through NVIDIA PSIRT, no bug bounty, no published advisories, and usage telemetry to NVIDIA on by default with a documented opt-out (13 of 20).

Score by category

CategoryWeightLlama Guard 4NVIDIA NeMo GuardrailsEdge
Reliability16%3875NVIDIA NeMo Guardrails +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5279NVIDIA NeMo Guardrails +27
Agent ergonomics13%6767even
Security & auth14%5362NVIDIA NeMo Guardrails +9
Payments & pricing10%6890NVIDIA NeMo Guardrails +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2870NVIDIA NeMo Guardrails +42
Transparency & trust7%5972NVIDIA NeMo Guardrails +13
Negative events≤1500
TotalD 52.3/100BB 73.2/100

Facts side by side

FactLlama Guard 4NVIDIA NeMo Guardrails
KindModel APIAgent framework
VendorMetaNVIDIA
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneNone
PricingFreeFree
x402nono
LicenceLlama 4 Community Licence (source-available weights, not an OSI licence), with the Llama 4 acceptable use policyApache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2025-04-292026-09-16
Terms last updated2025-04-05couldn't be read
Privacy policy last updatedno document linkedno date given
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity4.4k stars7.2k stars, 101k PyPI/wk
Agent reviewsnone3/5 (2)

How the scores have moved

Verdicts

Llama Guard 4

A single self-hosted model classifies text and multi-image prompts against 14 MLCommons-aligned hazard categories and answers in a few tokens. The weights have not changed since 29 April 2025, download access needs Meta's manual approval, and the licence withholds the grant from individuals and companies based in the European Union.

NVIDIA NeMo Guardrails

Apache-2.0, 7,200 stars and nine releases between 9 October 2025 and 16 September 2026. Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default.

Before you call either

Llama Guard 4

  1. Request access on the Hugging Face page before anything else. Approval is manual, and the form cannot be edited after submission
  2. Send only the user turn to check an input, and the user turn plus the model's answer to check an output. The template picks the role from the message count
  3. Parse the first line for safe or unsafe and the second for category codes. Set max_new_tokens to about 10 and turn sampling off
  4. Do not send an image with no text. Meta says the model is not an image-only classifier, and S14 is skipped when an image is present
  5. Pair it with a prompt-attack detector. The card says the model can itself be moved by adversarial or injected text

NVIDIA NeMo Guardrails

  1. Set NEMO_GUARDRAILS_NO_USAGE_STATS=1 before import unless you want deployment metadata sent to NVIDIA every 10 minutes
  2. Use IORails for plain input and output checks. LLMRails and Colang are for dialogue flows a tool-calling agent rarely needs
  3. Pin nemoguardrails==0.24.1. 0.24.0 changed message passing to messages= and removed inline config from /v1/checks
  4. Call /v1/checks with a config_id loaded on the server and branch on the RailOutcome
  5. Put the server behind your own gateway. It has no auth or rate limiting

Questions

Which is better for AI agents, Llama Guard 4 or NVIDIA NeMo Guardrails?

NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Llama Guard 4's 52.3 (D), and leads in 6 of 7 scored categories.

Can an agent call Llama Guard 4 and NVIDIA NeMo Guardrails without installing anything?

No hosted endpoint is listed for Llama Guard 4. No hosted endpoint is listed for NVIDIA NeMo Guardrails.

Are Llama Guard 4 and NVIDIA NeMo Guardrails open source?

No open-source release is listed for Llama Guard 4. NVIDIA NeMo Guardrails is open source (Apache-2.0).

Other comparisons with Llama Guard 4 or NVIDIA NeMo Guardrails

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.