Deliver the report you already wrote
Upload the PDF for your client and drop in the Burp Suite XML, Nuclei, JSON or CSV export behind it. Burp issues and Nuclei HTTP results keep their original request, so they're ready to replay.
Deliver every pentest report through a live remediation portal, with automated, scope-enforced retests that take minutes instead of billable days.
No card required · unlimited client users
Works with the tools you already use
Report delivery
Stop sending password-protected ZIPs. Upload the PDF and your client downloads it in the same portal where every finding updates live, so the report is never out of date the day after you send it.
How it works
The weeks after delivery are where findings stall and retests eat your margin. Closeout owns that stretch.
Upload the PDF for your client and drop in the Burp Suite XML, Nuclei, JSON or CSV export behind it. Burp issues and Nuclei HTTP results keep their original request, so they're ready to replay.
The client acknowledges the exact hosts and testing window inside the portal. No acknowledgement, no retests. It's enforced in code, not policy.
Engineers hit “We've deployed a fix”. Closeout replays the proof from our fixed server IP, rate-limited, and judges the response against your signature.
The engine never closes findings on its own. You review the evidence, confirm, and the client downloads a dated letter for their auditor.
Security
A service that replays attack traffic has to be paranoid. Here's what keeps it on a leash.
Read the full security overview, including what isn't done yet →Every retest is checked against the client-acknowledged host list and testing window before a single packet leaves.
Targets are resolved once, every address is validated, and the connection is pinned. Private ranges and cloud metadata are unreachable.
Session tokens in proof requests are encrypted with a per-engagement key (AES-256-GCM, row-bound). The API never returns them.
Expired sessions, WAF blocks and 5xx responses come back inconclusive, never fixed. A human confirms every closure.
Postgres Row-Level Security confines every query to one firm. A missing WHERE clause returns nothing, not someone else's findings.
Every retest records who asked, the verdict and why, and which IP the target resolved to. The application role can't edit history.
Pricing
Billed monthly in EUR or USD · plus VAT where applicable · cancel anytime
$49/mo
$199/mo
$449/mo
Founding firms
We're opening Closeout to ten pentest firms that want a say in what it becomes. No sales calls and no demos: you use it on real engagements and tell us what's missing, by email.
What we ask in return: use Closeout on at least one real engagement, and tell us honestly what works and what doesn't.
No. Keep writing reports in Burp, SysReptor, Ghostwriter or Word. Closeout takes over at delivery: upload the PDF and the portal, retests and attestation follow.
An emailed PDF is out of date the day after you send it, and you never know who opened it. In Closeout the client downloads it next to the live status of every finding, you see who downloaded which version and when, and the attestation cites the exact file by its SHA-256.
Retests only reach hosts the client acknowledged, inside the testing window, from our server's fixed IP (listed on our security page), one request per second per host. Redirects are never followed, private and metadata addresses are blocked, and a human confirms every fix.
Headers and bodies are encrypted with a per-engagement data key and only decrypted inside the isolated retest worker. The API shows header names only, and evidence is redacted before anyone sees it.
Never. Client users are unlimited on every plan, so the portal spreads the word for you.
Six months free, then 50% off for as long as you stay subscribed, and your requests go first. The only thing we ask is honest feedback by email after using Closeout on a real engagement. No calls, no case study you didn't agree to.