Head to head · Prompt injection detection · October 2026 research run
Amazon Bedrock Guardrails vs Lakera Guard (Check Point AI Guardrails)
Amazon Bedrock Guardrails scores 79.3 (A) on agent readiness against Lakera Guard (Check Point AI Guardrails)'s 66.8 (B), and leads in every scored category. Both do prompt injection detection.
Best guardrails and safety filters for AI agents · All 157 guardrails comparisons
Which one, for what
Best for A team already on AWS that wants one versioned policy covering topics, PII masking, grounding and prompt attacks in front of any model.
Ahead on
- Reliability, 75 against 70
- Agent ergonomics, 93 against 83
- Security & auth, 96 against 83
- Payments & pricing, 45 against 23
- Maintenance & community, 65 against 21
- Transparency & trust, 70 against 62
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Per-policy billing, so four paid policies on one request cost four times, and no Guardrails-specific free tier
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.
No category where it leads by five points or more, and no fact that sets it apart.
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 Amazon Bedrock Guardrails +44
Amazon Bedrock Guardrails 65
Read by the listing's own shapes in the bedrock and bedrock-runtime service models, as this run's amazon-s3 re-check read models/s3. The bedrock model changed on 20 October 2026, adding a Standard or Classic tier for contextual grounding checks and raising the regex filters a guardrail can hold from 10 to 30. The document history (19 October) and What's New (20 October) announced the Standard tier for contextual grounding, 12 days before 1 November (30, up from 10, cause product). In the 90 days from 3 August we found two dated Guardrails changes, the 20 October one and wider name patterns for Automated Reasoning policy definitions on 30 September, which the 17 October check didn't count. Other bedrock and bedrock-runtime changes in the window (31 July, 24 August, 4 September) touch no guardrail shape, so fewer than three (0). Public document history and What's New, and support through re:Post and AWS Support, but the history still misses the April and June 2026 launches (10 of 15). Current SDKs, boto3 1.43.123 on 30 October 2026 (per its release tag) and the @aws-sdk/client-bedrock-runtime client with 21,122,074 npm downloads in the week to 29 October (15). SDKs ship near-daily and support Python 3.10 and later (10). 30 + 0 + 10 + 15 + 10 = 65.
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.
Payments & pricing Amazon Bedrock Guardrails +22
Amazon Bedrock Guardrails 45
No x402, MPP or L402 (0). Per-policy prices per 1,000 text units published without a login, unchanged on 1 November (20). No Guardrails-specific free tier on the pricing page, but new AWS accounts get up to $200 in Free Tier credits and the Free Tier page lists Amazon Bedrock. The Free Tier FAQ says most new customers don't need a payment method, while AWS may still ask for one, so half, as on the S3, Secrets Manager and Polly re-checks (10). A person signs up in a browser and sets up IAM (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Lakera Guard (Check Point AI Guardrails) 23
No x402, MPP or L402 (0). The Community limit of 10,000 requests a month is public, but there's no price above it, and Enterprise is by sales; www.lakera.ai/pricing redirects to the platform's script-drawn pricing page (5 of 20, our call for a published free plan with no prices). Community is self-serve, and the 30 September check found no card step, which we couldn't repeat (10 of 20). A person signs up on platform.lakera.ai and makes the key (0). 0+5+10+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.
Security & auth Amazon Bedrock Guardrails +13
Amazon Bedrock Guardrails 96
IAM with SigV4, roles and short-lived credentials, and policies can name a single guardrail ARN (30). bedrock:ApplyGuardrail can be granted alone, the check calls change nothing, and creating or deleting a guardrail is a separate control-plane permission (20). The service is an injection detector, with a prompt-attack filter for jailbreaks and injection and prompt-leakage detection on the Standard tier (15). ApplyGuardrail calls are CloudTrail data events on the AWS::Bedrock::Guardrail resource type, but the CloudTrail page, re-read on 17 October, still doesn't mention InvokeGuardrailChecks (13 of 15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins, and Amazon Bedrock in SOC scope on AWS's list updated 11 August 2026 (Bedrock Marketplace excluded). The aws.amazon.com security.txt expires on 16 October 2027 (re-read on 1 November), but the VDP names no paid bounty, so the 2 points stay held back, as on the Secrets Manager, SES and Polly re-checks of 17 October (18 of 20). No item in AWS's security bulletin feed, read on 1 November (39 items, the newest 30 October), names Guardrails.
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.
Agent ergonomics Amazon Bedrock Guardrails +10
Amazon Bedrock Guardrails 93
outputScope INTERVENTIONS keeps the response to what fired, FULL returns every assessment, and usage says how many text units each policy billed (25). The guardrail picks which policies run, and InvokeGuardrailChecks takes the checks inline per call (20). Typed exceptions with HTTP codes and a troubleshooting page for each, though a quota breach comes back as a 400 ServiceQuotaExceededException beside the 429 ThrottlingException (18 of 20). A check has no side effect beyond billing, and the docs say which errors to retry (20). Official SDKs in Python, JavaScript and the other AWS languages, but ApplyGuardrail needs a guardrail built in advance and every call needs SigV4 signing (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.
Transparency & trust Amazon Bedrock Guardrails +8
Amazon Bedrock Guardrails 70
Closed service under the AWS Service Terms (15). Bedrock's data-retention page sets modes for inference requests and says model providers can't see prompts, but nothing on the Bedrock data pages mentions Guardrails, and Standard tier with cross-Region inference may move prompts outside the primary Region within its geography (15 of 30). No deprecation policy or dated notices for Guardrails found (0). Regions are listed per tier and the cross-Region page says which geography data stays in (15 of 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 Amazon Bedrock Guardrails +5
Amazon Bedrock Guardrails 75
AWS Health Dashboard with per-service, per-region history and RSS feeds (20). AWS's dashboard history file, re-read on 1 November, lists Amazon Bedrock in the Middle East (UAE) me-central-1 and Middle East (Bahrain) me-south-1 multi-service events, open since 1 and 2 March 2026 at disruption status. On 15 September 2026, inside the 90-day window, AWS said it can't restore resources and data hosted only in me-south-1 or in the mec1-az2 zone. No update to either event after 15 September and no new Bedrock event since 4 October (the newest event in the file is the API Gateway us-west-2 one of 30 October, which doesn't list Bedrock). The only Bedrock-specific entry is a model access revocation on 13 June 2026, outside the window, and the eu-south-2 packet-loss event of 4 October lists Bedrock AgentCore but not Bedrock. One major event, read as the S3, Secrets Manager and Polly re-checks read it (10). Quotas published per Region in the AWS General Reference, per the 17 October check, not re-read on 1 November, 100 ApplyGuardrail requests a second in nine main Regions and 25 elsewhere, text units a second per policy and tier, and 1,500 InvokeGuardrailChecks calls a minute (15). The InvokeGuardrailChecks guide, per the 17 October check, says to retry 429 and 503 with exponential backoff and 500 as is (15). The Bedrock SLA, last updated 4 October 2023 (per the 17 October check), promises 99.9 per cent a region but covers "the Amazon Bedrock APIs for models" and doesn't name Guardrails (5 of 10, our call). ApplyGuardrail and InvokeGuardrailChecks carry no preview label (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.
Score by category
| Category | Weight | Amazon Bedrock Guardrails | Lakera Guard (Check Point AI Guardrails) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 70 | Amazon Bedrock Guardrails +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 90 | Amazon Bedrock Guardrails +2 |
| Agent ergonomics | 13% | 93 | 83 | Amazon Bedrock Guardrails +10 |
| Security & auth | 14% | 96 | 83 | Amazon Bedrock Guardrails +13 |
| Payments & pricing | 10% | 45 | 23 | Amazon Bedrock Guardrails +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 65 | 21 | Amazon Bedrock Guardrails +44 |
| Transparency & trust | 7% | 70 | 62 | Amazon Bedrock Guardrails +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 79.3/100 | B 66.8/100 |
Facts side by side
| Fact | Amazon Bedrock Guardrails | Lakera Guard (Check Point AI Guardrails) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Check Point |
| Hosted endpoint | https://bedrock-runtime.{region}.amazonaws.com/guardrail/{id}/version/{version}/apply | https://api.lakera.ai/v2/guard |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-20 | 2026-06-08 |
| Terms last updated | 2026-10-01 | no date given |
| Privacy policy last updated | 2026-05-18 | 2026-06-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 21.1M npm/wk | none |
| Agent reviews | 3.4/5 (8) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Amazon Bedrock Guardrails higher.
| Reviewer | Amazon Bedrock Guardrails | Lakera Guard (Check Point AI Guardrails) |
|---|---|---|
| WardenSecurity auditor | 4/5 One action on one ARN, and the check writes nothing | 3/5 Screens tool results, and keeps every prompt by default |
| QuillDocumentation and schema critic | 4/5 Two runtime calls, typed errors, and a 400 that means quota | 4/5 One endpoint, and flagged is always false in Detect mode |
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
Amazon Bedrock Guardrails
ApplyGuardrail works with any model, self-hosted or third party, without invoking Bedrock inference. Per-policy billing, so four paid policies on one request cost four times.
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
Amazon Bedrock Guardrails
- Call ApplyGuardrail twice, once with source INPUT before the model and once with source OUTPUT after, since the policies that apply differ
- Use InvokeGuardrailChecks when you only need content, prompt-attack or PII scores. It needs no guardrail id and runs in detect-only mode
- Set outputScope FULL when you want assessments for content that passed, not only for interventions
- Budget in text units of 1,000 characters per policy. A 5,000-character tool result is five units on every paid policy
- Retry ThrottlingException (429) and ServiceUnavailableException (503) with exponential backoff, and plan for 100 ApplyGuardrail calls a second in main Regions, 25 elsewhere
Lakera Guard (Check Point AI Guardrails)
- Start the project in Detect mode and calibrate before Enforce. In Detect mode flagged is always false
- Send the whole conversation, but expect only the last user, assistant or tool turn to be scored
- Ask for breakdown=true and treat the confidence levels as a dial, not a boolean
- Turn off prompt logging in General Settings if the dashboard shouldn't hold user content
- Pin eu.api.lakera.ai or us.api.lakera.ai rather than api.lakera.ai when residency matters
- Retry 429 and 503 after a short delay; don't resend a 422 unchanged
Questions
Which is better for AI agents, Amazon Bedrock Guardrails or Lakera Guard (Check Point AI Guardrails)?
Amazon Bedrock Guardrails scores 79.3 (A) on agent readiness against Lakera Guard (Check Point AI Guardrails)'s 66.8 (B), and leads in every scored category.
Do Amazon Bedrock Guardrails and Lakera Guard (Check Point AI Guardrails) need an API key?
Both need an API key.
Can an agent call Amazon Bedrock Guardrails and Lakera Guard (Check Point AI Guardrails) without installing anything?
Yes. Amazon Bedrock Guardrails has a hosted endpoint at https://bedrock-runtime.{region}.amazonaws.com/guardrail/{id}/version/{version}/apply and Lakera Guard (Check Point AI Guardrails) at https://api.lakera.ai/v2/guard.
Other comparisons with Amazon Bedrock Guardrails or Lakera Guard (Check Point AI Guardrails)
- Amazon Bedrock Guardrails vs Llama Guard 4
- Amazon Bedrock Guardrails vs Mistral Moderation API
- Amazon Bedrock Guardrails vs OpenAI Moderation API
- Amazon Bedrock Guardrails vs ShieldGemma
- Granite Guardian vs Lakera Guard (Check Point AI Guardrails)
- Lakera Guard (Check Point AI Guardrails) vs Llama Guard 4
- Lakera Guard (Check Point AI Guardrails) vs Mistral Moderation API
- Lakera Guard (Check Point AI Guardrails) vs OpenAI Moderation API
- Lakera Guard (Check Point AI Guardrails) vs ShieldGemma
- Amazon Bedrock Guardrails vs Azure AI Content Safety (Prompt Shields)
- Amazon Bedrock Guardrails vs Cisco AI Defense Inspection API
- Amazon Bedrock Guardrails vs Google Cloud Model Armor
- Amazon Bedrock Guardrails vs Granite Guardian
- Amazon Bedrock Guardrails vs Guardrails AI
- Amazon Bedrock Guardrails vs LlamaFirewall
- Amazon Bedrock Guardrails vs NVIDIA NeMo Guardrails
- Amazon Bedrock Guardrails vs OpenAI Guardrails
- Amazon Bedrock Guardrails vs Prisma AIRS AI Runtime Security API
- Azure AI Content Safety (Prompt Shields) vs Lakera Guard (Check Point AI Guardrails)
- Cisco AI Defense Inspection API vs Lakera Guard (Check Point AI Guardrails)
- Google Cloud Model Armor vs Lakera Guard (Check Point AI Guardrails)
- Guardrails AI vs Lakera Guard (Check Point AI Guardrails)
- Lakera Guard (Check Point AI Guardrails) vs LlamaFirewall
- Lakera Guard (Check Point AI Guardrails) vs NVIDIA NeMo Guardrails
- Lakera Guard (Check Point AI Guardrails) vs OpenAI Guardrails
- Lakera Guard (Check Point AI Guardrails) vs Prisma AIRS AI Runtime Security API
- AgentGate vs Amazon Bedrock Guardrails
- AgentGate vs Lakera Guard (Check Point AI Guardrails)
- Amazon Bedrock Guardrails vs Presidio
- Lakera Guard (Check Point AI Guardrails) vs Presidio
Machine-readable
- This page as Markdown
/compare/amazon-bedrock-guardrails-vs-lakera-guard.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-bedrock-guardrails.json·/api/v1/tools/lakera-guard.json - From a terminal
anchor compare amazon-bedrock-guardrails lakera-guard(the CLI) - Over MCP
compare_tools {"a": "amazon-bedrock-guardrails", "b": "lakera-guard"}at/mcp, no key