All analysis was generated autonomously, without human review. Scores are analytical opinions drawn from the cited public sources, without hands-on testing. They are not audits, certifications, investment reports, purchasing advice, or evaluations of quality.
Wallarm sells enterprises software that blocks attacks on their APIs and enforces security policy on their AI agents. Founded in 2016, it raised a $55 million Series C led by Toba Capital in 2025. Wallarm names Panasonic, Victoria's Secret, Dropbox and Rappi among its customers. It holds a US patent on the method its AI Hypervisor product uses to read what AI agents do without modifying the application. In 2025, co-founder Ivan Novikov named Akamai, AWS and Google Cloud among Wallarm's most serious competitors. Wallarm sells AI Hypervisor exclusively through AWS Marketplace, where AWS could build policy enforcement for AI agents into its own security services. Wallarm's software acts on live traffic, so it can block an attack on an API or end a misbehaving AI agent's session.
| Description | Security platform that discovers APIs and AI workloads, enforces runtime policy inline, blocks API and AI-specific attacks, and generates continuous compliance evidence, marketed as an AI Control Platform built around AWS. | [f1] |
|---|---|---|
| Founded | 2016 | [f2] |
| HQ | Austin, Texas, United States | [f3] |
| Latest funding | Series C, $55M, July 2025 | [f4] |
| Product | What it does |
|---|---|
| Wallarm AI Control Platform | Unified platform that discovers, observes, enforces, and governs APIs, AI workloads, and AI agents at runtime using patented non-invasive kernel instrumentation. |
| AI Hypervisor | Runtime enforcement layer for AI agents, deployed as a Kubernetes DaemonSet that uses kernel-level eBPF instrumentation to observe agent calls and block sessions that violate policy. |
AI Defense Matrix
| Govern | Identify | Protect | Detect | Respond | Recover | |
|---|---|---|---|---|---|---|
| AI-Workload Platforms Inference servers, training platforms, vector DB platforms, and the model-loading supply chain. | ||||||
| AI Coding and Orchestration Tools AI coding tools and agentic orchestration tools on user devices, plus their plugins, skills, hooks, system prompts, scaffolding, harnesses, configuration settings, and MCP clients. | ||||||
| AI-Generated Code Code produced by AI tools, AI-assisted reviews, AI-generated infrastructure-as-code and tests, and vibe-coded apps that bypass CI/CD. | ||||||
| AI Traffic Paths to external and self-hosted AI services, MCP tool channels, agent-to-agent calls, model-registry downloads, and egress to unapproved AI services. AI gateways, LLM routers, and MCP gateways steer traffic along those paths. The steering decisions and their inputs belong here too: routing policies, MCP server registries, and agent naming and discovery services. | ||||||
| AI Model Model weights, fine-tuning checkpoints, model cards, registries, an AI bill of materials (AIBOM), and the third-party LLMs your enterprise consumes. | ||||||
| Training Data Datasets used for training, fine-tuning, and continued learning. | ||||||
| Runtime AI Data User prompts, inference inputs, RAG content, vector DB content, persistent agent memory, and interaction history. | ||||||
| AI Agent Identities AI agents as non-human principals, plus credentials, keys, permission scopes, service accounts, and delegation chains across agents and tools. |
AI Hypervisor observes AI agent decisions, the data boundaries they cross, and the external calls they make at runtime through kernel-level eBPF instrumentation, and blocks the actions that violate policy inline. These capabilities are mapped to the AI Defense Matrix. [f5]
Cyber Defense Matrix
| Identify | Protect | Detect | Respond | Recover | |
|---|---|---|---|---|---|
| Devices Workstations, servers, phones, tablets, storage, network devices, IoT infrastructure, and similar hardware. | |||||
| Applications Software, interactions, and application flows on the devices. | |||||
| Networks Connections and traffic flowing among devices and apps, plus communication paths. | |||||
| Data Content at rest, in transit, or in use across devices, apps, and networks. | |||||
| Users The people using the devices, apps, networks, and data. |
The Wallarm AI Control Platform's API Security and WAF/WAAP lines discover APIs, protect them inline, and detect and block attacks such as the OWASP API Top 10, abuse, and account takeover across REST, GraphQL, gRPC, SOAP, and WebSocket. These lines earn the Cyber Defense Matrix. [f1]
How well the company can compete in its security market, scored across eight dimensions against public evidence.
| Dimension | Score | Rationale |
|---|---|---|
| Problem Clarity How precisely the company defines its problem, with evidence the problem exists at the scale claimed. | 3/5 | Wallarm names the CISO and the CIO as its buyers. Wallarm states on its homepage that 87% of security leaders identify AI-related vulnerabilities as their fastest-growing cyber risk. The one independent quantification is ECI Research's survey on multi-agent adoption, a single non-vendor source where rung 4 asks for several. [s3, s1, s12] |
| Capability Depth How specific the technical capabilities are, with evidence beyond marketing claims such as docs and third-party validation. | 3/5 | Wallarm's documentation describes an AI workload scanner that attaches to processes through eBPF and memory analysis without an SDK or code change, and MCP controls that enforce access policies and validate tool calls. The outside coverage in the cited sources reports Wallarm's own argument for the platform and its threat research, rather than independently testing the protection mechanism. Concrete vendor-side detail without multiple independent validation points is rung 3. [s7, s19, s12, s10] |
| Market Timing Whether the market is ready for this product, with evidence that buyers are actively seeking solutions. | 4/5 | Two independent kinds of buyer-side signal appear. One is a regulatory driver, the EU AI Act, which the European Commission says became applicable on 2 August 2026. Its rules for high-risk use cases in certain sensitive areas follow on 2 December 2027. ECI Research calls the August 2026 deadline the near-term forcing function for European operations. The other is a 2025 buyer survey, in which ECI Research found two-thirds of enterprise AI leaders running multi-agent workflows. [s14, s12] |
| Team Credibility Demonstrated domain expertise with public signals such as prior exits, publications, and industry recognition. | 3/5 | Co-founder Ivan Novikov led Wallarm from its founding, according to BankInfoSecurity, and Google Patents lists him as the inventor on its granted patent. The March 2026 team adds enterprise-software operators, including a chief executive with senior roles at Quest Software and BMC Software. No prior exit in the security domain appears in the cited sources. The evidence shows one in-domain build, short of the plurality rung 4 requires. [s8, s15, s6] |
| GTM Proof Evidence of actual traction (customers, revenue signals, partnerships) beyond stated intentions. | 3/5 | Wallarm's site quotes Rappi's head of security on protecting its backend APIs, and the platform is generally available on AWS Marketplace. The 134% net revenue retention figure comes from Wallarm's own release, and its description of enterprise customers comes from its founder. Named references and a marketplace listing without independent corroboration of scale sit at rung 3. [s3, s12, s16, s8] |
| Funding Efficiency Whether funding matches go-to-market ambition, with signs of capital-efficient growth. | 3/5 | Wallarm closed a $55 million Series C led by Toba Capital in July 2025, and SecurityWeek puts total funding above $70 million. Visible output followed, including the general availability of the AI Control Platform in June 2026 and a patent granted in December 2025. Revenue and margin stay undisclosed and the 134% retention figure is the company's own, so efficiency is unconfirmed at the proportional-raise rung. [s5, s9, s17, s15, s16] |
| Category Clarity Whether the company creates or fits a recognizable category that buyers can quickly place in their stack. | 4/5 | Independent outlets place Wallarm in API security without coaching. SiliconANGLE calls it an application security company, and BankInfoSecurity describes it as moving from securing APIs to protecting the business logic they carry. The OWASP API Security Top 10 defines the risks that category covers. Outlets place that API-security core without coaching, which supports the 4. [s10, s8, s13, s12] |
| Incumbent Defensibility How vulnerable the core value proposition is to absorption as a feature by a platform vendor. | 3/5 | Novikov told BankInfoSecurity that Wallarm's most serious competition comes from Akamai and from AWS and Google Cloud, which offer built-in security features. Wallarm's patented kernel-level method and inline enforcement add friction to absorbing its product. The cited record shows no data flywheel or procurement position that bundling could not eventually replicate, which keeps the score at 3. [s8, s15, s1] |
Wallarm sells to the security and technology leaders of enterprises that run APIs and AI workloads in production. Its company page frames the buyer as the CISO who needs governance and the CIO who wants speed. The homepage adds that the platform is built for enterprises running AI on AWS.
Wallarm states on its homepage that 87% of security leaders identify AI-related vulnerabilities as their fastest-growing cyber risk. ECI Research adds its own 2025 survey, in which two-thirds of enterprise AI leaders already run multi-agent workflows.
The API side of the problem is documented outside the vendor. The OWASP API Security Top 10 catalogs API risks such as broken object level authorization. Wallarm's own 2026 threat report, as SiliconANGLE relays it, counts 11,053 API-related vulnerabilities published in 2025, 17% of the total. [s3, s1, s12, s13, s10]
The Wallarm AI Control Platform brings Infrastructure Discovery, AI Hypervisor and API Security together on one platform. Infrastructure Discovery provides cross-account visibility across a customer's AWS estate. API Security blocks the OWASP API Top 10, abuse and account takeover across REST, GraphQL, gRPC, SOAP and WebSocket traffic.
AI Hypervisor is the AI-specific core, and Wallarm made the platform generally available in June 2026. Its documentation describes software on each Kubernetes worker node that inspects AI workloads through patented memory analysis. The product traces model calls, agent actions and MCP tool use. It can end a session or block an outbound call before delivery to the model provider.
Wallarm's pages describe the deployment boundary two ways. The product page says AI Hypervisor deploys on EKS or any Kubernetes cluster, while the documentation says AI workloads must run on EKS. Wallarm also publishes the code of its open-source API Firewall on GitHub. [s1, s17, s7, s2, s31]
Wallarm's co-founder names cloud and CDN vendors as its hardest competition. Novikov told BankInfoSecurity in 2025 that Akamai, AWS and Google Cloud, with their built-in security features, are among its most serious rivals. That puts Wallarm against platforms already present in its buyers' infrastructure.
Wallarm's stated difference is joining API security and AI security in one enforcement point. In ECI Research's reading, that integration is what differentiates Wallarm's approach. On its AI Hypervisor page, Wallarm contrasts the product with AWS Bedrock Guardrails. It says Guardrails sees only Bedrock calls while AI Hypervisor works across providers.
The AWS alignment is both a sales channel and an exposure. Wallarm sells AI Hypervisor through AWS Marketplace and connects the platform to AWS security services such as GuardDuty and Security Hub. ECI Research lists the platform's handling of clouds beyond AWS among the areas to watch. Wallarm markets its API security line for any cloud and for on-premises environments. [s8, s12, s2, s7, s1, s16]
Wallarm names customers across several sectors. Its homepage names Panasonic, Victoria's Secret, Miro, Dropbox, Rappi and others under a Trusted By heading. On its company page, Rappi's head of security says Wallarm protects Rappi's backend APIs across multiple regions.
The AI line has a named customer as well. In the June 2026 launch announcement, CarCollect's chief technology officer says Wallarm secures its AI, MCP servers and APIs. AI Hypervisor sells only as an AWS Marketplace private offer, billed as a line item on the customer's AWS bill.
The scale figures come from the company. Wallarm reports 134% net revenue retention across enterprise accounts for 2024, a figure PR Newswire syndicated with its Series C release. In March 2026 Wallarm named a chief revenue officer with more than 30 years in enterprise sales. Novikov handed the broader business to the new executive team. [s1, s3, s17, s7, s5, s16, s6]
Co-founder Ivan Novikov led Wallarm from its founding until March 2026 and remains on its board. Google Patents lists him as the inventor on the patent Wallarm was granted in December 2025. TFiR describes Wallarm's API ThreatStats report as the 15th in a series running since 2022.
The operating team comes from enterprise software. Shayne Higdon moved from chief operating officer to chief executive in March 2026, after senior roles at Quest Software, BMC Software, Jamf and HighRadius. The new chief revenue officer brings more than 30 years in enterprise sales. The advisory board includes the author of the naxsi web application firewall.
No prior exit in the security domain appears in the cited sources. The team's standing comes from verifiable in-domain roles, a granted patent and a sustained research series. [s8, s6, s15, s30, s3]
Wallarm states on its own site that it has achieved SOC 2 Type 2 compliance. It offers a copy of the report to customers who ask its security team.
Compliance evidence is also a product feature. AI Hypervisor produces session audit logs, an AI software bill of materials and EU AI Act article mapping for customers. The European Commission's AI Act framework places monitoring and incident-reporting duties on providers and deployers of high-risk AI systems. Customers whose systems fall in that class can use that evidence.
Wallarm says on its homepage that the platform is validated against AWS's own AI security criteria. [s26, s2, s14, s1]
| Company | Relationship | Note | Compare |
|---|---|---|---|
| Salt Security | competes with | N/AWe captured the evidence for these companies under different evidence-model versions (v1 vs v2), so the totals were scored under different conditions and are not directly comparable. | |
| Cequence | competes with | ||
| Akamai | competes with | Wallarm's co-founder named Akamai among its most serious competitors in 2025 coverage. | N/AWe scored these companies at different scopes, so the totals measure different things. |
Add analyzed competitors to compare them side by side with Wallarm.
A closer look at the company's product strategy, measuring how defensible it is against market forces and examining the eight areas behind it.
press the advantage
Wallarm's API Security product blocks attacks in the API traffic routed through it. AI Hypervisor enforces policy at the kernel on AI workloads, so a customer leaving would have to replace an enforcement point and recreate its policies. Wallarm holds a granted US patent on the non-invasive monitoring method AI Hypervisor uses. Its compliance position is a SOC 2 Type 2 attestation, which competitors can also obtain. Wallarm's co-founder names cloud and CDN platforms such as AWS as its most serious competition. AWS is also where AI Hypervisor runs and is sold, which ties the AI line to that platform.
| Dimension | Score | Rationale |
|---|---|---|
| Value Delivery Does the product sell software as the product, or judgment, trust, or accountability with software as the delivery mechanism. | 1/3 | Customers buy software their own teams operate, such as AI Hypervisor, which appears as a subscription line item on their AWS bill. Wallarm also sells a SOC service that notifies customers of API attacks and a penetration testing service for agentic AI systems. Those services are optional additions to the platform, so the delivered product stays software. |
| Switching Cost How expensive leaving is for a customer: data portability, integrations, learned workflows, network effects, regulatory data residency. | 2/3 | Leaving means replacing an enforcement point in live API and AI traffic and recreating the policies built on it. AI Hypervisor also produces session audit logs and compliance evidence for the customer. The cited record documents the inline position but doesn't size a migration or show that this state is locked in. |
| Compliance Moat Whether certifications, liability acceptance, or audit trails block an easy replacement. | 1/3 | Wallarm's own attestation is SOC 2 Type 2, which a funded competitor can obtain through ordinary preparation. The EU AI Act mapping it produces serves its customers' obligations. No authorization or mandate held by Wallarm itself appears in the cited record. |
| Problem Complexity Whether the product requires ML, optimization, real-time systems, or years of specialized expertise. | 3/3 | AI Hypervisor inspects AI workloads at the kernel with eBPF and patented memory analysis across Python, Node.js, Go, Java and Ruby. API Security blocks attacks inline across REST, GraphQL, gRPC, SOAP and WebSocket. Both are real-time systems built on specialized kernel and protocol engineering. |
| Buyer Profile Whether buyers are SMB operators, mid-market IT teams, or regulated enterprises and governments with procurement gates. | 3/3 | Wallarm builds and sells its platform for enterprise security leaders at organizations running APIs and AI in production. It reports enterprise accounts in financial services, manufacturing and technology, and its named customers include Panasonic, Dropbox and Rappi. |
| Layer Whether the product is an end-user application, a platform with application features, or infrastructure other applications depend on. | 3/3 | Wallarm's API Security product blocks attacks inline in the API traffic routed through it. Rappi's head of security says it protects Rappi's backend APIs. AI Hypervisor enforces at the kernel, ending sessions or blocking outbound calls before they reach a model provider. Applications depend on these components only for the traffic and workloads routed through them. |
| Proprietary Data, Content, or IP Whether the product accumulates datasets, content licenses, or IP that a rival cannot recreate from scratch. | 2/3 | Wallarm holds granted IP. Google Patents lists Wallarm Inc as assignee of US 12,505,228, granted in December 2025 for non-invasive API discovery and monitoring in third-party processes. AI Hypervisor's documentation names that patent as its method. One patent leaves rivals room to reach similar results another way, and no retained cross-customer dataset appears in the cited record. |
Wallarm sells to enterprise security and technology leaders, framing the buyer as the CISO who needs governance and the CIO who wants speed. It reports enterprise accounts in financial services, manufacturing and technology. Its homepage names customers such as Panasonic, Dropbox and Rappi.
The AI line targets a narrower segment. Wallarm positions the AI Control Platform for enterprises running AI on AWS, and AI Hypervisor's documentation requires AI workloads to run on EKS. The API security line reaches wider, and Wallarm markets it for any cloud, hybrid and on-premises environments.
Wallarm pitches the AI line as an extension of its API platform. It says the platform that secures the APIs underneath a customer's AI now governs the AI itself.
AI Hypervisor inspects AI workloads at the kernel. Its documentation describes a DaemonSet that uses eBPF and patented memory analysis to inventory model providers, agents, MCP servers and data sources. It supports in-process introspection for Python, Node.js, Go, Java and Ruby.
The product enforces as well as observes. It can end a session or block, redact or flag an outbound call before delivery to the model provider. It also attributes each model call to the user who triggered it and produces compliance evidence for EU AI Act and SOC 2 audits.
Wallarm's API side extends to AI traffic. Its Agentic AI Protection documentation says it protects AI agents, AI proxies and APIs with AI features from injection and data leakage. API Security blocks the OWASP API Top 10 across REST, GraphQL, gRPC, SOAP and WebSocket.
Wallarm's go-to-market combines a named customer base with an AWS channel. Its homepage names Panasonic, Victoria's Secret, Dropbox, Rappi and others under a Trusted By heading. CarCollect's chief technology officer is quoted in the June 2026 launch announcement on securing AI, MCP servers and APIs with Wallarm.
AWS is the channel for the AI line. AI Hypervisor is procured only as an AWS Marketplace private offer, and the homepage lists private offers and co-sell. ECI Research adds that Marketplace availability could let customers apply existing AWS committed spend.
Sales leadership changed in March 2026. Wallarm named a chief revenue officer with more than 30 years building enterprise sales organizations. Novikov now focuses on rapid prototyping and threat research while the new executive team runs the broader business.
AI Hypervisor has a documented purchase path. It is procured only through the AWS Marketplace listing as a private offer and appears as a line item on the customer's AWS bill. The homepage describes the Marketplace listing as available with private offers and co-sell.
Wallarm's cited pages publish no list price, so the AI line's cost is set in each private offer. Wallarm markets attribution of LLM cost by user and team, which ties the product's value to AI spend a customer can measure.
The API security line has a separate commercial path. The documentation describes AI Hypervisor as a standalone annual subscription, separate from Wallarm API Security.
The platform is software the customer's team deploys and operates. AI Hypervisor's scanner installs into the customer's EKS cluster through Helm, and Wallarm hosts the tenant with the dashboard and telemetry store. Wallarm markets deployment without sidecars, pod restarts or impact on existing workloads.
Wallarm also sells human services around the platform. Its SOC service notifies customers of API attacks and vulnerabilities and gives advice on running the platform. In 2025 it introduced a penetration testing service for agentic AI systems.
The cited pages don't describe Wallarm taking accountability for security outcomes, so the core deliverable is the software the customer runs.
Wallarm states that it has achieved SOC 2 Type 2 compliance and offers the report to customers on request. Customers request the report by email from its security team.
The product's compliance output is a separate matter. AI Hypervisor maps customer activity to EU AI Act articles, keeps session audit logs and builds an AI software bill of materials. The European Commission sets monitoring and incident-reporting duties for providers and deployers of high-risk AI systems. Customers whose systems fall in that class can use that output.
Wallarm says on its homepage that the platform is validated against AWS's own AI security criteria.
The AI line is built around AWS. The platform connects to AWS Security Hub, GuardDuty, IAM Access Analyzer, Inspector and Macie, and AI Hypervisor sells through AWS Marketplace. Its documentation says AI workloads must run on EKS.
Wallarm markets its API business beyond AWS. It describes its API security solution for any cloud, multi-cloud, hybrid and on-premises environments. It offers three deployment modes, from a self-managed open-source edge inside the customer's network to a hosted service.
The AI line's exposure is its dependence on AWS. ECI Research lists the platform's handling of clouds beyond AWS among the areas to watch. Wallarm contrasts AI Hypervisor with AWS Bedrock Guardrails, saying Guardrails sees only Bedrock calls.
Co-founder Ivan Novikov led Wallarm from its founding until March 2026. He now focuses on rapid prototyping and threat research and remains a board member. Google Patents lists him as the inventor on Wallarm's granted patent.
The operating team came from enterprise software. Shayne Higdon moved from chief operating officer to chief executive, after senior roles at Quest Software, BMC Software, Jamf and HighRadius. The new chief revenue officer brings more than 30 years in enterprise sales.
The company's research output is sustained. TFiR describes the API ThreatStats report as the 15th since 2022, and the advisory board includes the author of the naxsi web application firewall.
| Id | Source | Tier | Accessed |
|---|---|---|---|
| f1 | Wallarm AI Control Platform homepage | official | 2026-06-21 |
| f2 | BankInfoSecurity: Wallarm Secures $55M (states founded 2016, some aggregators cite 2013) | press | 2026-06-21 |
| f3 | Wallarm: new leadership press release (Austin, TX dateline) | official | 2026-06-21 |
| f4 | Wallarm Announces $55 Million in Series C | official | 2026-06-21 |
| f5 | AI Defense Matrix Catalog mapping | other | 2026-09-23 |
This site is an experimental research aid created by Zeltser Security Corp. All its data gathering and analysis was performed autonomously without human review, and it can contain errors of fact, interpretation, and judgment that a human reviewer might catch.
The analyses are statements of opinion, not statements of fact. Machine analysis produced the scores, summaries, and matrix placements by weighing the public sources each page cites, and reasonable people can weigh the same sources differently. Where a page states a fact, it cites the public source and the date it was checked, and the statement is only as accurate as that source. Unless a profile expressly says otherwise, the analysis involves no hands-on testing and no independent validation of any company's products or services.
Nothing here is professional, security, legal, financial, investment, or purchasing advice, and nothing here is a recommendation to invest in, do business with, or avoid any company. Inclusion of a company is not an endorsement, and absence of a company is not a judgment about it. Reading this site creates no advisory or client relationship. Verify any detail you plan to act on against the vendor's current materials.
The content is provided "as is" and "as available," with all warranties disclaimed, express or implied, including merchantability, fitness for a particular purpose, accuracy, and non-infringement. No entry is warranted to be complete, current, or correct. Companies change, vendors update their claims, sources can be wrong, and automated analysis can misread them.
To the fullest extent permitted by law, the operator, Zeltser Security Corp, is not liable for any damages that arise from using this site or relying on its content, including direct, indirect, incidental, special, and consequential damages and lost profits, even if advised that such damages were possible. If you are dissatisfied with the site or disagree with these terms, your remedy is to stop using it.
Entries link to vendor pages, press coverage, and other external sites that Zeltser Security Corp does not control and is not responsible for. A link is not an affiliation with the destination or an endorsement of it. Product and company names and trademarks are the property of their owners, used here nominatively to identify the companies described. Short quotations from cited sources appear for identification and commentary.
Use, quotation, automated retrieval, and redistribution of the content are governed by the Terms of Use at cybercompanyprofiles.com/terms, which permit personal and internal business use with attribution and prohibit republication and resale.