Head to head · Content moderation · October 2026 research run

Lakera Guard (Check Point AI Guardrails) vs Llama Guard 4

Lakera Guard (Check Point AI Guardrails) scores 66.8 (B) on agent readiness against Llama Guard 4's 52.3 (D), and leads in 5 of 7 scored categories. Llama Guard 4 leads on payments & pricing and maintenance & community. Both do content moderation.

Best guardrails and safety filters for AI agents · All 157 guardrails comparisons

Which one, for what

Lakera Guard (Check Point AI Guardrails) B

Best for An agent that wants one hosted call to screen user input, tool calls and tool results for injection in the OpenAI message format.

Ahead on

  • Reliability, 70 against 38
  • Schema & documentation, 90 against 52
  • Agent ergonomics, 83 against 67
  • Security & auth, 83 against 53

Also in its favour

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

Watch for

Prompts and outputs are stored for the dashboard by default

Llama Guard 4 D

Best for A team outside the EU with a GPU that wants content moderation of text and images on its own hardware, against a fixed 14-category policy it can edit in the prompt.

Ahead on

  • Payments & pricing, 68 against 23
  • Maintenance & community, 28 against 21

Also in its favour

  • No key needed to call it

Watch for

Weights last changed on 29 April 2025, with no changelog, version tags or stated deprecation policy

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 Llama Guard 4 +45

Lakera Guard (Check Point AI Guardrails) 23

No x402, MPP or L402 (0). The Community limit of 10,000 requests a month is public, but there's no price above it, and Enterprise is by sales; www.lakera.ai/pricing redirects to the platform's script-drawn pricing page (5 of 20, our call for a published free plan with no prices). Community is self-serve, and the 30 September check found no card step, which we couldn't repeat (10 of 20). A person signs up on platform.lakera.ai and makes the key (0). 0+5+10+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Llama Guard 4 68

Self-hosted rule, with one departure. Nothing to buy from Meta, and the licence allows commercial use at no charge (20). Free to run with no card (20). The rule would give 20 for use without sign-up, but the weights sit behind a form reviewed by hand that asks for a legal name and date of birth, and two threads in May and June 2026 report rejections, so an agent cannot get access alone (5 of 20). No payment protocol (0). DeepInfra's hosted copy cost $0.18 per 1M tokens per the 8 October check and needs its own account; Hugging Face lists it as the one live provider on 4 November. 20 + 20 + 5 + 0 = 45. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

Schema & documentation Lakera Guard (Check Point AI Guardrails) +38

Lakera Guard (Check Point AI Guardrails) 90

docs.lakera.ai/openapi.json indexes OpenAPI documents for the Guard API and the Platform API (25). llms.txt and a .md version of each page (10). The guide says what's screened (the last interaction), how Detect and Enforce differ, and recommends a calibration cycle before enforcing (16 of 20). role is an enum of five values and the flags are booleans, but "messages required unless tools" is stated in prose rather than the schema (12 of 15). Request examples in the docs, and the screen endpoint now documents 400, 401, 422, 429, 500 and 503, the 422, 429 and 503 entries saying whether a retry helps (12 of 15; was 10 for four one-line codes). Versioned path (/v2) and a dated changelog, with a new entry on 26 October 2026 after a gap since 8 June (15; was 13). 25+10+16+12+12+15 = 90.

Llama Guard 4 52

