Software architecture first
AttackCompass comes from people who care about coherent systems — state, evidence, and decisions that stay connected as work gets complicated.
About
Built because real pentests do not follow checklists.
AttackCompass exists so work saved during an authorized engagement makes the next step — and the final report — easier to stand behind.
Why
Keep the engagement coherent from discovery to report.
Notes, screenshots, credentials, and pivots scatter across tools. AttackCompass sits above the stack you already use and connects that work into ranked next steps with reasons you can check.
The founder story matters only as credibility. The hero of AttackCompass is the operator running an authorized pentest — not the company page.
Origin
Who built this — and who it is for
Enough signal to answer “does this come from people who actually understand the job?” — without turning the site into a cult of personality.
Offensive security practice
Real engagements do not follow a straight checklist. Hosts lead to services. Logins open new paths. The product is built around that mess.
Operator as the protagonist
The pentester stays in control. AttackCompass ranks next steps and keeps proof ready for the report — it does not run the attack for you.
Principles
What we will not pretend
AttackCompass does not autonomously exploit targets. It does not replace Nmap, Burp, BloodHound, or your judgment. It does not promise complete coverage or a report that needs no review.
Read the Security Model before you put client data in a workspace. Start a trial when you are ready to test it on an authorized engagement.
Try it on work that matters
Seven days of full access. No billing details required to start.