Head to head · PII detection · October 2026 research run

Presidio vs NVIDIA NeMo Guardrails

NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Presidio's 68.6 (B), and leads in 3 of 7 scored categories. Presidio leads on maintenance & community. Both do pii detection.

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

Which one, for what

Presidio B

Best for Detecting and masking personal data in prompts, outputs, logs and images on the owner's own machines, with detection tuned by entity, threshold and custom recognisers.

Ahead on

  • Maintenance & community, 78 against 70

Watch for

The REST containers have no authentication by design. The FAQ says to put a gateway or proxy in front

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

  • Schema & documentation, 79 against 71
  • Security & auth, 62 against 53
  • Transparency & trust, 72 against 67

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Presidio loses 3 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.

Security & auth NVIDIA NeMo Guardrails +9

Presidio 53

Local-software reading. The REST services have no authentication, and the FAQ says this is by design and that a gateway, proxy or service mesh should sit in front (10 of 30). The analyser only reads text and returns spans. The anonymiser returns a transformed copy and deletes nothing. There are no roles or approval steps (12 of 20). It returns positions, types and scores for the caller's own text, not content from third parties (10). Requests accept a correlation_id that is written to the service log, and return_decision_process explains each match. No audit log beyond that (9 of 15). SECURITY.md routes reports to GitHub private vulnerability reporting with acknowledgement in 48 hours, CodeQL runs in CI and workflow actions are pinned to commit hashes. No published advisories, no bug bounty and no security.txt (12 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).

Schema & documentation NVIDIA NeMo Guardrails +8

Presidio 71

API reading for the REST services. An OpenAPI 3.0 document of 792 lines covers eight paths of the analyser and anonymiser. The image redactor's /redact is not in it (22 of 25). presidio.dataprivacystack.org/llms.txt returns 404 on 1 November 2026 (0). Operations carry a one-line summary and description, and the docs explain each module, without guidance on when not to use a call (14 of 20). Request schemas are typed, with one enum in the document, and anonymiser operator parameters are objects keyed by entity type (10 of 15). Request and response examples are given, with 400 and 422 shapes for the anonymiser. The analyser's 500 on missing text is not in the document (11 of 15). Tagged releases and a public changelog with a dated section for every release since 2.2.364, which the 8 October check found missing. The document's own version still reads 2.0 (14 of 15). 22+0+14+10+11+14 = 71.

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.

Maintenance & community Presidio +8

Presidio 78

2.2.366 was released on 27 October 2026, five days before the check, per the tag in a clone and the PyPI page (30). Two releases since 3 August, 2.2.365 on 25 October and 2.2.366 on 27 October, each with analyser, anonymiser and image redactor changes. Half the line for two, as earlier dossiers read it (10 of 20). Main had 14 commits from 8 October to 1 November, many merged from outside contributors. Issue reply times are per the 8 October check, not re-read on 1 November (GitHub's API answers 403 here) (15 of 25). Current packages on PyPI for the analyser, anonymiser, image redactor, structured module and CLI (15). Dependabot, committed uv lockfiles refreshed in 2.2.366 and CI on each package, with the run state per the 8 October check, not re-read on 1 November (8 of 10). 30+10+15+15+8 = 78.

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.

Transparency & trust NVIDIA NeMo Guardrails +5

Presidio 67

MIT licence, with the copyright line changed from Microsoft Corporation to Presidio Contributors in July 2026 (30). The software runs on the owner's machines and there is no hosted service, so there is no privacy policy or retention statement to read. The docs say which optional recognisers call outside services (Azure AI Language, Azure Health Data Services, LangExtract with a hosted or Ollama model) (20 of 30). Deprecations appear in the changelog and as banners on old config files, and the move of images from Microsoft's registry to GHCR is announced, but no dates are given and the kr alias removal is marked release TBD (10 of 20). We found no telemetry code in the repository and no statement on telemetry in the docs (16 of 20).

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

CategoryWeightPresidioNVIDIA NeMo GuardrailsEdge
Reliability16%7875Presidio +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7179NVIDIA NeMo Guardrails +8
Agent ergonomics13%6967Presidio +2
Security & auth14%5362NVIDIA NeMo Guardrails +9
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7870Presidio +8
Transparency & trust7%6772NVIDIA NeMo Guardrails +5
Negative events≤15-30
TotalB 68.6/100BB 73.2/100

Facts side by side

FactPresidioNVIDIA NeMo Guardrails
KindSDK + MCPAgent framework
VendorData Privacy StackNVIDIA
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-272026-09-16
Terms last updatedno document linkedcouldn't be read
Privacy policy last updatedno document linkedno date given
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularity11k stars, 1.2M PyPI/wk7.2k stars, 101k PyPI/wk
Agent reviews3.3/5 (4)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Presidio

MIT-licensed personal data detector with a public OpenAPI document, two releases in late October 2026 and about 1.2 million weekly PyPI downloads. The REST containers have no authentication, 2.2.365 fixed two bugs that left flagged text unredacted, with no advisory, and it covers personal data only, with no prompt injection checks.

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

Presidio

  1. Install from PyPI or pull images from ghcr.io/data-privacy-stack. The mcr.microsoft.com/presidio-* images are no longer updated
  2. Use Python 3.11 to 3.14. Since 2.2.366 a Python 3.10 environment resolves to older releases
  3. Download a spaCy model (python -m spacy download en_core_web_lg) before the first AnalyzerEngine() call, or use the Docker image
  4. Send both text and language to /analyze. A request missing either returns HTTP 500 with a JSON error field
  5. Pass entities and score_threshold to limit results. Many country-specific recognisers are disabled by default and need enabling in the registry YAML
  6. Keep the containers on a private network or behind your own authenticating proxy. They accept any caller
  7. Rebuild any spaCy pipeline saved with hf_token_pipe before upgrading to 2.2.366, which registers presidio_hf_token_pipe instead

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

NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Presidio's 68.6 (B), and leads in 3 of 7 scored categories. Presidio leads on maintenance & community.

Are Presidio and NVIDIA NeMo Guardrails open source?

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

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