Local-first design
Penetration testing touches some of the most sensitive data an organization has — credentials, internal topology, and proof of exploitable weaknesses. AgentRidge is built so that the sensitive core of an engagement stays on the operator's own workstation.
Where the work happens
The heavy lifting — the reasoning, the tool execution, the findings, and the report generation — all runs inside the app on your machine. The reasoning core, the Ridge inference engine, runs locally rather than sending your engagement to a remote service.
The only things that talk to the cloud are account and licensing functions: signing in, checking your entitlement (free trial vs Pro), and handling a purchase. Your targets, findings, evidence, and reports are not part of that.
What this means for you
- Sensitive data stays local. Target details, discovered credentials, and proof-of-concept evidence live on your workstation, in the app's local data directory. See Data locations.
- Works on your terms. Because the reasoning engine is local, the app is suited to isolated or restricted environments where sending engagement data to a third-party service would be unacceptable.
- Predictable footprint. The runtime is downloaded once and reused; it is not re-fetched for every mission. See First launch.
The trade-off: a capable machine
Running the reasoning engine locally is why AgentRidge asks for a reasonably powerful machine and a one-time runtime download. This is a deliberate choice: the privacy and autonomy of a local-first engine are worth the disk space and memory. See System requirements for the specifics.
Next: installing AgentRidge →