From discovery to report.

Keep recon, creds, pivots, findings, and evidence connected in one workspace. AttackCompass helps you see what to test next, where expected inventory still has gaps from incomplete enumeration, and what belongs in the final report. You stay in control.

See AttackCompass on a real engagement before you decide.

Enumerate

As you scan and look around, save each host, service, and login you find.

Exploit

See what to try for a first foothold and why. Save proof as you work.

Escalate

When you get in, see what higher access to try next. Keep the path clear.

Report

Use your saved loot and findings to write the final report.

Pentesting gets messy fast

Running the tools is only part of the job. You must also track the work.

A pentest may start with one target. Soon, your notes, proof, and test results are spread across many tools.

The target list grows

One target can lead to many systems and paths.

The next step changes

A new service, login, or finding can open a better path.

What did we try? What should we test next?

Proof gets hard to find

It may sit in notes, screenshots, or terminal logs.

Writing starts late

You may have to search old notes to rebuild the report.

Coverage gets unclear

Done, blocked, and still open can live in different places.

One place for your pentest work

Follow the work from discovery to report.

Each step uses what you already saved. Your findings and proof are ready when you write the report.

Scope
Hosts
Services
Credentials

1. Discover

Add what you find as you test. In Lab mode, you can also import Nmap or OpenVAS XML files.

Recommended
Backup
Blocked
Reason

2. Decide

See what to test next. Each step says why it is recommended or what it needs first.

Notes
Evidence
Findings
From / Via / Target

3. Capture

Save notes, proof, findings, logins, and access paths as you work.

Scope
Method
Findings
Evidence

4. Report

Add saved findings and proof to the report. Edit and review. Lab mode: export the complete rendered PDF. Client mode: browser print / Save as PDF.

Works with your tools

Keep the tools you already use.

Keep using your current tools with AttackCompass. In Lab mode, add hosts and services by importing Nmap or OpenVAS XML. For other tools, save the key findings, notes, proof, and results in one place.

Nmap and OpenVAS

Import XML files in Lab mode to add hosts and services.

Burp Suite

Use Burp as you do now. Save the key finding and proof in AttackCompass.

BloodHound

Record useful findings and route details from the work you run outside AttackCompass.

NetExec and your terminal

Copy commands out, run them yourself, and save the result.

Metasploit and other tools

Run them outside AttackCompass. You choose every action.

Your notes and process

Keep both. AttackCompass records what you found and what may be useful next.

Reporting

Build the report from work you already saved.

Save notes, proof, and findings while you test. When it is time to write, the work is ready to use and review.

Report

Scope

Show what was approved for the pentest.

Method

Explain how the pentest was run.

Attack story

Show how the work moved from one step to the next.

Findings

Add each issue and the systems it affects.

Evidence

Add the proof that supports each finding.

How to fix it

Add clear steps to lower the risk.

Test limits

State what was not tested or could not be checked.

Review

Check changes and old sections before delivery.

A Letter

Why AttackCompass was built

Real pentests do not follow a straight line. One host leads to a new service. A login opens a new path.

AttackCompass was built around one simple idea: work saved during a pentest should make the next step and the final report easier to understand.

Know what to test next. Save proof as you go. Build a report you can stand behind.

With love,
The AttackCompass Team

Security

Built for engagements you cannot afford to leak.

Pentest engagements can contain credentials, hashes, API keys, vulnerabilities, screenshots, internal hostnames, network details, and exploit evidence. Client mode is commercial client-side encryption for sensitive fields against a hosted-storage adversary — sealed before upload, with structural metadata left readable on purpose.

Encrypt before upload in Client mode

Commercial client-side encryption for sensitive fields against a hosted-storage adversary: credentials, findings, notes, report content, and more are sealed in the browser or local proxy before they reach AttackCompass. Supported IPv4 addresses and ranges become keyed projections.

Media stays opaque on the server

In Client mode, screenshots and engagement media are encrypted on your device before upload. The hosted app stores opaque ciphertext.

You keep execution control

AttackCompass ranks next steps from what you recorded. You choose and run every attack action. The web product does not autonomously execute attack tools.

Delete workspace records

Deleting a workspace hard-deletes its database records. After a trial expires or a paid subscription ends without renewal, inactive accounts and engagement data are retained for 30 days, then permanently deleted.

Read the Security Model →

Commercial client-side encryption for sensitive fields against a hosted-storage adversary. Operator controlled. No autonomous exploitation.

7-Day Full Trial

See AttackCompass on a real engagement before you decide.

Get full access for seven days. Start with the sample engagement or use AttackCompass on your own approved pentest.

Discover → prioritize → capture evidence → generate report

No billing details required to start. If you do not choose a paid plan and agree to its terms, the trial ends after seven days without a charge.

Full Founding Operator access for seven days. No demo-only limits.

Paid plans after the trial

  • Founding Operator Monthly — $49 a month
  • Founding Operator Annual — $399 a year

A trial converts only after you choose a plan, enter billing details, and agree to renewal. Paid plans renew on their own. Cancel any time. Tax calculated at checkout.

Refunds

Ask for a full refund within 30 days of your first payment.

Email [email protected] within 30 calendar days of the first payment (UTC). Renewals and chargebacks do not qualify. See the Refunds page for full terms.

Common questions

Does AttackCompass run attacks for me?

No. AttackCompass gives guidance. You choose and run every action.

Can I keep using my current tools?

Yes. Keep using your current tools with AttackCompass.

What happens to my pentest data?

Client mode is commercial client-side encryption for sensitive fields against a hosted-storage adversary. Read the security page before adding client data — it explains what is sealed before upload, what structural metadata remains server-readable, and what happens when you export or delete data.

How do cancellation and refunds work?

A trial without billing consent expires without a charge. Paid users can cancel anytime through the Stripe customer portal. If you need the portal link or help canceling, email [email protected]. For refund rules, see the Refunds page.