Back to vendors
L

Lakera

Also known as: Lakera Guard

Visit site
Entry priceFree to start · plan prices not readable (client-rendered page) · enterprise via salesFull pricing detail

AI security platform, now owned by Check Point, that screens prompts, responses and agent conversations at runtime against configurable guardrails and red teams the customer's models and agents with scored attacks that can gate releases in CI/CD.

Lakera, now owned by Check Point, sells two AI security products. AI Guardrails (formerly Lakera Guard) screens AI traffic at runtime, and AI Red Teaming attacks a customer's models and agents before and after launch. Check Point announced the acquisition in September 2025. The lakera.ai site and its free sign-up still carry the Lakera name, while the documentation now presents the products as Check Point's.

AI Guardrails sits beside an application's models and agents. The application sends prompts, responses, retrieved content and agent conversations to the Guard API, which checks them against the guardrails in a project's policy, such as prompt defense, content moderation, data leakage prevention, malicious links, agent behavior defense, audio defense, custom guardrails and allow and deny lists.

The dashboard logs each screening request with its content and results, admins control logging, retention and SIEM export, and processing can be pinned to US, EU or Singapore endpoints or self-hosted on Kubernetes, Docker or air-gapped infrastructure. AI Red Teaming runs attack objectives against a target model or agent, scores each result, and can gate releases in CI/CD through its SDK.

Lakera fits security teams protecting customer-facing AI applications and agents, and teams that want to test those systems before shipping. It is a security layer, not an agent builder. It does not run workflows, ground agents in knowledge, give them memory or connect them to business systems.

Vendor details

Canonical URL

https://www.lakera.ai

Category

Agent infrastructure

Subcategory

AI security and red teaming

Funding status

Acquired by Check Point Software Technologies (NASDAQ: CHKP), in a deal announced in September 2025.

Company status

acquired

Use cases & customers

Primary use cases

LLM and agent runtime securityprompt injection defensedata leakage preventionAI red teamingGenAI guardrails

Target customers

enterprisesecurity teams

Deployment options

SaaSself-hostedon-prem

Integrations

Applications call the Guard API alongside their own models to screen prompts, responses, retrieved content and agent conversations, choosing a processing region by endpoint. AI Red Teaming reaches a customer's model or agent through built-in model connectors or a custom API wrapper and runs in CI/CD through its SDK. Agent platforms connect for discovery and risk assessment, and Enterprise logs export to SIEMs.

In practice

Your customer-facing chatbot can be tricked into leaking system prompts or PII. You send its traffic to the Guard API with a policy that blocks prompt injection and data leakage, and every screening lands in the dashboard log.

Before launching an agent with tool access, you need to know how it can be exploited. AI Red Teaming runs scored attacks against it, and a CI/CD gate blocks the release if any attack succeeds.

Your data must stay in the EU. You send screening requests to the EU endpoint and keep logs in the EU region, or self-host AI Guardrails in your own cluster.

Agentic Index coverage score

7.0 / 14 capabilities · 50%

Integrations & Tool Calling Partial

Agent platforms connect to Lakera so it can discover agents and assess their risk, and the Guard API screens their traffic. For red teaming, Lakera reaches customer agents through custom API wrappers, and it exports logs to SIEMs. All of these connections bring traffic in for screening and testing. No connector lets an agent take authenticated action in an outside system through Lakera.

SourceLakera (Check Point), docs.lakera.ai llms.txt (connecting agent platforms, integration guide, Red custom API formats)read 2026-09-25

Workflow Orchestration Not documented

The customer's agents run in their own frameworks, which own the steps and handoffs. Lakera screens and tests those agents without running their work. Red team scans are attack runs against a target, not multi step agent work the customer builds. Lakera has no workflow model of its own.

SourceLakera (Check Point), docs.lakera.ai llms.txtread 2026-09-25

Knowledge Grounding & RAG Not documented

Retrieved documents are screened for threats, but Lakera does not index the customer's documents for an agent to ground its answers on. It keeps no retrieval structure over the customer's corpus.

SourceLakera (Check Point), docs.lakera.ai llms.txtread 2026-09-25

Human Oversight & Guardrails Full

AI Guardrails screens prompts, responses and agent conversations inline against guardrails the customer sets in policies for each project. The guardrails cover prompt defense, content moderation, data leakage prevention, malicious link detection, agent behavior defense and audio defense. Custom guardrails and allow and deny lists sit alongside them, and the policies come with a linter and a health check. A guardrail stops an input or output outright. Lakera names no step where a person approves an action.

SourceLakera (Check Point), docs.lakera.ai llms.txt (defenses, policies, projects, Guard API, policies linter)read 2026-09-25

Security, Identity & Governance Full

Enterprise plans get organization SSO, role based access control and organization settings that only admins can change. AI Red Teaming adds two layers of roles, organization roles (admin, member) and folder roles (viewer, member, admin), with a table of what each can do. It also has API keys scoped to a folder, which members create and admins revoke. Admins can switch prompt logging and data retention on or off, and PII is masked before logging.

Lakera names no attestation. Its security address, lakera.ai/security, now redirects to Check Point's AI security page, which names no certification, and Lakera links no trust center.

SourceLakera (Check Point), docs.lakera.ai/docs/platform.md and /docs/red/folder-roles.md, and lakera.ai/security; docs.lakera.ai/docs/platformread 2026-09-25

Observability & Auditability Full

Every screening request is logged on the AI Guardrails dashboard with the exact content screened, including prompts, responses and agent conversations with their roles. Each entry also shows the checks run, the project mode and the detection results.

A Threats view and analytics by project and time range sit on top, and the Platform API returns logs and analytics. Admins control prompt logging and data retention, and Enterprise customers export logs to a SIEM. AI Red Teaming keeps a separate audit trail through its management API. The record holds the agent's own traffic as well as security events.

SourceLakera (Check Point), docs.lakera.ai/docs/platform.md and llms.txt (logs, analytics, Red audit trail, screening agent conversations); docs.lakera.ai/docs/platformread 2026-09-25

Memory & State Persistence Not documented

Screening logs and red team target profiles describe the customer's agents. The agents never read them back as context for a decision. Lakera names no memory layer.

SourceLakera (Check Point), docs.lakera.ai llms.txtread 2026-09-25

Deployment & Data Residency Full

Customers pick where screening runs by choosing an endpoint. The choices are a US endpoint across several regions, US East, US West, EU Ireland or Asia Singapore. Customers also set where logs are stored when the organization is created, with the EU as the default. AI Guardrails can be self hosted on premises or in a private cloud, through a Helm chart for any Kubernetes cluster, plain Docker or a fully air gapped install.

SourceLakera (Check Point), docs.lakera.ai/docs/data-regions.md and /docs/selfhosting.md; docs.lakera.ai/docs/data-regionsread 2026-09-25

Prebuilt Agents, Templates & Packs Partial

Prebuilt detectors for prompt defense, content moderation, data leakage prevention, malicious links, agent behavior and audio are ready for the customer to assemble into policies. Evaluation datasets support proof of value testing. The customer puts these libraries together, and Lakera offers no packaged agents or workflows to adopt as working units.

SourceLakera (Check Point), docs.lakera.ai llms.txt (defenses, datasets)read 2026-09-25

Triggers & Channel Coverage Not documented

The Guard API runs a screening when the customer's code calls it. Red team scans start on demand or from the customer's own CI/CD pipeline. Lakera does not start agents, and no schedule, webhook or event of its own starts work.

SourceLakera (Check Point), docs.lakera.ai/docs/red/sdk-how-tos/run-scans-in-ci-cd.md and llms.txt; docs.lakera.ai/docs/red/sdk-how-tos/run-scans-in-ci-cdread 2026-09-25

Model Flexibility & Routing Not documented

Screening runs through Lakera's own detection models. The customer's model calls are not proxied or routed, since the application calls the Guard API alongside whatever model it already uses. Red Teaming targets are the customer's models under test, not a choice of models inside Lakera. No model or provider for Lakera's own AI can be selected.

SourceLakera (Check Point), docs.lakera.ai llms.txt (integration guide, Guard API, Red targets)read 2026-09-25

APIs, SDKs & MCP Extensibility Full

