Compare
AttackCompass vs Dradis
Dradis is strong for collaborative engagement notes and reporting. AttackCompass is operator-controlled engagement guidance — ranked next actions from recorded state, with a report path that starts from work you already captured.
Context
What Dradis is good at
What teams usually hire Dradis for — before stacking AttackCompass beside it.
- Collaborative engagement documentation and report-oriented workflows many pentest teams already know
- A shared place for notes and findings when the deliverable is the primary pain
- Familiar “engagement binder” mental model for firms that standardize on Dradis
AttackCompass
What AttackCompass adds
- Turns recorded scope, hosts, services, credentials, findings, attempts, and evidence into ranked next actions — and shows why
- Recommendations adapt as engagement state changes; blocked steps show missing prerequisites
- Operator stays in control — the web product does not autonomously execute attack tools
- Hosts, services, credentials, findings, notes, evidence, sessions, objectives, and route context can live in one workspace
- Report workflow from engagement context; PDF export; lossy Markdown content export as documented — tester remains editor
- Not another tool you run; the system that keeps the engagement coherent while you run tools you trust
You can keep Dradis (or any report collab tool) if it works for deliverables. AttackCompass adds live decision support and memory during the test — not a mandate to rip out your report stack on day one.
Side by side
Category comparison
Where a cell shows a dash, that product is not built for that job.
| Topic | Dradis (category) | AttackCompass |
|---|---|---|
| Primary job | Collaborative notes / report-oriented engagement docs | Operator-controlled engagement guidance + coherence from discovery to report |
| Next-step prioritization | Varies by workflow | Ranked next actions with reasons from recorded state |
| Adapts as state changes | — | Recommendations change with services, findings, progress, and context |
| Executes attacks | — | No — operator executes |
| Workspace state | Notes / report collaboration focus | Hosts, services, creds, findings, evidence, sessions, route context |
| Reporting | Strong category fit for collab reporting | Report editor from captured work; PDF; lossy Markdown export — not auto client-ready |
| Best when | Team already standardized on Dradis for deliverables | Operator needs ranked “what next” from live state without replacing scanners |
FAQ
Common questions
- I already use Dradis.
- Keep it if deliverables work there. AttackCompass adds structured engagement state and decision guidance notes alone do not provide.
- Is this a scanner?
- No. Your scanners tell you what exists. AttackCompass helps you decide what matters next.
- Does it run attacks?
- No. Recommendations only; the operator controls execution.
- Will it replace my report tool?
- Not required. The advantage is reporting that starts from context captured during the engagement.
- Is this only for juniors?
- Juniors get guidance; seniors get less bookkeeping and a cleaner evidence-to-report path.
Try it on a real engagement
Start a 7-day trial — full Founding Operator access, no card to start. Then Founding Operator $49/mo or $399/yr. Team plans: [email protected].