Agentic Index
F5 AI Guardrails vs Lakera (2026)
Both vendors last verified
Choose F5 AI Guardrails, formerly CalypsoAI, for inference layer AI security with red teaming, defense, and monitoring in one platform. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Choose Lakera for runtime protection against prompt injection, jailbreaks, and data leakage with continuous red teaming. F5 gives no public price, while Lakera offers a free signup.
On the Agentic Index agent infrastructure ranking, F5 AI Guardrails clears the bar and Lakera does not. F5 AI Guardrails documents all five production contract capabilities in full; Lakera does not document model flexibility and routing in full. 33 of the 186 vendors in the lane clear it. See the agent infrastructure ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. F5 AI Guardrails and Lakera are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,140 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose F5 AI Guardrails if
- F5 is already in your infrastructure and consolidated vendor management matters
- You want model traffic routed through the security layer to providers you choose per project
- Red team campaigns should run on a schedule without anyone starting them
Choose Lakera if
- Check Point is already your security vendor
- You want to start free and self serve before any sales conversation
- Screening should run in a region you pick, with logs kept in the EU by default
| Feature | F F5 AI Guardrails |
L Lakera |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
F5 AI GuardrailsIntegrations & Tool Calling Proxy integrations route the OpenAI and Anthropic SDKs, Claude Code, OpenAI Codex and Google Gemini through the platform, along with Slack and Microsoft Teams integrations and a SIEM connection. These route model traffic and send events, and no connector lets an agent take authenticated action in an outside system. F5 says it audits and blocks agents' tool calls, which governs actions that other systems take. SourceF5 AI Security, docs.aisecurity.f5.com (docs index and integration guides) and /reference/roles-permissions.htmlread 2026-09-25 |
||
|
LakeraIntegrations & Tool Calling 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 Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
F5 AI GuardrailsWorkflow Orchestration The platform sits in front of the customer's models and agents and does not run their workflows. Guardrails scan each call inline, and red team campaigns are ordered attack runs against a target, not agent work in several steps that the customer builds. There is no workflow model. SourceF5 AI Security, docs.aisecurity.f5.com/api-docs/about-api.html and /red-team/managing-campaigns.htmlread 2026-09-25 |
||
|
LakeraWorkflow Orchestration 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 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
F5 AI GuardrailsTriggers & Channel Coverage AI Red Team campaigns run on a schedule. The campaign schedules API sets the start and end time, frequency and interval, along with the number of occurrences and the target providers, and it can run remediation automatically. So a schedule starts the platform's own adversarial testing with no person present. Guardrails work inline, starting when the customer's application sends a scan or a proxied prompt, so they add no trigger of their own, and blocks and alerts are outputs, not triggers. SourceF5 AI Security, docs.aisecurity.f5.com/operations/post_campaign_schedules.html and /api-docs/about-api.htmlread 2026-09-25 |
||
|
LakeraTriggers & Channel Coverage 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 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
F5 AI GuardrailsKnowledge Grounding & RAG Prompts and responses are scanned and the customer's models attacked, but none of the documented API resources, which cover admin, roles, campaigns, license, projects, prompts, scanners, scans, tokens and users, indexes or retrieves the customer's documents for an agent to ground its answers on. SourceF5 AI Security, docs.aisecurity.f5.com/api-docs/about-api.htmlread 2026-09-25 |
||
|
LakeraKnowledge Grounding & RAG 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 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
F5 AI GuardrailsMemory & State Persistence The platform keeps records about the customer's agents, not memory for them. Prompt history, agent sessions and the audit log are read by people and by the scanners' enforcement, and the agent never reads them as context to decide. There is no memory layer or state the agent carries between runs. SourceF5 AI Security, docs.aisecurity.f5.com/operations/get_agent_sessions.html and /api-docs/about-api.htmlread 2026-09-25 |
||
|
LakeraMemory & State Persistence 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 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
F5 AI GuardrailsHuman Oversight & Guardrails AI Guardrails runs structured guardrails inline on prompts and responses. Admins build guardrail packages from prebuilt and custom scanners, switch each one on or off and choose block or audit mode. They can also customize the response a blocked user sees and enforce guardrail use across projects. F5 adds that it explains and traces why each interaction was blocked or allowed, and audits and blocks unauthorized tool calls and agent actions. These guardrails stop an output outright, and there is no human approval step. SourceF5 AI Security, docs.aisecurity.f5.com/reference/roles-permissions.html and f5.com/products/ai-guardrailsread 2026-09-25 |
||
|
LakeraHuman Oversight & Guardrails 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 RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
F5 AI GuardrailsSecurity, Identity & Governance The AI Security platform, formerly CalypsoAI and now sold by F5 (calypsoai.com redirects to f5.com), has a deep access surface. Admins create custom roles from granular permissions over the organization, guardrails, model connections and secrets, projects, users, red team campaigns, reports and attack types, down to API access, which is off by default for basic users. MFA and user blocking are there too. Admins can switch data retention and prompt history logging on or off, and an audit endpoint records activity. No SSO or SAML integration is named. No attestation scoped to these products appears. The F5 Trust Center describes a product certification program (FIPS, NIST, ISO) without naming the AI Security products, and no certificate scoped to AI Guardrails or AI Red Team is shown. F5 owns the product, so a scoped F5 certificate would apply. SourceF5 AI Security, docs.aisecurity.f5.com/reference/roles-permissions.html and f5.com/company/trust-centerread 2026-09-25 |
||
|
LakeraSecurity, Identity & Governance 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 Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
F5 AI GuardrailsObservability & Auditability The platform records the agent's own traffic. Prompt history logs, which admins can switch on or off, can be read in the product and through the API. Agent sessions show agent and tool counts and first and last prompt times, along with errors and the peak outcome, and a dashboard shows token use by project and guardrail. A separate audit log records user and configuration activity, and admins can send events to a SIEM. SourceF5 AI Security, docs.aisecurity.f5.com/operations/get_agent_sessions.html, /guardrails/guardrails-dashboard.html and /reference/roles-permissions.htmlread 2026-09-25 |
||
|
LakeraObservability & Auditability 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 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
F5 AI GuardrailsDeployment & Data Residency The platform runs as SaaS, usually at us1.calypsoai.app, or inside the customer's own environment. The CAI-Deploy installer provisions or installs all AI Security products into AWS, Azure or Google Cloud accounts, into Oracle Cloud, or into an existing Kubernetes cluster, with separate guides for Helm, GCP and OpenShift. F5 also offers private cloud and fully air gapped on premises deployment with full functionality. Hosting it yourself needs your own GPUs, at least 24 GB for Guardrails and 48 GB for Red Team. SourceF5 AI Security, docs.aisecurity.f5.com/get-started/ai-security-install.html and f5.com/products/ai-guardrailsread 2026-09-25 |
||
|
LakeraDeployment & Data Residency 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 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
F5 AI GuardrailsPrebuilt Agents, Templates & Packs Security content ships rather than agents or workflows. Monthly attack packs feed red team campaigns, prebuilt scanners go into guardrail packages the customer assembles, and country PII guardrail sets cover core, France, Japan, Korea and Spain, alongside prompt templates. These are libraries the customer assembles into its own guardrails and campaigns, not packaged assets a customer adopts as working units. SourceF5 AI Security, docs.aisecurity.f5.com/red-team/managing-campaigns.html, /reference/roles-permissions.html and the docs index (PII guardrail references)read 2026-09-25 |
||
|
LakeraPrebuilt Agents, Templates & Packs 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 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
F5 AI GuardrailsModel Flexibility & Routing Admins add model connections with their own stored secrets, set a default provider for each project and switch providers on or off per project. The API sends a prompt to a chosen provider through endpoints compatible with OpenAI, Anthropic and Google, and custom providers can be created too. So admins and users choose the model with their own keys inside the product, and the proxy endpoints do route model traffic. SourceF5 AI Security, docs.aisecurity.f5.com/api-docs/about-api.html and /reference/roles-permissions.htmlread 2026-09-25 |
||
|
LakeraModel Flexibility & Routing 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 Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
F5 AI GuardrailsAPIs, SDKs & MCP Extensibility The AI Security API covers almost everything the platform does, including admin backup and import, roles and permissions, red team campaigns, license, projects, prompts and prompt templates, scanners (which can be created and versioned, exported and imported), scans, tokens and users. It is a REST API with bearer tokens and a full endpoint reference. A Python SDK, the calypsoai package, wraps it, and every sample in the docs uses it. There is no MCP server. SourceF5 AI Security, docs.aisecurity.f5.com/api-docs/about-api.html and /api-reference/read 2026-09-25 |
||
|
LakeraAPIs, SDKs & MCP Extensibility 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 Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
F5 AI GuardrailsTesting, Debugging & Optimization AI Red Team tests the customer's own models, applications and agents. Campaigns bundle attacks of several types, from standard and operational to agentic and custom, each defined by technique, vector and severity, with converters, and drawn from monthly attack packs. They run against the customer's providers, with reports and results the customer reads and compares across runs, and datasets and dataset runs are documented in the API too. Evaluating models is what this module sells, and the model under test is the customer's. SourceF5 AI Security, docs.aisecurity.f5.com/red-team/managing-campaigns.html and /api-docs/about-api.htmlread 2026-09-25 |
||
|
LakeraTesting, Debugging & Optimization 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 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
F5 AI GuardrailsBrowser & Computer Use The platform secures and tests AI models, apps and agents and does not operate a browser or computer itself. SourceF5 AI Security, f5.com/products/ai-guardrails and docs.aisecurity.f5.comread 2026-09-25 |
||
|
LakeraBrowser & Computer Use 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 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | F F5 AI Guardrails |
L Lakera |
|---|---|---|
|
Entry price Lowest public entry point |
Contact sales | Free to start · plan prices not readable (client-rendered page) · enterprise via sales |
|
Pricing confidence How public the numbers are |
Contact only | Contact only |
|
Billing Primary billing axis |
No billing unit is published. | not readable; the pricing page renders client side |
|
Variable cost Workload / overage exposure |
High variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
Free tier
|
|
Buying motion Self-serve vs sales call |
Sales call | Sales call |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
F5 AI Guardrails
-
· Deployment / data residency
Version 10.140.0 of the on premises release adds Performance versions of some F5 AI Guardrails, starting with PII core and the Adversarial attacks package, the new name for the Prompt Injection package.
Source -
· Human approval / guardrails
Arabic language guardrail packages for Saudi Arabia and the United Arab Emirates are now available in F5 AI Guardrails, covering local identifiers such as national IDs, residency and visa numbers, addresses and bank accounts.
Source -
· Security / enterprise
F5 AI Security released SaaS version 10.98.4, introducing improved project administrator support and a new September attack pack for the AI Red Team.
Source
F5 acquired CalypsoAI and Check Point acquired Lakera, both in 2025. F5 sells CalypsoAI's platform as F5 AI Guardrails, and lakera.ai still sells directly with a free signup.
More comparisons with F5 AI Guardrails or Lakera
Other matchups in agent infrastructure platforms
Not the pairing you were after? These compare a different set of agent infrastructure platforms on the same 14 capabilities.