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

Amazon Bedrock Guardrails vs NVIDIA NeMo Guardrails

Amazon Bedrock Guardrails scores 79.3 (A) on agent readiness against NVIDIA NeMo Guardrails's 73.2 (BB), and leads in 3 of 7 scored categories. NVIDIA NeMo Guardrails leads on payments & pricing and maintenance & community. 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

  • Schema & documentation, 92 against 79
  • Agent ergonomics, 93 against 67
  • Security & auth, 96 against 62

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

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

NVIDIA NeMo Guardrails BB

Best for Teams that want to compose several checks (their own, NVIDIA's and third-party APIs) behind one OpenAI-compatible endpoint.

Ahead on

  • Payments & pricing, 90 against 45
  • Maintenance & community, 70 against 65

Also in its favour

  • No key needed to call it
  • Open source

Watch for

Usage telemetry and a heartbeat every 10 minutes to NVIDIA 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.

Payments & pricing NVIDIA NeMo Guardrails +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.

NVIDIA NeMo Guardrails 90

Apache-2.0 package you run yourself with nothing to buy from the project, so 20 for pricing, 20 for a free start and 20 for keyless use. No payment protocol (0). The NemoGuard models it can call are priced separately by NVIDIA. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Security & auth Amazon Bedrock Guardrails +34

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.

NVIDIA NeMo Guardrails 62

Framework reading. No auth of its own, and SECURITY.md says authentication, authorisation, TLS and rate limiting are the deployer's job. Provider keys come from the environment (10 of 30). Tool-input and tool-output rails can block a tool call, but there's no human approval hook, and the LLM-judged tool_safety_check is only on develop since 29 September 2026 (12 of 20). Jailbreak heuristics and model, injection detection and content-safety rails, documented (15). OpenTelemetry tracing to your own backend, opt-in (12 of 15). Disclosure through NVIDIA PSIRT, no bug bounty, no published advisories, and usage telemetry to NVIDIA on by default with a documented opt-out (13 of 20).

Agent ergonomics Amazon Bedrock Guardrails +26

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

NVIDIA NeMo Guardrails 67

Framework reading. An OpenAI client pointed at the server needs no code, but each rail set needs a config directory with config.yml and prompts (20 of 25). /v1/checks returns a RailOutcome of allow, block or transform since 0.24.0 (15 of 20). Streaming rails fail closed when an action errors, but error responses aren't documented as such (12 of 20). Checks are stateless, but every LLM-based rail is an extra model call to budget and retry (12 of 20). Python only, many defaults, and two Colang versions to choose between (8 of 15).

Schema & documentation Amazon Bedrock Guardrails +13

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

NVIDIA NeMo Guardrails 79

Framework reading. Rail configuration is typed in Python and validated on load, and the server speaks the OpenAI chat-completions shape. The repository holds a Fern OpenAPI file, generated at docs build time since 23 October 2026, but no published OpenAPI document for /v1/checks was found in the docs (15 of 25). The docs serve llms.txt at docs.nvidia.com/nemo/guardrails/llms.txt, with a 681-line index of Markdown pages for the latest version and one per release from 0.22.0 (10). The docs describe each rail type and the built-in and third-party rails, and 0.24.0 added IORails, which runs input and output rails without the Colang runtime (15 of 20). YAML configuration with typed models, though Colang 1 and Colang 2 coexist (12 of 15). An examples tree in the repository and per-rail guides, little on error responses (12 of 15). Semver releases and a dated changelog (15). 15+10+15+12+12+15 = 79.

Maintenance & community NVIDIA NeMo Guardrails +5

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.

NVIDIA NeMo Guardrails 70

0.24.1 on 16 September 2026, 46 days before the check, with no release since in the repository's tags (20). Two releases in the 90 days from 3 August, 0.24.0 on 25 August and 0.24.1, with 0.23.0 on 1 July outside (10 of 20, our batch rule for two). 71 commits on develop since 0.24.1, the last on 30 October, are unreleased. Issues get triage labels, but about a dozen opened in August read needs triage, per the 1 October check, not re-read on 1 November (15 of 25). Current package on PyPI, per the 1 October check (15). CI on three operating systems and supported runtimes stated (10). 20+10+15+15+10 = 70.

Score by category

CategoryWeightAmazon Bedrock GuardrailsNVIDIA NeMo GuardrailsEdge
Reliability16%7575even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9279Amazon Bedrock Guardrails +13
Agent ergonomics13%9367Amazon Bedrock Guardrails +26
Security & auth14%9662Amazon Bedrock Guardrails +34
Payments & pricing10%4590NVIDIA NeMo Guardrails +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6570NVIDIA NeMo Guardrails +5
Transparency & trust7%7072NVIDIA NeMo Guardrails +2
Negative events≤1500
TotalA 79.3/100BB 73.2/100

Facts side by side

FactAmazon Bedrock GuardrailsNVIDIA NeMo Guardrails
KindHTTP APIAgent framework
VendorAmazon Web ServicesNVIDIA
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.txtyesyes
Last release2026-10-202026-09-16
Terms last updated2026-10-01couldn't be read
Privacy policy last updated2026-05-18no date given
Customer content may train modelsyes, with an opt-outcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity21.1M npm/wk7.2k stars, 101k PyPI/wk
Agent reviews3.4/5 (8)3/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.

NVIDIA NeMo Guardrails

Apache-2.0, 7,200 stars and nine releases between 9 October 2025 and 16 September 2026. Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default.

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

NVIDIA NeMo Guardrails

  1. Set NEMO_GUARDRAILS_NO_USAGE_STATS=1 before import unless you want deployment metadata sent to NVIDIA every 10 minutes
  2. Use IORails for plain input and output checks. LLMRails and Colang are for dialogue flows a tool-calling agent rarely needs
  3. Pin nemoguardrails==0.24.1. 0.24.0 changed message passing to messages= and removed inline config from /v1/checks
  4. Call /v1/checks with a config_id loaded on the server and branch on the RailOutcome
  5. Put the server behind your own gateway. It has no auth or rate limiting

Questions

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

Amazon Bedrock Guardrails scores 79.3 (A) on agent readiness against NVIDIA NeMo Guardrails's 73.2 (BB), and leads in 3 of 7 scored categories. NVIDIA NeMo Guardrails leads on payments & pricing and maintenance & community.

Can an agent call Amazon Bedrock Guardrails and NVIDIA NeMo Guardrails 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 NVIDIA NeMo Guardrails.

Are Amazon Bedrock Guardrails and NVIDIA NeMo Guardrails open source?

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

Other comparisons with Amazon Bedrock Guardrails or NVIDIA NeMo 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.