Match each cloud managed guardrail product to its provider
Drag each answer to line up with its matching prompt
Prompt Shields
Google Cloud
Bedrock Guardrails
Amazon AWS
Model Armor
Microsoft Azure
NeMo Guardrails
Meta
Llama Guard 4 / Prompt Guard 2
OpenAI
Moderation API and safety filters
NVIDIA
Azure ships Prompt Shields, AWS ships Bedrock Guardrails, Google ships Model Armor, NVIDIA ships NeMo Guardrails, Meta ships Llama Guard plus Prompt Guard, OpenAI ships Moderation.
Imagine three big grocery chains all selling their own brand of bleach. Same job, different bottles, slightly different smells. Cloud guardrails are like that. Each big cloud has rebottled the safety layer with its own brand name so they can sell it next to their model hosting. The OSS world has its own brands too, Meta makes the safety-classifier bottles, NVIDIA makes the orchestration bottle, OpenAI runs its own first-party detector behind the API. The job each of them does is the same shape: filter inputs, filter outputs, and refuse policy-violating prompts. The price tags, the latency, and the supported policy categories are what actually differ.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
The cloud-managed guardrail landscape in 2026 is small enough to memorise and just confusing enough that interview candidates routinely cross-attribute the products. Knowing the names and the vendor behind each one is the floor. Knowing the axes along which they actually differ, data residency, customisation, latency, blame surface, is what separates someone who has read a vendor page from someone who has shipped a production safety layer.
This walkthrough names the six vendor lines, explains the structural difference between cloud-managed shields and self-hosted classifiers, and lays out the hybrid pattern most enterprise teams converge on by the end of their first year in production.
Mental model: cloud providers brand their guardrails with cloud-flavoured words (Shields, Guardrails, Armor). Model vendors brand theirs with their model family (NeMo, Llama Guard, Prompt Guard). The pattern holds across every major name.
The six vendor product lines
The hyperscaler trio
The three big cloud providers each ship a managed guardrail product:
- Azure Prompt Shields is Microsoft's offering, part of the broader Azure AI Content Safety service. It targets prompt-injection screening (both direct and indirect) and integrates with Azure OpenAI deployments. The naming hints at scope: 'Shields' suggests the inline protection role.
- AWS Bedrock Guardrails is Amazon's product, layered around any model invoked through Bedrock. It exposes five policy types: content filter, denied topics, sensitive information, contextual grounding, and word filter. The branding follows AWS service-naming convention.
- Google Cloud Model Armor is Google's equivalent, sitting around Gemini 3.1 and Vertex AI model endpoints. Naming is again service-specific.
The OSS and vendor-branded set
- NVIDIA NeMo Guardrails is the orchestration framework, open-source, with the Colang DSL as the rule language. It is not a classifier itself; it calls classifiers (Llama Guard, custom models, regex) as rails.
- Meta Llama Guard 4 is the broad safety classifier with a configurable taxonomy and multimodal coverage. Meta Prompt Guard 2 is the specialised injection/jailbreak detector. Both ship as open-weights models you self-host.
- OpenAI Moderation is the first-party content classifier exposed at the OpenAI platform API. Anthropic ships equivalent first-party filters baked into its API surface, not as a separately purchasable product.
A note on smaller players
The vendor landscape also includes Lakera Guard and Protect AI Rebuff (hosted injection-detection APIs), Guardrails AI (open-source Python SDK with a validator hub), and Patronus AI plus Vijil (safety-evaluation specialists). They sit alongside the big six rather than replacing them.
Situations where this technique stops working.
2–4 min · Everything important, quickly.
Real products, models, and research that use this idea.
- Anthropic's Claude Opus 4.7 is invoked through AWS Bedrock with Bedrock Guardrails as the policy layer at most enterprise customers.
- Microsoft Azure OpenAI deployments using GPT-5.5 ship Prompt Shields enabled by default for direct and indirect injection screening.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you choose between Bedrock Guardrails and self-hosted Llama Guard 4 for a B2B SaaS shipping in three cloud regions?
Bedrock Guardrails wins on operational simplicity and audit trail across the three regions if all three are AWS. Self-hosted wins on customisation and on multi-cloud portability. Most B2B SaaS teams ship Bedrock for default coverage and self-hosted Prompt Guard 2 as a secondary on routes that handle customer PII.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Confusing the cloud-managed shields with each other or thinking Llama Guard is Microsoft's product, Llama Guard ships from Meta and is self-hostable, not a cloud-managed offering.
60 second bullets to scan on the way to the call.
Six vendors and their guardrail product lines
Distinction between cloud-managed shields and self-hosted classifiers
Primary sources. Browse if you want the original framing.
Same topic, related formats. Practice these next.