| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| AI security platforms | Security operations | 0% | 35 of 233 | 6% | 16 | accepted challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 3 | 0 | 3 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 0 | 1 |
| Perplexity Sonar | 0 | 1 | 0 | 0 | 1 |
| Grok 4.1 Fast | 0 | 1 | 0 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 1 | 0 | 0 | 1 |
| Kimi K2 | 0 | 1 | 0 | 1 | 2 |
| GLM 4.7 FlashX | 0 | 1 | 0 | 0 | 1 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 1 | 0 | 0 | 1 |
| Muse Glimmer 30B | 0 | 1 | 0 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“Lakera Guard is worth testing on a tight budget; its community tier is limited to 10,000 screening requests per month” GPT-6 Luna · AI security · budget prompt · alternative
“If your risk is users hacking your customer-facing chatbot, look at Lakera Guard or Cisco AI Defense.” Gemini 3.5 Flash · AI security · comparative prompt · alternative
“Gandalf Guard for prompt injection; real-time runtime defense; excels in production OWASP LLM risks.” Grok 4.1 Fast · AI security · comparative prompt · alternative
“Provides runtime defense for LLMs and agents, focusing on prompt injection and model extraction.” GLM 4.7 FlashX · AI security · comparative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Custom pricing, typically enterprise-focused with complex deployment” Kimi K2 · AI security · paraphrase prompt · hard negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 43 of the 48 answers that named Lakera Guard and are not a share of its labels.
123 of the 123 domain citations in answers naming Lakera Guard came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 95 | undated | DLP | ||
| Conference or event | 10 | undated | |||
| Webinar or virtual event | 3 | undated | |||
| Case study | 2 | undated | |||
| Comparison | 2 | undated | |||
| Template or tool | 1 | undated | |||
| Glossary or explainer | 1 | undated |
Every page lakera.ai exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 29, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Lakera Guard's own pages state, read October 5, 2026: lakera.ai, trust.lakera.ai, lakera.ai/customers. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Lakera Guard's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Lakera Guard, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Lakera Guard by email, built from the raw record of the edition. It shows: