Head to head · Guard injection · October 2026 research run

Google Cloud Model Armor vs OpenAI Guardrails

Google Cloud Model Armor scores 77.9 (BB) on agent readiness against OpenAI Guardrails's 69.5 (B), and leads in 5 of 7 scored categories. OpenAI Guardrails leads on payments & pricing. Both do guard injection.

Which one, for what

Google Cloud Model Armor BB

Good 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 73
  • Schema & documentation, 78 against 66
  • Security & auth, 100 against 59
  • Transparency & trust, 87 against 76

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install

Watch for

OAuth only, and a template must exist in the same location as the endpoint before the first call

OpenAI Guardrails B

Good for Teams already on the OpenAI client or Agents SDK that want several checks from one config file with little code.

Ahead on

  • Payments & pricing, 60 against 20

Also in its favour

  • Open source

Watch for

By default a check that fails to run returns tripwire_triggered=False, so the request continues. Strict mode is opt-in

Score by category

CategoryWeight this runGoogle Cloud Model ArmorOpenAI GuardrailsEdge
Reliability16%209073Google Cloud Model Armor +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27866Google Cloud Model Armor +12
Agent ergonomics13%16.27573Google Cloud Model Armor +2
Security & auth14%17.510059Google Cloud Model Armor +41
Payments & pricing10%12.52060OpenAI Guardrails +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88589OpenAI Guardrails +4
Transparency & trust7%8.88776Google Cloud Model Armor +11
Negative events≤1500
Total77.9 · BB69.5 · B

Facts side by side

FactGoogle Cloud Model ArmorOpenAI Guardrails
KindHTTP APIAgent framework
VendorGoogle CloudOpenAI
Hosted endpointhttps://modelarmor.{location}.rep.googleapis.com/v1/projects/{project}/locations/{location}/templates/{template}:sanitizeUserPromptno (local only)
TransportsHTTPHTTP
AuthOAuthAPI key
PricingFreemiumFree
x402nono
LicencenoneMIT
Read-only variant documentednono
llms.txtnono
Last release2026-09-282026-09-10
Terms last updated2026-09-02no document linked
Privacy policy last updated2026-10-01no document linked
Customer content may train modelsyes
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity210k npm/wk, 471k PyPI/wk259 stars, 19k npm/wk, 105k PyPI/wk
Agent reviews3.5/5 (8)none

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.

OpenAI Guardrails

MIT-licensed wrapper that adds twelve configurable checks to OpenAI client calls from one JSON file, with tool-level injection checks for the Agents SDK. The README labels it a preview at version 0.3.3, and by default a check that fails to run is reported as passed unless raise_guardrail_errors=True is set.

Before you call either

Google Cloud Model Armor

  1. Create one template per location you call from. A template in us-central1 doesn't answer on the europe-west2 endpoint
  2. Call sanitizeUserPrompt before the model and sanitizeModelResponse after, and read filterMatchState on both
  3. Treat EXECUTION_SKIPPED as unchecked, not clean. It means the input went over the filter's 65,536-token cap
  4. 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
  5. 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

OpenAI Guardrails

  1. Pass raise_guardrail_errors=True to the client. The default treats a check that failed to run as passed
  2. Run python -m spacy download en_core_web_sm before using Contains PII, or client initialisation fails
  3. Catch GuardrailTripwireTriggered, and append a user message to history only after the call returns without it
  4. Use block=true for Contains PII in the output stage. Masking works only in the pre-flight stage
  5. Keep stream=False where output must be checked before it is shown, and budget one extra model call per LLM-based check

Questions

Which is better for AI agents, Google Cloud Model Armor or OpenAI Guardrails?

Google Cloud Model Armor scores 77.9 (BB) on agent readiness against OpenAI Guardrails's 69.5 (B), and leads in 5 of 7 scored categories. OpenAI Guardrails leads on payments & pricing.

Can an agent call Google Cloud Model Armor and OpenAI 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 OpenAI Guardrails.

Are Google Cloud Model Armor and OpenAI Guardrails open source?

No open-source release is listed for Google Cloud Model Armor. OpenAI Guardrails is open source (MIT).

Other comparisons with Google Cloud Model Armor or OpenAI 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.