Your autonomous AI hacker.
Hand it an authorized target and an objective. It maps the attack surface, builds and runs exploits, and writes up exactly what it proved.
An AI agent that attacks your own apps. A hunter that checks whether the patch actually closed the hole. A daemon that bans what hits your servers. One rule across all three: no proof, no finding.
Offense, research and defense, built on the same rule: a model can suggest anything, but only evidence and deterministic code get the final word.
Hand it an authorized target and an objective. It maps the attack surface, builds and runs exploits, and writes up exactly what it proved.
An advisory says the bug is gone. The hunter checks whether a sibling path survived and whether your stack can reach it. No reproducer, no finding.
Host defense for Linux. Reads your logs, correlates attacks into incidents, bans with expiring nftables rules. An LLM can explain. Only policy can block.
How a team runs the three today. Each tool works on its own and the handoffs are manual — wiring them together is on the roadmap, and marked that way.
An advisory drops. The hunter diffs the fix, hunts the sibling path the patch missed, and proves it under a sanitizer with a reproducer — or tells you exactly why it doesn't apply to your stack.
Service · PHP firstPoint the Agent at your own apps inside a frozen scope. It maps the surface, builds and runs the exploit, and comes back with evidence — not a list of maybes.
Private betaWarden tails your logs, correlates the noise into one incident and bans the source with an expiring nftables rule — under your policy, never on a model's say-so.
Open source soonHunter detection packs delivered to Warden as a rules feed. Agent findings turned into Warden watchlists. On the roadmap. Not shipped — and we won't pretend otherwise.
PlannedTargets, authorization and limits are locked before anything runs. No tool can widen them mid-flight.
A crash isn't an exploit. A scan isn't a finding. Every result ships with reproducers, receipts and stated limits.
Models propose. Deterministic code enforces scope, budgets and policy — and you approve what matters.
All three products are going open source — read, run and audit the code that tests and defends your systems. Teams pay for hosted operation, continuous coverage, fleets, feeds and compliance. Safety controls are never a paid feature.
Hosting and platform providers, agencies and MSSPs carry thousands of third-party components across many apps and servers. Start by verifying which patch gaps your stack can actually reach, hit your apps with the Agent, and defend the fleet with Warden.