Escape – AI-Powered Offensive Security for APIs and Web Apps

TL;DR

TL;DR: Escape replaces point-in-time security scanners with AI agents that continuously discover, test, and prove exploitability across your API attack surface — delivering actionable remediation steps instead of generic vulnerability reports.

Source and Accuracy Notes

• Project page: escape.tech ← verified homepage content
• Source repository (open-source component): github.com/Escape-Technologies/graphql-armor ← verified README
• Open-source package: @escape.tech/graphql-armor on npm
• License: MIT (per GitHub repo LICENSE file)
• HN launch thread: news.ycombinator.com/item?id=39215779 — 96 points, YC W23 batch
• Docs: docs.escape.tech

What Is Escape?

Escape is an offensive security platform built around four core products:

• Attack Surface Management — discovers and validates exposure of applications, APIs, and infrastructure from code to cloud
• Business-logic-aware DAST — dynamic application security testing that understands your application logic, not just generic vulnerability patterns
• AI Pentesting — multi-agent architecture that probes for complex vulnerabilities, produces proof-of-exploit, and delivers fix-ready reports
• External Network Pentesting — continuous probing of internet-facing infrastructure

The company’s stated goal is to replace legacy point-in-time security scanners (DAST tools that run once per release cycle) with continuous, intelligence-driven assessment that compounds over time rather than resetting.

Their open-source GraphQL Armor library (@escape.tech/graphql-armor) is published on npm and protects GraphQL servers against introspection abuse, batch queries, and depth attacks. It is the main OSS component of the platform.

Setup Workflow

Quick Start: GraphQL Armor (OSS)

GraphQL Armor is the standalone open-source piece and the fastest way to get familiar with Escape’s approach:

# npm
npm install -S @escape.tech/graphql-armor

# yarn
yarn add @escape.tech/graphql-armor
```bash

```javascript
// Apollo Server example
import { applyArmor } from '@escape.tech/graphql-armor';
import { makeExecutableSchema } from '@graphql-tools/schema';
import { ApolloServer } from '@apollo/server';

const typeDefs = `type Query { hello: String }`;
const resolvers = { Query: { hello: () => 'Hello world!' } };

const schema = applyArmor(makeExecutableSchema({ typeDefs, resolvers }));
const server = new ApolloServer({ schema });

The library adds per-operation cost analysis, depth limiting, and introspection suppression as middleware — blocking the most common GraphQL-specific attack patterns without changing your schema.

Enterprise Platform (SaaS)

The full Escape platform is cloud-hosted and SaaS-only. There is no self-hosted option for the main pentesting and ASM products.

1. Book a demo at escape.tech/book-a-demo
2. Connect your target application (REST, GraphQL, or internal API)
3. The AI agent begins its reconnaissance phase automatically
4. Results appear with proof-of-exploit, request/response traces, and fix recommendations

How the AI Pentesting Agent Works

Escape describes its core architecture as a multi-agent system that maintains a memory of your application context — roles, data models, auth patterns — across engagements.

Rather than returning a raw vulnerability list, the agent produces:

• Exploit proof — a full request chain showing exactly how an attacker would trigger the finding
• Framework-specific remediation — code snippets tailored to your actual stack, not generic “apply OWASP guidelines”
• Regression test — a DAST test that can be added to your CI pipeline to prevent the same issue recurring

The company claims this reduces time-to-remediation significantly versus manual penetration tests, where reports often sit unread because engineers cannot immediately act on a generic severity rating.

Core Platform Features

Continuous ASM and DAST

Traditional DAST tools run at release time and produce a snapshot. Escape’s dynamic scanning is continuous — re-running against every significant deployment and flagging drift from the known-good baseline.

Business Logic Testing

Generic scanners understand HTTP status codes and error messages. Escape’s AI models attempt to understand what the application is supposed to do — which roles exist, what an admin can access versus a regular user — before probing for logic flaws like IDOR, broken authentication, and privilege escalation.

IDOR Scanning

The company specifically calls out IDOR (Insecure Direct Object Reference) scanning as a differentiator. Their site notes that “IDOR scanning and multi-tenant capabilities set it apart from other security testing solutions” (from a verified customer testimonial on the Escape blog).

GraphQL Armor (OSS)

For teams running GraphQL in production, the open-source library covers:

• Batch query limiting — prevents attackers from weaponizing batched operations for data extraction
• Depth limiting — stops deeply nested queries that can cause server-side resource exhaustion
• Introspection suppression — removes the introspection endpoint from production traffic
• Cost analysis — per-field cost scoring to detect abnormally expensive operations

Practical Evaluation Checklist

If you are evaluating Escape for a team or project, here is a concrete checklist based on what the site and documentation describe:

• Does your application expose a large or undocumented API surface? Escape’s ASM product is designed to find endpoints that are not tracked in your OpenAPI spec.
• Are your current penetration tests producing generic reports that engineering ignores? Escape’s fix-specific output and regression tests are aimed at that problem.
• Do you run GraphQL in production? GraphQL Armor is a no-dependency middleware that covers the most exploited GraphQL-specific attack patterns.
• Are you subject to PCI-DSS, SOC2, or ISO 27001 compliance audits? Escape mentions both as supported compliance frameworks with audit-ready reporting.

Security Notes

Escape is a SaaS platform, which means your API traffic — including test payloads — routes through their infrastructure. For internal applications, the site mentions “cloud and on-prem hybrid deployments” as an option for keeping assessment traffic local.

For the open-source GraphQL Armor library: it is a middleware layer and makes no outbound connections. Audit the source at github.com/Escape-Technologies/graphql-armor before adding it to a security-critical service.

FAQ

Q: Is Escape open source? A: Partially. The GraphQL Armor library is open source under the MIT license. The main pentesting platform and ASM/DAST products are SaaS-only.

Q: How does Escape differ from a traditional DAST scanner? A: Traditional DAST tools scan for known vulnerability patterns against a fixed baseline. Escape’s DAST is described as “business-logic-aware” — it attempts to model your application’s intended behavior before testing, which allows it to surface logic flaws (IDOR, auth bypass, broken access control) that pattern-matchers miss.

Q: Can Escape run against internal APIs not reachable from the internet? A: The site mentions hybrid cloud/on-prem deployment options. Contact their team for architecture specifics if you have air-gapped environments.

Q: Does Escape replace bug bounty programs? A: Escape frames its AI pentesting as complementary to — and in some cases a replacement for — ongoing bug bounty programs. Their claim is that continuous automated testing with proof-of-exploit is more actionable than a queue of submissions from external researchers with varying quality.

Conclusion

Escape’s most differentiated claim is not a specific vulnerability class or scanner feature — it is the architecture of the assessment process itself. Traditional penetration testing produces a document; Escape produces a continuous, regression-tested security posture that compounds instead of resetting every quarter.

For developers and security engineers tired of penetration test reports that produce more questions than answers, the platform’s fix-specific output and CI-integrated regression testing address a real pain point. The open-source GraphQL Armor library is the most immediately usable piece — a single npm package that covers the GraphQL-specific attack patterns most likely to appear in a bug bounty猎赏金猎人 report.

The company is YC-backed (W23), has been publishing security research (they found CVE-2026-17059 in Keycloak), and has customer testimonials from security teams at Visma, Schibsted, and Applied Systems.

Source and Accuracy Notes

• Project page: escape.tech
• Source repository (OSS): github.com/Escape-Technologies/graphql-armor
• License: MIT (verified via GitHub LICENSE file)
• HN launch thread: news.ycombinator.com/item?id=39215779 — Launch HN, YC W23, 96 points
• Docs: docs.escape.tech