Levo
changelog-20261020-c5ed4996 commercialThe section your link pointed to isn't on Levo's page any more, so we've brought you to the top.
Levo is a platform that provides API security testing, API inventory management, and AI security controls including an AI Gateway and AI Firewall.
Summary
Levo is a commercial web application security platform, run as a hosted service, that combines API discovery, DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces. scanning, and AI security monitoring into one system for finding and testing an organization's exposed applications, APIs, and AI agents. It suits application security and platform teams responsible for attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. visibility, particularly those who need to track APIs and AI/MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. components that traditional scanners miss, and it also supports CLI-driven scans for teams wanting to trigger tests from pipelines. Levo sits in the broader web-app and API security space, layering policy-based AI guardrails and traffic attribution for agents and sessions on top of conventional scanning and discovery work. Recent development has pushed deeper into AI-specific coverage: discovering AI agents and MCP tools, tagging AI traffic to individual sessions, and enforcing guardrails through a dedicated policy framework, alongside steadier DAST and EASMEASMExternal Attack Surface Management: a discipline and category of tooling that continuously discovers and monitors an organization's internet-facing assets to identify exposures before attackers do. improvements.
Levo is a platform that provides API security testing, API inventory management, and AI security controls including an AI Gateway and AI Firewall.
How Levo helps
Which of our APIs and web applications are actually exposed on the internet, including ones nobody documented?
crawls and discovers endpoints from both traffic and source code, then lists them in a catalog alongside what's already known so undocumented or forgotten services surface as attack surface
Which AI agents and MCP tools are running in our environment right now?
scans cloud providers and network traffic to find agents, models, and MCP tools in use, adding them to the discovery catalog even when they weren't provisioned through a normal review process
Whose session or agent generated this suspicious AI traffic?
tags AI traffic to the individual agent and session that produced it, so a flagged request can be traced back to the actor behind it rather than left as an anonymous log line
Do any of our applications have exploitable vulnerabilities, and can we prove it?
runs scheduled or on-demand scans against the application, including logging in through AI-driven authentication, and captures evidence of exploitation alongside each finding
Which AI guardrail rules are actually being enforced, and where are they being violated?
evaluates live AI traffic against the policy framework's identity-aware rules and raises alerts when a guardrail is crossed, showing which policy fired and against which session
Has scanning coverage or behavior quietly changed for a specific application versus the rest of our environment?
lets each application override the environment's default security-test settings and marks every setting as inherited or overridden, so a divergence is visible rather than buried in shared configuration
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Levo, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Levo puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What Levo connects to, runs on and detects, read from its release notes and docs. So far: 1 updated detection, 1 new integration.
2 changes, tracked since Sep 22, 2026.
-
Oct 122026
updated TLS findings from the Satellite restored
TLS findings from the Satellite are reported again after being silently absent
-
Sep 222026
new WSO2 API Gateway integration
This release connects Levo to WSO2 API Gateway with a one-click push of endpoints
Cloud platforms & services 1
Nothing first seen in this window. That doesn't mean Levo shipped nothing, only that we found no record of it.
How we count
Read from 8 of 26 release notes and docs updates we hold for Levo. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Levo's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
26 entries
No entries match these filters.
- October 20268
- September 20266
- August 20261
- July 20262
- June 20261
- May 20262
- April 20262
- March 20262
- February 20261
- January 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →