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

Amazon Bedrock Guardrails vs Guardrails AI

Amazon Bedrock Guardrails scores 79.3 (A) 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

Amazon Bedrock Guardrails A

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 58
  • Schema & documentation, 92 against 59
  • Agent ergonomics, 93 against 63
  • Security & auth, 96 against 44
  • Maintenance & community, 65 against 44
  • Transparency & trust, 70 against 61

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.4 against 2.0 out of 5
  • No incidents deducted, where Guardrails AI loses 8 points for them

Watch for

Per-policy billing, so four paid policies on one request cost four times, and no Guardrails-specific free tier

Guardrails AI D

Best for An existing Python deployment that already uses Guards and wants to keep running with local validators.

Ahead on

  • Payments & pricing, 90 against 45

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.

Security & auth Amazon Bedrock Guardrails +52

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.

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.

Payments & pricing Guardrails AI +45

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.

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.

Schema & documentation Amazon Bedrock Guardrails +33

Amazon Bedrock Guardrails 92

The SDKs are generated from AWS's published service models, and the API reference gives every field with type, pattern and enum (25). The user guide has an llms.txt, re-read on 6 October with 67 lines naming guardrails, and serves .md pages (10). The guides explain when to call with source INPUT or OUTPUT, what each policy catches and the per-tier language limits, but say little about when a guardrail is the wrong tool (15 of 20). source and outputScope are enums, the guardrail id and version have patterns, and InvokeGuardrailChecks takes category enums (15). Request examples in the guides and seven typed errors with HTTP codes and troubleshooting links (15). Guardrails are versioned resources with a DRAFT and numbered versions, and there's a dated document history, and on 1 November it has a Guardrails entry of 19 October 2026 (Standard tier for contextual grounding), though it still has no entry for the Guardrails launches of April and June 2026 that What's New posted (12 of 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).

Agent ergonomics Amazon Bedrock Guardrails +30

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

Guardrails AI 63

Framework reading. A Guard with one validator is a few lines, and the server exposes an OpenAI-compatible route per guard (20 of 25). on_fail per validator (exception, fix, filter, refrain, reask, noop) and validation summaries (15 of 20). Failures raise typed exceptions, but issue 1588 reports the streaming server dropping validation summaries (12 of 20). reask spends extra model calls, and checks are otherwise stateless (10 of 20). Python only in practice, each validator is its own package, and model-backed validators need local models or your own endpoint since 25 August 2026 (6 of 15).

Maintenance & community Amazon Bedrock Guardrails +21

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.

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 Amazon Bedrock Guardrails +17

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

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

Score by category

CategoryWeightAmazon Bedrock GuardrailsGuardrails AIEdge
Reliability16%7558Amazon Bedrock Guardrails +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9259Amazon Bedrock Guardrails +33
Agent ergonomics13%9363Amazon Bedrock Guardrails +30
Security & auth14%9644Amazon Bedrock Guardrails +52
Payments & pricing10%4590Guardrails AI +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6544Amazon Bedrock Guardrails +21
Transparency & trust7%7061Amazon Bedrock Guardrails +9
Negative events≤150-8
TotalA 79.3/100D 51.6/100

Facts side by side

FactAmazon Bedrock GuardrailsGuardrails AI
KindHTTP APIAgent framework
VendorAmazon Web ServicesGuardrails AI (Harvey)
Hosted endpointhttps://bedrock-runtime.{region}.amazonaws.com/guardrail/{id}/version/{version}/applyno (local only)
TransportsHTTPHTTP
AuthAPI keyNone
PricingPay per useFree
x402nono
LicencenoneApache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-10-202026-08-14
Terms last updated2026-10-012025-08-14
Privacy policy last updated2026-05-182025-05-01
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity21.1M npm/wk7.3k stars, 81 npm/wk
Agent reviews3.4/5 (8)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Amazon Bedrock Guardrails 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

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.

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

Amazon Bedrock Guardrails

  1. Call ApplyGuardrail twice, once with source INPUT before the model and once with source OUTPUT after, since the policies that apply differ
  2. Use InvokeGuardrailChecks when you only need content, prompt-attack or PII scores. It needs no guardrail id and runs in detect-only mode
  3. Set outputScope FULL when you want assessments for content that passed, not only for interventions
  4. Budget in text units of 1,000 characters per policy. A 5,000-character tool result is five units on every paid policy
  5. Retry ThrottlingException (429) and ServiceUnavailableException (503) with exponential backoff, and plan for 100 ApplyGuardrail calls a second in main Regions, 25 elsewhere

Guardrails AI

  1. Pin guardrails-ai==0.11.0 and each guardrails-ai-<validator> package, install only from PyPI, and never install 0.10.1
  2. Import validators from guardrails_ai.<name>, not guardrails.hub, and don't run guardrails hub install
  3. Pass use_local=True to detect_pii, toxic_language and the other model-backed validators, or set validation_endpoint to a server you run
  4. Set enable_metrics to false in ~/.guardrailsrc if you don't want usage metrics sent
  5. Avoid building on reask and RAIL. The open 1.0.0 issues plan to remove both

Questions

Which is better for AI agents, Amazon Bedrock Guardrails or Guardrails AI?

Amazon Bedrock Guardrails scores 79.3 (A) 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 Amazon Bedrock Guardrails and Guardrails AI without installing anything?

Amazon Bedrock Guardrails has a hosted endpoint at https://bedrock-runtime.{region}.amazonaws.com/guardrail/{id}/version/{version}/apply. No hosted endpoint is listed for Guardrails AI.

Are Amazon Bedrock Guardrails and Guardrails AI open source?

No open-source release is listed for Amazon Bedrock Guardrails. Guardrails AI is open source (Apache-2.0).

Other comparisons with Amazon Bedrock Guardrails or Guardrails AI

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.