LLM firewalls & guardrails

Qwen3Guard: open multilingual safety moderation model family

Qwen3Guard is an open multilingual safety moderation model family from Alibaba Cloud. It is open source under the Apache-2.0 license and is offered as: Self-hosted, Library.

  • Last reviewed
Open sourceApache-2.0 Layer 6: Runtime guardrails

Best for

  • Teams that need an open multilingual moderation model they can host, including one that scores tokens while a response is still being generated
  • Teams that want published per-benchmark F1 scores, in English, Chinese and multilingual sets, before choosing a guard model

Consider instead if

  • You want models that also check groundedness and function-calling errors, with a clear Apache-2.0 repository license. See Granite Guardian.
  • Your categories do not fit a fixed taxonomy and you would rather write the policy yourself, at the cost of running a 20B or 120B reasoning model. See gpt-oss-safeguard.

What Qwen3Guard does

Qwen3Guard is the Qwen team's open moderation model series from Alibaba Cloud, in 0.6B, 4B and 8B sizes. It works from a fixed taxonomy: each prompt or response gets Safe, Controversial or Unsafe plus a category, and you decide whether Controversial counts as unsafe, which the technical report calls strict and loose modes. The Stream variant labels tokens while a reply is still being generated, so a harmful answer can be flagged before it finishes. Response checks also report whether the model refused. The report's own limits section says adversarial prompts may get past it. If your categories do not fit its taxonomy, gpt-oss-safeguard takes a written policy instead. Hugging Face cards state Apache-2.0; the GitHub repository states no license. You run it on your own hardware.

This summary is our own wording of the sourced facts on this page.

Key facts

Each value links to the page that states it, with the date we checked it.

API reference
Not documented in the sources we checked
Security page
Not documented in the sources we checked
Attestations or disclosure
Not documented in the sources we checked

Capabilities

As documented by the vendor or project. The tag is our label from a controlled vocabulary.

Integrations

Where Qwen3Guard fits in our AI security layers

Our analysis

Our editorial model, not a standard. The primary layer follows the category, except for tools whose main documented job is detection and response; other layers rest on a capability the sources document. How the model works.

AI security layers that Qwen3Guard covers, with the role, how each applies and what it rests on
LayerRoleHow it appliesBased on
L6 Runtime Runtime guardrails Primary Screen what goes into and comes out of a model in live traffic, and limit abuse of the model endpoint. Follows its category, LLM firewalls & guardrails

OWASP LLM Top 10 mapping

Our analysis

The risk list is OWASP's (Top 10 for LLM Applications, 2025). The mapping is our analysis, and each row rests on a capability the sources document.

OWASP LLM risks mapped to Qwen3Guard, with the capabilities each mapping rests on
RiskHow it appliesBased on
LLM01 Prompt Injection Jailbreak is a built-in input category. Includes Jailbreak as an input-only safety category for prompts

Alternatives and related tools

More in LLM firewalls & guardrails, ranked within the category by Coverage Score.

Open sourceApache-2.0
  • Library
  • Self-hosted
  • API

Adds programmable input, dialog, retrieval, execution and output rails to LLM applications.

Best for: Teams that want to script rules for one LLM application in Python and run them in their own infrastructure

Coverage Score 76 out of 100
  • LLM01 Prompt Injection
  • LLM02 Sensitive Information Disclosure
  • LLM05 Improper Output Handling
  • LLM06 Excessive Agency

Reviewed

Portkey AI Gateway

Palo Alto Networks (Portkey)

Open sourceMIT Freemium Now Prisma AIRS AI Gateway
  • SaaS
  • Self-hosted
  • API

Routes LLM traffic through one gateway API and runs input and output guardrail checks on each request.

Best for: Teams that want a single gateway for several LLM providers with guardrail checks, available as open source or as a hosted service

Coverage Score 69 out of 100
  • LLM01 Prompt Injection
  • LLM02 Sensitive Information Disclosure
  • LLM05 Improper Output Handling
  • LLM09 Misinformation

Reviewed

Open sourceApache-2.0
  • Self-hosted
  • SaaS
  • API

Routes LLM traffic through Kong with prompt guards, PII sanitization, spend limits and observability.

Best for: Teams that already run Kong as an API gateway and want LLM routing and prompt controls on the same data plane

Coverage Score 65 out of 100
  • LLM01 Prompt Injection
  • LLM02 Sensitive Information Disclosure
  • LLM10 Unbounded Consumption

Reviewed

Qwen3Guard FAQ

What license does Qwen3Guard use?

The Hugging Face cards for the 8B Gen and Stream models state Apache-2.0. The GitHub repository has no LICENSE file and its README states no license, so check the model card for the size you use.

What is the difference between Gen and Stream?

Gen classifies a whole prompt or response. Stream adds a token-level head that scores text as it is generated, and it works best with models that share the Qwen3 tokenizer. In the technical report, Stream-8B averages 88.3 F1 on English prompts against 90.0 for Gen-8B.

What are strict and loose modes?

Every label is Safe, Controversial or Unsafe with a category such as violent, PII, self-harm, politically sensitive or copyright; Jailbreak applies to prompts only. Strict mode treats Controversial as unsafe and loose mode treats it as safe. On ToxicChat the 8B Gen model scores 68.9 F1 strict and 82.8 loose.

Can I compare its scores with gpt-oss-safeguard?

Only loosely. Both vendors report F1 on ToxicChat and the OpenAI Moderation set, but Qwen3Guard is scored against its own fixed taxonomy while gpt-oss-safeguard is given policies OpenAI wrote, and each figure is the vendor's own.

Key facts you can cite

We have no commercial relationship with Alibaba Cloud.

Sources & last reviewed

Last reviewed . We compile from the vendors' own public pages and repositories and we do not run the products. Source links open in a new tab. Found a mistake? Report a correction.