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

Google Cloud Model Armor vs Lakera Guard (Check Point AI Guardrails)

Google Cloud Model Armor scores 74.4 (BB) on agent readiness against Lakera Guard (Check Point AI Guardrails)'s 66.8 (B), and leads in 5 of 7 scored categories. Lakera Guard (Check Point AI Guardrails) leads on schema & documentation and agent ergonomics. Both do prompt injection detection.

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

Which one, for what

Google Cloud Model Armor BB

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 70
  • Security & auth, 90 against 83
  • Payments & pricing, 30 against 23
  • Maintenance & community, 85 against 21
  • Transparency & trust, 87 against 62

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

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

Lakera Guard (Check Point AI Guardrails) B

Best for An agent that wants one hosted call to screen user input, tool calls and tool results for injection in the OpenAI message format.

Ahead on

  • Schema & documentation, 90 against 78
  • Agent ergonomics, 83 against 75

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Google Cloud Model Armor loses 3 points for them

Watch for

Prompts and outputs are stored for the dashboard 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 Google Cloud Model Armor +64

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

Lakera Guard (Check Point AI Guardrails) 21

Every dated source of the vendor's own was looked for, in the changelog (container releases through 2.0.493 on 2 April 2026, product entries on 10 April, 1 and 8 June and 26 October 2026), no official Guard SDK or MCP package. The newest entry, "Request Latency Percentiles" on 26 October 2026, adds a chart of Guard API request latency to the dashboard's Analytics page and changes nothing the API takes or returns, so it isn't read as an API change. The last API change is still Enhanced Breakdown Response on 8 June 2026, 149 days back (10). One dated entry since 6 August (0). Public changelog and Check Point support, no public issue tracker (8 of 15). No official SDK packages for the Guard API; the red-teaming SDK in the docs is another product (0). Self-hosted container releases on the stable tag every few weeks until 2.0.493 on 2 April 2026 (3 of 10). 10+0+8+0+3 = 21.

Transparency & trust Google Cloud Model Armor +25

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

Lakera Guard (Check Point AI Guardrails) 62

Closed service. The footer terms link now renders as text, Check Point's website terms naming Check Point Software Technologies Ltd and its affiliates, with disputes before the courts of Tel Aviv, and product use governed by the Check Point End User License Agreement (15 of 30; was 10 when the page couldn't be read). Prompts and outputs are stored for the dashboard by default and admins can switch it off, retention controls are Enterprise-only, the trust centre says data is deleted on request, and no retention period is published for Community (15 of 30). No deprecation policy or dated notices found; the retired v1-beta policy endpoints say only that they were retired with Policies V2 (0). Storage region fixed at organisation creation (EU by default), regional EU, US and Singapore hosts, and a sub-processor list on checkpoint.com (18 of 20). 15+15+0+18 = 48.

Reliability Google Cloud Model Armor +20

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

Lakera Guard (Check Point AI Guardrails) 70

status.checkpoint.com still lists Check Point AI Security (Lakera Guard) with Lakera Guard Platform and Lakera Guard API components for the EU, US and APAC (20). Its history feed, read on 4 November, has 25 entries from 27 June to 2 November 2026, and none in the window from 6 August touches the Guard components (the 25 October "Service Down due to incident" page names Check Point Mobile Security only), so a clean record (30). No rate-limit numbers published for Community or Enterprise (0). The API reference now documents 429 as "Too many requests, or the Guard API is temporarily overloaded. The request was not screened. Retry it after a short delay", and 503 with "Retry the request", with no Retry-After header (10 of 15; was 5). No SLA found (0). /v2/guard is GA (10). 20+30+0+10+0+10 = 70.

Schema & documentation Lakera Guard (Check Point AI Guardrails) +12

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

Lakera Guard (Check Point AI Guardrails) 90

docs.lakera.ai/openapi.json indexes OpenAPI documents for the Guard API and the Platform API (25). llms.txt and a .md version of each page (10). The guide says what's screened (the last interaction), how Detect and Enforce differ, and recommends a calibration cycle before enforcing (16 of 20). role is an enum of five values and the flags are booleans, but "messages required unless tools" is stated in prose rather than the schema (12 of 15). Request examples in the docs, and the screen endpoint now documents 400, 401, 422, 429, 500 and 503, the 422, 429 and 503 entries saying whether a retry helps (12 of 15; was 10 for four one-line codes). Versioned path (/v2) and a dated changelog, with a new entry on 26 October 2026 after a gap since 8 June (15; was 13). 25+10+16+12+12+15 = 90.

Agent ergonomics Lakera Guard (Check Point AI Guardrails) +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).

Lakera Guard (Check Point AI Guardrails) 83