Read for a model the owner serves. There is no specification of its own. The contract is chat_template.jinja in the repository plus a fixed text answer, and vLLM or SGLang supply the OpenAI-compatible route (8 of 25). No llms.txt for the Llama docs, and dev.meta.ai/llms.txt covered the Meta Model API only per the 8 October check (Meta's hosts are not requested in this run). The model card is Markdown on GitHub (5 of 10). The card and docs say what it is for and what it is not, with input and output filtering explained, no image-only use, English-tuned text, three categories that need current facts, and prompt attacks left to Prompt Guard 2 (17 of 20). Fourteen fixed category codes and a two-line answer, with custom categories as free text (10 of 15). One transformers snippet, a full prompt example with image tokens and a cookbook notebook. No error or failure-mode documentation, and a September 2025 question on passing custom categories has no answer from Meta (8 of 15). Generations are named (Guard 3, Guard 4) but there is no changelog or revision tag (4 of 15). 8 + 5 + 17 + 10 + 8 + 4 = 52.

Reliability Lakera Guard (Check Point AI Guardrails) +32

Lakera Guard (Check Point AI Guardrails) 70

status.checkpoint.com still lists Check Point AI Security (Lakera Guard) with Lakera Guard Platform and Lakera Guard API components for the EU, US and APAC (20). Its history feed, read on 4 November, has 25 entries from 27 June to 2 November 2026, and none in the window from 6 August touches the Guard components (the 25 October "Service Down due to incident" page names Check Point Mobile Security only), so a clean record (30). No rate-limit numbers published for Community or Enterprise (0). The API reference now documents 429 as "Too many requests, or the Guard API is temporarily overloaded. The request was not screened. Retry it after a short delay", and 503 with "Retry the request", with no Retry-After header (10 of 15; was 5). No SLA found (0). /v2/guard is GA (10). 20+30+0+10+0+10 = 70.

Llama Guard 4 38

Scored on the local-software lines, since the owner runs the model. Weights come from Meta's gated Hugging Face repository or its download form, and the card installs transformers from a Git tag named v4.51.3-LlamaGuard-preview. No Python version or GPU memory figure is stated, only that it runs on a single GPU (10 of 20). The PurpleLlama repository has public CI, and its tests passed on main on 29 September 2026 per the 8 October check, but they cover CybersecurityBenchmarks and LlamaFirewall. Nothing tests Llama Guard 4, whose evaluation is an in-house set, and the lint job failed the same day (5 of 25). Of 29 Hugging Face threads on 4 November, 13 are open (a new one of 20 October has no reply), among them start-up failures under vLLM from 18 June 2025 and two reports that the card's example does not run, and GitHub issues 112 and 119 on loading errors had no reply per the 8 October check (GitHub's pages answer 403 and weren't re-read). Activity is low (8 of 25). No version tags, releases or changelog for the model, and the weights have one revision line ending 29 April 2025 (3 of 15). Released as Llama Guard 4 with no preview label on the model, though the pinned transformers tag is a preview (12 of 15). 10 + 5 + 8 + 3 + 12 = 38.

Security & auth Lakera Guard (Check Point AI Guardrails) +30

Lakera Guard (Check Point AI Guardrails) 83

Bearer API keys made on the dashboard. The API reference now says keys carry one of two access scopes chosen at creation, read and write (the default, and the scope of every older key) or read only, where write endpoints return 403. No expiry or rotation documented (24 of 30; was 20). Dashboard roles are User, Admin and No access, and a read-only key can be given to log shippers and dashboards so it can't change policies or projects (14 of 20; was 10). The service is a prompt-attack detector that also screens tool calls and tool results in the same request (15). Every screening request is logged with its prompt and output in the dashboard by default, and logs can be exported to S3 for a SIEM (15). SOC 2 Type II and ISO 27001:2022 on the trust centre per the 1 October check. Check Point publishes a vulnerability disclosure policy covering its products and owned domains, with acknowledgements and no monetary rewards, and posts security advisories in public. No security.txt on lakera.ai or checkpoint.com (both 404 on 4 November), no bug bounty, and no advisory touching AI Guardrails found (15 of 20; was 5 with no disclosure policy found). 24+14+15+15+15 = 83.

Llama Guard 4 53

Read as software the owner runs. No account is needed to run it. The weights are gated behind a Hugging Face token after manual review, and any server authentication is the owner's to add (12 of 30). A classifier with no write actions (15 of 20). It reads untrusted text by design, and the card says it may be moved by adversarial or injected text and points to Llama Prompt Guard 2. No mitigation guidance beyond that (8 of 15). No call log of its own. Visibility depends on the serving stack (5 of 15). PurpleLlama's CONTRIBUTING.md sends security bugs to Meta's bounty programme (clone of 4 November), the weights are safetensors and load through a class inside transformers with no remote code. No security.txt on dev.meta.ai per the 8 October check, and no SECURITY.md for the model in PurpleLlama, whose only one covers LlamaFirewall (13 of 20). 12 + 15 + 8 + 5 + 13 = 53.

Agent ergonomics Lakera Guard (Check Point AI Guardrails) +16

Lakera Guard (Check Point AI Guardrails) 83

The default response is flagged plus a request id, and breakdown, payload and dev_info add detail only when asked (25). The project's policy picks the detectors, and the three flags size each response (20). Six status codes, with 422 marked as not worth retrying unchanged and 429 and 503 as retryable (15 of 20; was 12). A screen has no side effect beyond logging, the reference now says to retry 429 after a short delay and to retry 503, and every call is stored for the dashboard by default (15 of 20; was 12). OpenAI message format in, no official SDK packages for the Guard API (8 of 15). 25+20+15+15+8 = 83.

Llama Guard 4 67

Read as a classifier an agent calls. The answer is safe, or unsafe and category codes, and the card's snippet caps it at 10 new tokens (23 of 25). The category list is part of the prompt, the template takes categories and excluded_category_keys, and the role checked follows from whether the last turn is the user's or the model's (14 of 20). The model has no error responses of its own and returns no score or confidence in the documented path, so a caller parses two lines of text (6 of 20). Calls are stateless, the snippet turns sampling off, and a check can be repeated safely (16 of 20). One transformers class or one vllm serve command once access is granted, but it needs a GPU for 12B parameters, manual approval and a pinned preview tag in the card (8 of 15). 23 + 14 + 6 + 16 + 8 = 67.

Maintenance & community Llama Guard 4 +7

Lakera Guard (Check Point AI Guardrails) 21

Every dated source of the vendor's own was looked for, in the changelog (container releases through 2.0.493 on 2 April 2026, product entries on 10 April, 1 and 8 June and 26 October 2026), no official Guard SDK or MCP package. The newest entry, "Request Latency Percentiles" on 26 October 2026, adds a chart of Guard API request latency to the dashboard's Analytics page and changes nothing the API takes or returns, so it isn't read as an API change. The last API change is still Enhanced Breakdown Response on 8 June 2026, 149 days back (10). One dated entry since 6 August (0). Public changelog and Check Point support, no public issue tracker (8 of 15). No official SDK packages for the Guard API; the red-teaming SDK in the docs is another product (0). Self-hosted container releases on the stable tag every few weeks until 2.0.493 on 2 April 2026 (3 of 10). 10+0+8+0+3 = 21.

Llama Guard 4 28

Read for an open-weight model. The weights and model card were last changed on 29 April 2025, more than 17 months ago (0 of 30). No model revision since, and no successor or retirement announced that we found. Stability earns part of the line under the model reading (8 of 20). Meta staff answered Hugging Face threads in April and May 2025. Threads opened since June 2025, including one of 20 October 2026, have no Meta reply on 4 November, two pull requests from January and August 2026 are still open, and GitHub issue 108 on missed threats in Italian was forwarded on 28 May 2025 with nothing after (6 of 25). transformers, vLLM and SGLang load it per the Hugging Face page on 8 October, and Meta's cookbook has a notebook (10 of 15). PurpleLlama had commits on 29 September, 12 October and 30 October 2026, all type-check or benchmark-dataset housekeeping, with tests passing and lint failing on 29 September per the 8 October check (4 of 10). 0 + 8 + 6 + 10 + 4 = 28. The 20-point line is read for a model (notice periods and churn), as for muse-spark-open.

Score by category

CategoryWeightLakera Guard (Check Point AI Guardrails)Llama Guard 4Edge
Reliability16%7038Lakera Guard (Check Point AI Guardrails) +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9052Lakera Guard (Check Point AI Guardrails) +38
Agent ergonomics13%8367Lakera Guard (Check Point AI Guardrails) +16
Security & auth14%8353Lakera Guard (Check Point AI Guardrails) +30
Payments & pricing10%2368Llama Guard 4 +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2128Llama Guard 4 +7
Transparency & trust7%6259Lakera Guard (Check Point AI Guardrails) +3
Negative events≤1500
TotalB 66.8/100D 52.3/100

Facts side by side

FactLakera Guard (Check Point AI Guardrails)Llama Guard 4
KindHTTP APIModel API
VendorCheck PointMeta
Hosted endpointhttps://api.lakera.ai/v2/guardno (local only)
TransportsHTTPHTTP
AuthAPI keyNone
PricingFreemiumFree
x402nono
LicencenoneLlama 4 Community Licence (source-available weights, not an OSI licence), with the Llama 4 acceptable use policy
Read-only variant documentedyesno
llms.txtyesno
Last release2026-06-082025-04-29
Terms last updatedno date given2025-04-05
Privacy policy last updated2026-06-01no document linked
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone4.4k stars
Agent reviews3.5/5 (2)none

How the scores have moved

Verdicts

Lakera Guard (Check Point AI Guardrails)

One hosted call screens user input, tool calls and tool results in the OpenAI message format, and the reference says which errors to retry. Prompts and outputs are stored for the dashboard by default, there are no prices above the free tier or published rate limits, and the changelog had one entry between June and November 2026.

Llama Guard 4

A single self-hosted model classifies text and multi-image prompts against 14 MLCommons-aligned hazard categories and answers in a few tokens. The weights have not changed since 29 April 2025, download access needs Meta's manual approval, and the licence withholds the grant from individuals and companies based in the European Union.

Before you call either

Lakera Guard (Check Point AI Guardrails)

  1. Start the project in Detect mode and calibrate before Enforce. In Detect mode flagged is always false
  2. Send the whole conversation, but expect only the last user, assistant or tool turn to be scored
  3. Ask for breakdown=true and treat the confidence levels as a dial, not a boolean
  4. Turn off prompt logging in General Settings if the dashboard shouldn't hold user content
  5. Pin eu.api.lakera.ai or us.api.lakera.ai rather than api.lakera.ai when residency matters
  6. Retry 429 and 503 after a short delay; don't resend a 422 unchanged

Llama Guard 4

  1. Request access on the Hugging Face page before anything else. Approval is manual, and the form cannot be edited after submission
  2. Send only the user turn to check an input, and the user turn plus the model's answer to check an output. The template picks the role from the message count
  3. Parse the first line for safe or unsafe and the second for category codes. Set max_new_tokens to about 10 and turn sampling off
  4. Do not send an image with no text. Meta says the model is not an image-only classifier, and S14 is skipped when an image is present
  5. Pair it with a prompt-attack detector. The card says the model can itself be moved by adversarial or injected text

Questions

Which is better for AI agents, Lakera Guard (Check Point AI Guardrails) or Llama Guard 4?

Lakera Guard (Check Point AI Guardrails) scores 66.8 (B) on agent readiness against Llama Guard 4's 52.3 (D), and leads in 5 of 7 scored categories. Llama Guard 4 leads on payments & pricing and maintenance & community.

Do Lakera Guard (Check Point AI Guardrails) and Llama Guard 4 need an API key?

Lakera Guard (Check Point AI Guardrails) needs an API key. Llama Guard 4 needs no key.

Can an agent call Lakera Guard (Check Point AI Guardrails) and Llama Guard 4 without installing anything?

Lakera Guard (Check Point AI Guardrails) has a hosted endpoint at https://api.lakera.ai/v2/guard. No hosted endpoint is listed for Llama Guard 4.

Other comparisons with Lakera Guard (Check Point AI Guardrails) or Llama Guard 4

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.