AI-powered
penetration testing.
violet runs autonomous security agents that find, confirm, and report real vulnerabilities — not just alerts. Point it at your app — production, staging, or local — with whatever auth it needs, and get a pentest-grade report with reproducible exploits.
Five phases, from target to reproducible PoC.
violet emulates a human pentester’s methodology — combining authenticated reconnaissance with live exploitation in a real browser.
Confirmed exploits. Not alerts.
Confirmed exploits ship with a working proof-of-concept. When a WAF, CSP, or rate limit blocks the attack, the finding still ships as a security recommendation — not silently discarded.
- →Copy-and-paste PoCs you can re-run yourself
- →Markdown + PDF deliverables for auditors
- →Severity ranked · CVSS · remediation guidance
- →AI-fix prompt file — one per finding, ready for Claude, Codex, Gemini, or your team's AI assistant
SQL injection leaks credentials on /rest/products/search
The q query parameter is concatenated into a raw SQL statement. A UNION-based payload leaks the full Users table, including bcrypt hashes.
# UNION payload pulling users + bcrypt hashes $ curl "https://app.acme.com/rest/products/search?q=qwert'))" "UNION SELECT id,email,password,null,null,null,null,null,null FROM Users--" → 200 OK [{"email":"[email protected]","password":"$2a$08$..."}, ...]
Watch the agent work.
Every action streams to a live activity feed — tool calls, HTTP traffic, reasoning, and the exact moment a hypothesis is confirmed as a real exploit. Replay any run.
Your team ships every day. Your pentest shouldn’t happen once a year.
Every pentest credit gets you a full run of the 5-phase pipeline. Kick one off before a release, after a refactor, or whenever you want a fresh pair of eyes on the code.
Can I run violet against production?
Yes. Configure a production scan with rate limiting and focus/avoid path rules to keep traffic and blast radius controlled. For destructive payload classes we still recommend staging or a sandbox — but production is a first-class target.
Does violet need my source code?
No. Source code analysis is optional — it helps find deeper bugs when you connect GitHub or GitLab, but violet runs a full black-box pentest without it. Point it at your URL and go.
What authentication does violet support?
Login forms, API keys, and username/password (basic auth) — plus fully anonymous scans for public surfaces. The auth step accepts standard credentials and handles login automatically. Credentials are used only during the scan and never stored.
What vulnerabilities does it cover?
OWASP Top 10 coverage — and growing. violet runs 5 parallel agents during vulnerability analysis, then 5 more parallel agents during exploitation that confirm each finding with a working PoC. Coverage expands without blowing up wall-clock time.
How long does a pentest take?
A full run typically completes in 1–1.5 hours. Phase 3 runs 5 parallel agents for vulnerability analysis, and Phase 4 runs 5 parallel agents for exploitation — parallelism per phase keeps wall-clock time down.
How is violet different from a traditional scanner?
Traditional DAST tools fire payloads and flag responses — producing long lists of "potential" issues. violet reasons through your code, forms hypotheses, and actually exploits them. What you get back is a short list of confirmed bugs with working PoCs, not a spreadsheet of maybes.
Point violet at something you built.
Sign up, point violet at your app, and get a pentest-grade report in about an hour.