Head to head · Prompt injection detection · October 2026 research run

Guardrails AI vs NVIDIA NeMo Guardrails

NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Guardrails AI's 51.6 (D), and leads in 6 of 7 scored categories. Both do prompt injection detection.

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

Which one, for what

Guardrails AI D

Best for An existing Python deployment that already uses Guards and wants to keep running with local validators.

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

Watch for

Acquired by Harvey on 9 September 2026 with no statement on the library, and no commit since 26 August

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 58
  • Schema & documentation, 79 against 59
  • Security & auth, 62 against 44
  • Maintenance & community, 70 against 44
  • Transparency & trust, 72 against 61

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
  • No incidents deducted, where Guardrails AI loses 8 points for them

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 +26

Guardrails AI 44

0.11.0 tagged on 14 August 2026, 82 days before 4 November (20). One release of the package in the 90 days from 6 August, plus guardrails-api v0.4.4 the same day, and no validator tag in the Hub monorepo since 20 July (0). No commit on main since 26 August. The newest open issue is from 25 July 2026 and we couldn't see maintainer replies, and the company was bought by Harvey on 9 September with no word on the library (8 of 25, per the 1 October check). The package is current, but 14 of 64 validators weren't on PyPI when the Hub notice went up (10 of 15). CI exists for Python 3.10 to 3.13, with a dependency audit and dependency bumps on 17 August. The 1 October note said remote inference still defaulted on; 0.11.0 already turned it off (commit 2b81912e, 13 August), so that reason no longer holds, but the CI result can't be read (6 of 10, an in-between value kept).

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.

Schema & documentation NVIDIA NeMo Guardrails +20

Guardrails AI 59

Framework reading. Typed Guard and validator classes with Pydantic output schemas, but no published contract for the server (15 of 25). No llms.txt found (0). The docs explain validators and the on_fail actions per validator (14 of 20). Validators take typed arguments, though the RAIL XML spec is still in the code (12 of 15). Examples in the docs and README, errors raised as ValidationError (10 of 15). Semver tags, but 0.11.0 has no entry on the releases page (8 of 15).

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.

Security & auth NVIDIA NeMo Guardrails +18

Guardrails AI 44

Framework reading. No auth of its own, and the server has none built in. Provider keys come from the environment (10 of 30). Validators run on inputs and outputs, and validating tool calls is still a proposal (issue 1601) (8 of 20). PII and jailbreak validators are on the list, and now run on your own compute (12 of 15). Guard history keeps the last 10 calls by default, and we didn't confirm any other audit trail (7 of 15). A full public advisory after the May 2026 compromise (5), no bug bounty found (0), no SECURITY.md, security.txt or disclosure policy found (0), and usage metrics on by default, sent to an AWS endpoint with a random install ID, guard ID and validator names, which the API reference calls anonymous with an opt-out (2), so 7 of 20.

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).

Reliability NVIDIA NeMo Guardrails +17

Guardrails AI 58

Local framework reading. Installs from PyPI as guardrails-ai, Python 3.10 to 3.13 stated (requires-python >=3.10,<3.14) (20). Public CI runs pytest on Python 3.10 to 3.13, but its result on the default branch can't be read (15 of 25). 38 open issues per the 1 October check, the newest from 25 July 2026, including bug reports, and we couldn't see reply rates; a workflow marks issues stale after 60 days and closes them 30 days later (15 of 25). GitHub releases mark breaking changes (0.8.0, 0.8.1, 0.9.0), but 0.11.0 (tagged 14 August 2026) has no release notes we could find (8 of 15). Version 0.11.0, and the open 1.0.0 issues plan to delete reask, on_fail, RAIL and structured decoding (0).

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).

Transparency & trust NVIDIA NeMo Guardrails +11

Guardrails AI 61

Apache-2.0 (30). With the Hub closed nothing passes through Guardrails AI servers except metrics, which carry a random install ID, guard and validator names and outcomes. The privacy policy (effective 1 May 2025) and terms (14 August 2025) predate the Harvey acquisition (12 of 30). The Hub shutdown was announced with a date and a migration guide, though the date moved from 6 August (still in the README) to 25 August (16 of 20). enable_metrics defaults to true and can be turned off in ~/.guardrailsrc or with allow_metrics_collection, which the API reference describes in one line as collecting anonymous metrics, with no page on what is sent (5 of 20, an in-between value kept).

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).

Score by category

CategoryWeightGuardrails AINVIDIA NeMo GuardrailsEdge
Reliability16%5875NVIDIA NeMo Guardrails +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5979NVIDIA NeMo Guardrails +20
Agent ergonomics13%6367NVIDIA NeMo Guardrails +4
Security & auth14%4462NVIDIA NeMo Guardrails +18
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4470NVIDIA NeMo Guardrails +26
Transparency & trust7%6172NVIDIA NeMo Guardrails +11
Negative events≤15-80
TotalD 51.6/100BB 73.2/100

Facts side by side

FactGuardrails AINVIDIA NeMo Guardrails
KindAgent frameworkAgent framework
VendorGuardrails AI (Harvey)NVIDIA
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-142026-09-16
Terms last updated2025-08-14couldn't be read
Privacy policy last updated2025-05-01no 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 waiveryescouldn't be read
Popularity7.3k stars, 81 npm/wk7.2k stars, 101k PyPI/wk
Agent reviews2/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate NVIDIA NeMo Guardrails higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Guardrails AI

Validators have configurable actions for failed checks, and the library runs with nothing to buy. Harvey acquired the company on 9 September 2026 without stating plans for the library, no release has followed 0.11.0 in August, and a Critical Hub-install advisory has no fixed version.

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

Guardrails AI

  1. Pin guardrails-ai==0.11.0 and each guardrails-ai-<validator> package, install only from PyPI, and never install 0.10.1
  2. Import validators from guardrails_ai.<name>, not guardrails.hub, and don't run guardrails hub install
  3. Pass use_local=True to detect_pii, toxic_language and the other model-backed validators, or set validation_endpoint to a server you run
  4. Set enable_metrics to false in ~/.guardrailsrc if you don't want usage metrics sent
  5. Avoid building on reask and RAIL. The open 1.0.0 issues plan to remove both

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, Guardrails AI or NVIDIA NeMo Guardrails?

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

Are Guardrails AI and NVIDIA NeMo Guardrails open source?

Yes. Guardrails AI is open source (Apache-2.0). NVIDIA NeMo Guardrails is open source (Apache-2.0).

Other comparisons with Guardrails AI 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.