Compare
AttackCompass vs Obsidian
Obsidian and Notion are general-purpose notes and knowledge bases. AttackCompass is engagement-state and operator-controlled next-step guidance built for authorized pentesting — then a report path from work you already recorded.
Context
What Obsidian and Notion are good at
Notes apps are still the right home for lasting technique libraries — AttackCompass is not trying to replace that.
- Fast personal knowledge bases, wikis, and long-lived technique libraries
- Flexible linking and databases for whatever structure you invent
- Excellent for reusable technique notes (commands, checklists, writeups) that outlive a single engagement
AttackCompass
What AttackCompass adds
- Live engagement objects — hosts, services, credentials, findings, evidence, sessions, route context — not only freeform pages
- Ranked next actions with reasons that change as the engagement changes
- Report workflow fed by captured engagement context rather than reconstructing from scattered notes at the end
- Operator-controlled; does not autonomously execute attack tools
- PDF export and lossy Markdown content export as documented; tester remains editor
Technique notes stay in Obsidian or Notion. Engagement-specific state for this host, this credential, this evidence, and this unfinished path belongs in the engagement workspace.
Side by side
Category comparison
Where a cell shows a dash, that product is not built for that job.
| Topic | Obsidian / Notion | AttackCompass |
|---|---|---|
| Primary job | General notes / PKM / docs | Operator-controlled engagement guidance |
| Technique library | Excellent | Not the primary job — keep your notes app |
| Live engagement state | You invent the schema | First-class hosts, services, creds, findings, evidence, sessions, routes |
| Next steps | Manual / checklist pages | Ranked next actions with reasons |
| Adapts mid-engagement | Manual update | Recommendations change with state |
| Executes tools | N/A | No autonomous execution |
| Reporting | Export / paste into your report tool | Report editor from captured work; PDF; lossy Markdown |
Using Notion instead of Obsidian?
Same distinction. Notion is strong for team docs and databases. AttackCompass still sits above notes as the engagement brain — ranked next steps from recorded state, not another wiki.
FAQ
Common questions
- I already use Obsidian, Notion, or Markdown.
- Keep them. AttackCompass adds structured engagement state and decision intelligence that notes alone do not provide.
- Won’t this duplicate my vault?
- Technique notes stay in Obsidian or Notion. Engagement-specific state belongs in the engagement workspace.
- Is this a checklist app?
- Static checklists do not change when the engagement changes. AttackCompass adapts to recorded findings, access, scope, and progress.
- Does it replace my tools?
- No. Keep Nmap, Burp, BloodHound, and the rest of your stack.
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].