Amazon Bedrock Guardrails vs NVIDIA NeMo Guardrails

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, and no free tier.

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.

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, but treat a 400 ServiceQuotaExceededException as a quota to raise

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