The platform has a public API with an OpenAPI 3.1 specification. The Guard API screens content and returns detailed results, and it also lints policies and checks their health. The Platform API manages policies and projects end to end and returns logs and analytics. AI Red Teaming adds a versioned SDK and a management API for folders, members and API keys, along with the audit trail. The MCP server on docs.lakera.ai serves the documentation, not the product.

SourceLakera (Check Point), docs.lakera.ai llms.txt (API docs, OpenAPI spec, Red SDK and management API)read 2026-09-25

Testing, Debugging & Optimization Full

AI Red Teaming tests the customer's own models and agents. Targets connect to a model or a custom agent API, and scans run attack objectives against them. Each result carries an attack success score from 0 to 5, an indicator and an explanation, with a pass or fail verdict. A CI/CD gate script runs a scan on each release and fails closed. It blocks on failed, errored or unscored results, and customers can set their own pass and fail criteria. Tool tracing covers agent tool calls during scans. Testing AI systems is Lakera's core business.

SourceLakera (Check Point), docs.lakera.ai/docs/red/sdk-how-tos/run-scans-in-ci-cd.md and llms.txt (red quickstart, interpreting results, trace agent tools); docs.lakera.ai/docs/red/sdk-how-tos/run-scans-in-ci-cdread 2026-09-25

Browser & Computer Use Not documented

The product screens and tests AI traffic and does not operate a browser or a computer.

SourceLakera (Check Point), docs.lakera.ai llms.txt and lakera.airead 2026-09-25

The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded

Product updates

·Observability / auditabilityVerified

Version 0.11.0 of the AI Red Teaming SDK adds a tool response poisoning strategy for testing indirect prompt injection. A benign request leads the agent to call a tool, and Red plants malicious content in the tool result to see whether the agent acts on it. The release also renames setConversationId to setSessionId, a breaking change.

Bears on: Security / enterprise

View source
View all Lakera updates →Tracked since Oct 2026 · Verified from public vendor sources

Pricing

Free to start · plan prices not readable (client-rendered page) · enterprise via sales

not readable; the pricing page renders client side

Free tier

Included quota

Not public. Lakera Guard (runtime protection) and Lakera Red (red teaming) are licensed through enterprise agreements, increasingly via Check Point Infinity, where AI security can be added to existing deployments.

What is public

A free sign-up path and the product structure (AI Guardrails and AI Red Teaming) are public; prices were not readable.

Billing mechanics

A free self-serve sign-up exists; paid plan structure is on a client-rendered pricing page, and enterprise licensing runs through sales, including through Check Point.

Cost watchouts

Runtime screening scales with AI traffic, and self-hosting AI Guardrails runs on the customer's own Kubernetes or Docker infrastructure, with GPU acceleration supported.

Variable cost rationale

As a runtime API screening every prompt and response, cost typically scales with AI traffic volume, but exact metering and rates are set in enterprise agreements and not public.

Additional watchouts

Documentation, support and the security page now carry Check Point branding, so enterprise contracts may run through Check Point.

Overage / add-ons

Not publicly disclosed; commercial terms are set through enterprise sales.

Sales call required

Yes, required for paid access

Free / trial

lakera.ai offers "Start for free" sign-up at platform.lakera.ai; the free plan's limits were not readable

Lowest paid plan

Not public; sold through enterprise sales and the Check Point Infinity platform

Commercial notes

Now part of Check Point Software. Sold to Fortune 500 enterprises through the Check Point go to market, with the runtime API offering near immediate time to protect. Gandalf serves as a free, public on ramp and intelligence source.

Key ambiguities

platform.lakera.ai/pricing renders client side and returned only a shell, so whether paid plans carry published prices is unknown; the badge stays contact_only until someone reads it.

Cancellation / refund

Not publicly disclosed; set in enterprise agreements.

Support SLA / resale

Enterprise support through Check Point, including the Infinity Portal already used for its other security products.

Missing data

Plan names, prices and limits on platform.lakera.ai/pricing, which did not render to a fetch.

Agentic Index verified 2026-09-25

Alternatives to Lakera

The closest documented capability profiles to Lakera among agent infrastructure platforms tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.

Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded

Contact us

Found a vendor we missed? Have feedback on the index? We'd love to hear from you.