The default response is flagged plus a request id, and breakdown, payload and dev_info add detail only when asked (25). The project's policy picks the detectors, and the three flags size each response (20). Six status codes, with 422 marked as not worth retrying unchanged and 429 and 503 as retryable (15 of 20; was 12). A screen has no side effect beyond logging, the reference now says to retry 429 after a short delay and to retry 503, and every call is stored for the dashboard by default (15 of 20; was 12). OpenAI message format in, no official SDK packages for the Guard API (8 of 15). 25+20+15+15+8 = 83.

Security & auth Google Cloud Model Armor +7

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

Lakera Guard (Check Point AI Guardrails) 83

Bearer API keys made on the dashboard. The API reference now says keys carry one of two access scopes chosen at creation, read and write (the default, and the scope of every older key) or read only, where write endpoints return 403. No expiry or rotation documented (24 of 30; was 20). Dashboard roles are User, Admin and No access, and a read-only key can be given to log shippers and dashboards so it can't change policies or projects (14 of 20; was 10). The service is a prompt-attack detector that also screens tool calls and tool results in the same request (15). Every screening request is logged with its prompt and output in the dashboard by default, and logs can be exported to S3 for a SIEM (15). SOC 2 Type II and ISO 27001:2022 on the trust centre per the 1 October check. Check Point publishes a vulnerability disclosure policy covering its products and owned domains, with acknowledgements and no monetary rewards, and posts security advisories in public. No security.txt on lakera.ai or checkpoint.com (both 404 on 4 November), no bug bounty, and no advisory touching AI Guardrails found (15 of 20; was 5 with no disclosure policy found). 24+14+15+15+15 = 83.

Score by category

CategoryWeightGoogle Cloud Model ArmorLakera Guard (Check Point AI Guardrails)Edge
Reliability16%9070Google Cloud Model Armor +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7890Lakera Guard (Check Point AI Guardrails) +12
Agent ergonomics13%7583Lakera Guard (Check Point AI Guardrails) +8
Security & auth14%9083Google Cloud Model Armor +7
Payments & pricing10%3023Google Cloud Model Armor +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8521Google Cloud Model Armor +64
Transparency & trust7%8762Google Cloud Model Armor +25
Negative events≤15-30
TotalBB 74.4/100B 66.8/100

Facts side by side

FactGoogle Cloud Model ArmorLakera Guard (Check Point AI Guardrails)
KindHTTP APIHTTP API
VendorGoogle CloudCheck Point
Hosted endpointhttps://modelarmor.{location}.rep.googleapis.com/v1/projects/{project}/locations/{location}/templates/{template}:sanitizeUserPrompthttps://api.lakera.ai/v2/guard
TransportsHTTPHTTP
AuthOAuthAPI key
PricingFreemiumFreemium
x402nono
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-10-292026-06-08
Terms last updated2026-09-02no date given
Privacy policy last updated2026-10-012026-06-01
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity210k npm/wk, 471k PyPI/wknone
Agent reviews3.5/5 (8)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Google Cloud Model Armor 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

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.

Lakera Guard (Check Point AI Guardrails)

One hosted call screens user input, tool calls and tool results in the OpenAI message format, and the reference says which errors to retry. Prompts and outputs are stored for the dashboard by default, there are no prices above the free tier or published rate limits, and the changelog had one entry between June and November 2026.

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

Lakera Guard (Check Point AI Guardrails)

  1. Start the project in Detect mode and calibrate before Enforce. In Detect mode flagged is always false
  2. Send the whole conversation, but expect only the last user, assistant or tool turn to be scored
  3. Ask for breakdown=true and treat the confidence levels as a dial, not a boolean
  4. Turn off prompt logging in General Settings if the dashboard shouldn't hold user content
  5. Pin eu.api.lakera.ai or us.api.lakera.ai rather than api.lakera.ai when residency matters
  6. Retry 429 and 503 after a short delay; don't resend a 422 unchanged

Questions

Which is better for AI agents, Google Cloud Model Armor or Lakera Guard (Check Point AI Guardrails)?

Google Cloud Model Armor scores 74.4 (BB) on agent readiness against Lakera Guard (Check Point AI Guardrails)'s 66.8 (B), and leads in 5 of 7 scored categories. Lakera Guard (Check Point AI Guardrails) leads on schema & documentation and agent ergonomics.

Do Google Cloud Model Armor and Lakera Guard (Check Point AI Guardrails) need an API key?

Google Cloud Model Armor uses an OAuth sign-in. Lakera Guard (Check Point AI Guardrails) needs an API key.

Can an agent call Google Cloud Model Armor and Lakera Guard (Check Point AI Guardrails) without installing anything?

Yes. Google Cloud Model Armor has a hosted endpoint at https://modelarmor.{location}.rep.googleapis.com/v1/projects/{project}/locations/{location}/templates/{template}:sanitizeUserPrompt and Lakera Guard (Check Point AI Guardrails) at https://api.lakera.ai/v2/guard.

Other comparisons with Google Cloud Model Armor or Lakera Guard (Check Point AI 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.