Skip to main content
Describe what you need in plain language and Neo plans and executes it. Here’s what Neo can handle:
  • Pentesting applications and APIs
  • Reviewing code for vulnerabilities
  • Triaging scanner findings
  • Mapping attack surfaces
  • Validating patches
  • Modeling threats
  • Monitoring for new exposures
If you’re getting started, the workflows below give you a structured entry point. Neo fills in the details so you don’t have to get the prompt exactly right.

Pentest

Long-running, contextual pentest: full recon through exploitation with real-world impact proof

Vuln triage

Cut through noise: rank findings by true exploitability and blast radius

Code audit

Exhaustive code review: full architecture mapping, data-flow tracing, and validation

​
How Neo works

Regardless of which workflow you run, Neo follows the same four-phase process every time.
1

Plan

Neo reads your scope, credentials, and any context you provided, then builds a multi-step testing plan. It maps the attack surface, identifies the highest-risk areas based on the application’s architecture, and decides which tools and techniques to apply in what order.You can see the plan before execution begins and steer it if needed.
2

Execute

Neo works through the assessment systematically: crawling the application, probing endpoints, testing authentication and authorization flows, attempting injection, chaining findings into multi-step attack paths, and running browser-based tests for client-side vulnerabilities.Every command, request, and decision streams in real time so you can follow along or intervene at any point.
3

Verify

Before reporting any finding, Neo independently confirms it is exploitable. It re-runs the attack, captures the full evidence trail (payloads, request/response pairs, screenshots, execution logs), and validates that the issue is real, not a theoretical concern.Findings that cannot be confirmed are discarded, not reported.
4

Report and file issues

Neo delivers a complete report in your chosen format: every confirmed vulnerability with its severity, evidence, reproduction steps, and remediation guidance. If you have Linear, Jira, or GitHub connected, Neo automatically creates issues for each finding. No copy-pasting required.
Stay in session for your first run. Watching Neo plan and execute gives you a clear sense of how it thinks, which makes every subsequent run easier to direct.

​
Using Neo Effectively

Once you’ve seen Neo complete a workflow end to end, the next step is learning how to collaborate with it effectively. Neo works best when you treat it like a security engineer on your team: share intent, give context, and let it think and work through the details. You can brief it like a teammate, describing what to test, what to avoid, and what success looks like, or give it freedom to explore creatively, like you would with a red teamer.
  • When your goal is specific, Neo executes with precision:
    “Test the staging API for authentication flaws and create tickets for confirmed issues.” “Re-scan assets discovered last week and flag new endpoints only.”
  • When your goal is broad, Neo thinks like an attacker, exploring systems creatively to uncover real paths to risk:
    “Find ways to move laterally from our exposed APIs into internal systems.” “Explore potential privilege escalation paths across the staging environment.”
In both cases, Neo plans a multi-step workflow: mapping assets, selecting tools, chaining tests, and adapting its approach as it learns more about your environment. It can pivot between structured workflows and creative exploration seamlessly. Quick Tips
  • Use clear intent, but don’t be afraid to give Neo open-ended goals; it performs well in both.
  • Provide context once: Neo remembers and builds on it.
  • Interact mid-run: steer or refine in real time.
  • Chain workflows for compounded efficiency and coverage.
  • Review outputs early: transparency builds trust quickly.
  • Iterate toward autonomy: start guided, scale over time.