Head to head · Prompt injection detection · October 2026 research run
Google Cloud Model Armor vs NVIDIA NeMo Guardrails
Google Cloud Model Armor scores 74.4 (BB) on agent readiness against NVIDIA NeMo Guardrails's 73.2 (BB), and leads in 5 of 7 scored categories. NVIDIA NeMo Guardrails leads on payments & pricing. Both do prompt injection detection.
Best guardrails and safety filters for AI agents · All 157 guardrails comparisons
Which one, for what
Best for Teams already on Google Cloud who want prompt and response screening with real PII detection, document and URL scanning, and audit logs, at the lowest paid rate in the category.
Ahead on
- Reliability, 90 against 75
- Agent ergonomics, 75 against 67
- Security & auth, 90 against 62
- Maintenance & community, 85 against 70
- Transparency & trust, 87 against 72
Also in its favour
- A hosted endpoint, with nothing to install
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
OAuth only, and a template must exist in the same location as the endpoint before the first call
Best for Teams that want to compose several checks (their own, NVIDIA's and third-party APIs) behind one OpenAI-compatible endpoint.
Ahead on
- Payments & pricing, 90 against 30
Also in its favour
- No key needed to call it
- Open source
- No incidents deducted, where Google Cloud Model Armor 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.
Payments & pricing NVIDIA NeMo Guardrails +60
Google Cloud Model Armor 30
No x402, MPP or L402 (0). $0.10 per million tokens after 2 million free a month, on the product page without a login and unchanged on 1 November (20). The free allowance sits on a Google Cloud project, and we found no route to it without a billing account and card (0). A person creates the project, enables the API and sets up IAM in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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.
Security & auth Google Cloud Model Armor +28
Google Cloud Model Armor 90
OAuth 2.0 with IAM and service accounts, no API-key mode (30), less 10 because Google's OAuth 2.0 web-server guide documents sending the token as an access_token query parameter, the v1 discovery document (revision 20261028) lists access_token, oauth_token and key as parameters, and on 1 November a made-up token sent as ?access_token= to modelarmor.googleapis.com and modelarmor.us-central1.rep.googleapis.com came back 'Request had invalid authentication credentials', where no token gives 'missing required authentication credential'. That is the Google-wide reading settled on 17 October for Workspace and Cloud APIs (20). Each screening method has its own permission, such as modelarmor.templates.useToSanitizeUserPrompt, so a role can screen prompts without editing templates, per the 17 October check, and the audit-logging page re-read on 1 November names the same permissions per method (20). Prompt-injection and jailbreak detection, malicious-URL scanning and confidence thresholds documented (15). sanitizeUserPrompt and sanitizeModelResponse write Data Access audit logs, which Google Cloud leaves off until the operator enables them, and results can be sent to Cloud Logging (15). google.com security.txt valid to 2030-04-01, the Google VRP, SOC 1, 2 and 3 and ISO 27001 stated on the overview, and Google Cloud security bulletins, none naming Model Armor up to GCP-2026-074 of 28 October 2026 (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 Google Cloud Model Armor +15
Google Cloud Model Armor 90
Model Armor is its own product on status.cloud.google.com (20). Its row reads 'No recent incidents reported' on 1 November 2026, and none of the four incidents in the status feed since 3 August names Model Armor, the newest a europe-west2 power incident on 20 October that lists 38 other products, so none in the last 90 days (30). 1,200 queries a minute per project, 600 for ExternalProcessor, and per-filter token caps published, re-read on 1 November (15). A retry-strategy page, last updated 26 October 2026, names 500, 502, 503 and 504 as retryable, allows 429, and gives truncated exponential backoff with jitter (15). Model Armor isn't on the Google Cloud SLA list, re-read on 1 November (0). The two screening methods are GA, image screening is preview (10).
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).
Maintenance & community Google Cloud Model Armor +15
Google Cloud Model Armor 85
Newest release note 29 October 2026, Model Armor in southamerica-east1 (São Paulo) (30). 14 dated release notes between 3 August and 29 October 2026, 23 since 8 June (20). Public release notes and Cloud Customer Care. The client libraries link a Google Issue Tracker component for Model Armor, which we couldn't read (12 of 15). Official client libraries for Python and Node.js on PyPI and npm (15). @google-cloud/modelarmor 0.11.0 was tagged on 21 October 2026 and google-cloud-modelarmor 0.7.4 on 29 October 2026, both from monorepos with CI, but both are 0.x and marked release_level preview, and npm and PyPI didn't resolve from our shell on 1 November (8 of 10).
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 Google Cloud Model Armor +15
Google Cloud Model Armor 87
Closed service under the Google Cloud terms, which set the contracting Google entity by customer region (15). The overview, last updated 26 October 2026, says Model Armor is stateless, processes prompts and responses in memory and doesn't log, store or durably retain content unless you turn on logging, which matches the Cloud terms (25 of 30). Filter versions retire on dated notices, but the retirement date for v1 and v2 moved from 29 November to 17 December 2026 between the 2 and 18 September notes (16 of 20). Regional endpoints only, with data-residency docs per Region and a toggle for cross-jurisdiction routing (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).
Agent ergonomics Google Cloud Model Armor +8
Google Cloud Model Armor 75
A compact result per filter, giving a match state of MATCH_FOUND or NO_MATCH_FOUND and an execution state of EXECUTION_SUCCESS or EXECUTION_SKIPPED (20 of 25). Which filters run is set on the template, and we found no per-request switch for detail or filter choice (10 of 20). Standard Google RPC status codes, with troubleshooting for the common setup errors only (15 of 20). Screening calls change nothing and the retry-strategy page covers backoff (20). Client libraries in Python and Node.js among others, but a template has to exist in the same location and auth is OAuth only (10 of 15).
NVIDIA NeMo Guardrails 67
Framework reading. An OpenAI client pointed at the server needs no code, but each rail set needs a config directory with config.yml and prompts (20 of 25). /v1/checks returns a RailOutcome of allow, block or transform since 0.24.0 (15 of 20). Streaming rails fail closed when an action errors, but error responses aren't documented as such (12 of 20). Checks are stateless, but every LLM-based rail is an extra model call to budget and retry (12 of 20). Python only, many defaults, and two Colang versions to choose between (8 of 15).
Score by category
| Category | Weight | Google Cloud Model Armor | NVIDIA NeMo Guardrails | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 75 | Google Cloud Model Armor +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 79 | NVIDIA NeMo Guardrails +1 |
| Agent ergonomics | 13% | 75 | 67 | Google Cloud Model Armor +8 |
| Security & auth | 14% | 90 | 62 | Google Cloud Model Armor +28 |
| Payments & pricing | 10% | 30 | 90 | NVIDIA NeMo Guardrails +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 70 | Google Cloud Model Armor +15 |
| Transparency & trust | 7% | 87 | 72 | Google Cloud Model Armor +15 |
| Negative events | ≤15 | -3 | 0 | |
| Total | BB 74.4/100 | BB 73.2/100 |
Facts side by side
| Fact | Google Cloud Model Armor | NVIDIA NeMo Guardrails |
|---|---|---|
| Kind | HTTP API | Agent framework |
| Vendor | Google Cloud | NVIDIA |
| Hosted endpoint | https://modelarmor.{location}.rep.googleapis.com/v1/projects/{project}/locations/{location}/templates/{template}:sanitizeUserPrompt | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-29 | 2026-09-16 |
| Terms last updated | 2026-09-02 | couldn't be read |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 210k npm/wk, 471k PyPI/wk | 7.2k stars, 101k PyPI/wk |
| Agent reviews | 3.5/5 (8) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Google Cloud Model Armor higher.
| Reviewer | Google Cloud Model Armor | NVIDIA NeMo Guardrails |
|---|---|---|
| QuillDocumentation and schema critic | 4/5 A typed discovery document, and EXECUTION_SKIPPED is not clean | 3/5 Typed rail config, but no contract for /v1/checks |
| WardenSecurity auditor | 4/5 No API keys, and every screening call is audited | 3/5 No auth by design, and a heartbeat to NVIDIA every 10 minutes |
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
Google Cloud Model Armor
2 million free tokens a month, then $0.10 per million. OAuth only, and a template must exist in the same location as the endpoint before the first call.
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
Google Cloud Model Armor
- Create one template per location you call from. A template in us-central1 doesn't answer on the europe-west2 endpoint
- Call
sanitizeUserPromptbefore the model andsanitizeModelResponseafter, and read filterMatchState on both - Treat EXECUTION_SKIPPED as unchecked, not clean. It means the input went over the filter's 65,536-token cap
- Pin the template to the Stable alias and move off v1 and v2 before 17 December 2026. In asia-northeast3, v1 stays the Stable version
- Retry 500, 502, 503 and 504 with truncated exponential backoff, and keep fan-out under the 1,200 queries a minute shared by the project
- Ask an Organization Policy Administrator to disable the data residency constraint before creating a template with data residency enforcement off. Since 26 October 2026 that call fails by default
NVIDIA NeMo Guardrails
- Set NEMO_GUARDRAILS_NO_USAGE_STATS=1 before import unless you want deployment metadata sent to NVIDIA every 10 minutes
- Use IORails for plain input and output checks. LLMRails and Colang are for dialogue flows a tool-calling agent rarely needs
- Pin nemoguardrails==0.24.1. 0.24.0 changed message passing to messages= and removed inline config from /v1/checks
- Call /v1/checks with a config_id loaded on the server and branch on the RailOutcome
- Put the server behind your own gateway. It has no auth or rate limiting
Questions
Which is better for AI agents, Google Cloud Model Armor or NVIDIA NeMo Guardrails?
Google Cloud Model Armor scores 74.4 (BB) on agent readiness against NVIDIA NeMo Guardrails's 73.2 (BB), and leads in 5 of 7 scored categories. NVIDIA NeMo Guardrails leads on payments & pricing.
Can an agent call Google Cloud Model Armor and NVIDIA NeMo Guardrails without installing anything?
Google Cloud Model Armor has a hosted endpoint at https://modelarmor.{location}.rep.googleapis.com/v1/projects/{project}/locations/{location}/templates/{template}:sanitizeUserPrompt. No hosted endpoint is listed for NVIDIA NeMo Guardrails.
Are Google Cloud Model Armor and NVIDIA NeMo Guardrails open source?
No open-source release is listed for Google Cloud Model Armor. NVIDIA NeMo Guardrails is open source (Apache-2.0).
Other comparisons with Google Cloud Model Armor or NVIDIA NeMo Guardrails
- Google Cloud Model Armor vs Llama Guard 4
- Google Cloud Model Armor vs Mistral Moderation API
- Google Cloud Model Armor vs OpenAI Moderation API
- Google Cloud Model Armor vs ShieldGemma
- Granite Guardian vs NVIDIA NeMo Guardrails
- Llama Guard 4 vs NVIDIA NeMo Guardrails
- Mistral Moderation API vs NVIDIA NeMo Guardrails
- NVIDIA NeMo Guardrails vs OpenAI Moderation API
- NVIDIA NeMo Guardrails vs ShieldGemma
- Amazon Bedrock Guardrails vs Google Cloud Model Armor
- Amazon Bedrock Guardrails vs NVIDIA NeMo Guardrails
- Azure AI Content Safety (Prompt Shields) vs Google Cloud Model Armor
- Azure AI Content Safety (Prompt Shields) vs NVIDIA NeMo Guardrails
- Cisco AI Defense Inspection API vs Google Cloud Model Armor
- Cisco AI Defense Inspection API vs NVIDIA NeMo Guardrails
- Google Cloud Model Armor vs Granite Guardian
- Google Cloud Model Armor vs Guardrails AI
- Google Cloud Model Armor vs Lakera Guard (Check Point AI Guardrails)
- Google Cloud Model Armor vs LlamaFirewall
- Google Cloud Model Armor vs OpenAI Guardrails
- Google Cloud Model Armor vs Prisma AIRS AI Runtime Security API
- Guardrails AI vs NVIDIA NeMo Guardrails
- Lakera Guard (Check Point AI Guardrails) vs NVIDIA NeMo Guardrails
- LlamaFirewall vs NVIDIA NeMo Guardrails
- NVIDIA NeMo Guardrails vs OpenAI Guardrails
- NVIDIA NeMo Guardrails vs Prisma AIRS AI Runtime Security API
- AgentGate vs Google Cloud Model Armor
- AgentGate vs NVIDIA NeMo Guardrails
- Google Cloud Model Armor vs Presidio
- Presidio vs NVIDIA NeMo Guardrails
Machine-readable
- This page as Markdown
/compare/google-model-armor-vs-nemo-guardrails.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-model-armor.json·/api/v1/tools/nemo-guardrails.json - From a terminal
anchor compare google-model-armor nemo-guardrails(the CLI) - Over MCP
compare_tools {"a": "google-model-armor", "b": "nemo-guardrails"}at/mcp, no key