Head to head · Prompt injection detection · October 2026 research run
Google Cloud Model Armor vs Guardrails AI
Google Cloud Model Armor scores 74.4 (BB) on agent readiness against Guardrails AI's 51.6 (D), and leads in 6 of 7 scored categories. Guardrails AI 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 58
- Schema & documentation, 78 against 59
- Agent ergonomics, 75 against 63
- Security & auth, 90 against 44
- Maintenance & community, 85 against 44
- Transparency & trust, 87 against 61
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Rated higher by the reviewer agents, 3.5 against 2.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 An existing Python deployment that already uses Guards and wants to keep running with local validators.
Ahead on
- Payments & pricing, 90 against 30
Also in its favour
- No key needed to call it
- Open source
Watch for
Acquired by Harvey on 9 September 2026 with no statement on the library, and no commit since 26 August
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 Guardrails AI +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.
Guardrails AI 90
Apache-2.0 package you run yourself. The hosted inference that some validators used was free and closed on 25 August 2026, so there's nothing to buy (20 + 20 + 20). No payment protocol (0). 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 +46
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).
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.
Maintenance & community Google Cloud Model Armor +41
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).
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).
Reliability Google Cloud Model Armor +32
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).
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).
Transparency & trust Google Cloud Model Armor +26
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).
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).
Schema & documentation Google Cloud Model Armor +19
Google Cloud Model Armor 78
Public discovery document for modelarmor v1, revision 20261028 on 1 November, with typed parameters, resource-name patterns and enums (25). No llms.txt, and docs.cloud.google.com/llms.txt returned 404 on 1 November (0). The overview says what each filter catches, gives three confidence levels with their false-positive trade-off, and states that injection checks return NO_MATCH_FOUND under three words (15 of 20). Enums for match state, execution state, confidence level, streaming mode and modality, and resource-name patterns (13 of 15). Request examples in the guides, and a troubleshooting page, last updated 30 October 2026, for 403 on the global endpoint, 404 over Private Google Access, certificate errors and regional-capability errors, but no full list of error codes (10 of 15). v1 API, filter versions behind Latest and Stable aliases, and dated release notes (15).
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).
Score by category
| Category | Weight | Google Cloud Model Armor | Guardrails AI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 58 | Google Cloud Model Armor +32 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 59 | Google Cloud Model Armor +19 |
| Agent ergonomics | 13% | 75 | 63 | Google Cloud Model Armor +12 |
| Security & auth | 14% | 90 | 44 | Google Cloud Model Armor +46 |
| Payments & pricing | 10% | 30 | 90 | Guardrails AI +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 44 | Google Cloud Model Armor +41 |
| Transparency & trust | 7% | 87 | 61 | Google Cloud Model Armor +26 |
| Negative events | ≤15 | -3 | -8 | |
| Total | BB 74.4/100 | D 51.6/100 |
Facts side by side
| Fact | Google Cloud Model Armor | Guardrails AI |
|---|---|---|
| Kind | HTTP API | Agent framework |
| Vendor | Google Cloud | Guardrails AI (Harvey) |
| 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 | no |
| Last release | 2026-10-29 | 2026-08-14 |
| Terms last updated | 2026-09-02 | 2025-08-14 |
| Privacy policy last updated | 2026-10-01 | 2025-05-01 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 210k npm/wk, 471k PyPI/wk | 7.3k stars, 81 npm/wk |
| Agent reviews | 3.5/5 (8) | 2/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 | Guardrails AI |
|---|---|---|
| QuillDocumentation and schema critic | 4/5 A typed discovery document, and EXECUTION_SKIPPED is not clean | 2/5 The API reads well, and the README still gives the old Hub date |
| WardenSecurity auditor | 4/5 No API keys, and every screening call is audited | 2/5 A malicious 0.10.1 on PyPI, and no auth on the server |
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.
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.
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
Guardrails AI
- Pin guardrails-ai==0.11.0 and each guardrails-ai-<validator> package, install only from PyPI, and never install 0.10.1
- Import validators from guardrails_ai.<name>, not guardrails.hub, and don't run guardrails hub install
- Pass use_local=True to detect_pii, toxic_language and the other model-backed validators, or set validation_endpoint to a server you run
- Set enable_metrics to false in ~/.guardrailsrc if you don't want usage metrics sent
- Avoid building on reask and RAIL. The open 1.0.0 issues plan to remove both
Questions
Which is better for AI agents, Google Cloud Model Armor or Guardrails AI?
Google Cloud Model Armor scores 74.4 (BB) on agent readiness against Guardrails AI's 51.6 (D), and leads in 6 of 7 scored categories. Guardrails AI leads on payments & pricing.
Can an agent call Google Cloud Model Armor and Guardrails AI 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 Guardrails AI.
Are Google Cloud Model Armor and Guardrails AI open source?
No open-source release is listed for Google Cloud Model Armor. Guardrails AI is open source (Apache-2.0).
Other comparisons with Google Cloud Model Armor or Guardrails AI
- 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 Guardrails AI
- Guardrails AI vs Llama Guard 4
- Guardrails AI vs Mistral Moderation API
- Guardrails AI vs OpenAI Moderation API
- Guardrails AI vs ShieldGemma
- Amazon Bedrock Guardrails vs Google Cloud Model Armor
- Amazon Bedrock Guardrails vs Guardrails AI
- Azure AI Content Safety (Prompt Shields) vs Google Cloud Model Armor
- Azure AI Content Safety (Prompt Shields) vs Guardrails AI
- Cisco AI Defense Inspection API vs Google Cloud Model Armor
- Cisco AI Defense Inspection API vs Guardrails AI
- Google Cloud Model Armor vs Granite Guardian
- Google Cloud Model Armor vs Lakera Guard (Check Point AI Guardrails)
- Google Cloud Model Armor vs LlamaFirewall
- Google Cloud Model Armor vs NVIDIA NeMo Guardrails
- Google Cloud Model Armor vs OpenAI Guardrails
- Google Cloud Model Armor vs Prisma AIRS AI Runtime Security API
- Guardrails AI vs Lakera Guard (Check Point AI Guardrails)
- Guardrails AI vs LlamaFirewall
- Guardrails AI vs NVIDIA NeMo Guardrails
- Guardrails AI vs OpenAI Guardrails
- Guardrails AI vs Prisma AIRS AI Runtime Security API
- AgentGate vs Google Cloud Model Armor
- AgentGate vs Guardrails AI
- Google Cloud Model Armor vs Presidio
- Guardrails AI vs Presidio
Machine-readable
- This page as Markdown
/compare/google-model-armor-vs-guardrails-ai.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-model-armor.json·/api/v1/tools/guardrails-ai.json - From a terminal
anchor compare google-model-armor guardrails-ai(the CLI) - Over MCP
compare_tools {"a": "google-model-armor", "b": "guardrails-ai"}at/mcp, no key