For boutique pentest firms & independent testers

The report isn't the finish line. Closeout is.

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

getcloseout.tech/portal/acme-web-q4
Acme web app, Q4
Redline Security · 3 findings
0%
  • F-001IDOR on /api/invoices/:idOpen
  • F-002Reflected XSS in /searchOpen
  • F-003Missing rate limit on loginOpen
GET https://app.acme.test/api/invoices/1002
· waiting for client to ship a fix

Works with the tools you already use

Burp Suite XML
Nuclei
CSV & spreadsheets
JSON
SysReptor
Ghostwriter
Jira
Linear
GitHub Issues

Report delivery

The report and the remediation, in one link

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.

Proof of delivery
See who downloaded which version, and when. No more “we never got the report”.
Versions, not attachments
Re-issue it after retests as v2, v3. Delivered versions are locked, so the record holds up.
Sealed at rest, up to 200 MB
Every PDF is encrypted with its engagement's own key. 180 pages of screenshots fit easily.
Tied to the attestation
The attestation letter cites the report by its SHA-256, so an auditor can match the two.
Deliver your next report with Closeout →
Acme Corp · Remediation portal
Web app and API pentest, Q4
Encrypted
v2Retest report
Acme – Pentest Q4 v2.pdf · 148 MB · 182 pages
Download
Uploading to the portal…
v1Initial report
Since the first report
8/ 14 closed
Attestation cites
SHA-256
4d0b0b82…1b7fd224
✓ matches v2

How it works

From PDF to verified fix in four steps

The weeks after delivery are where findings stall and retests eat your margin. Closeout owns that stretch.

  1. 01

    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.

    burp-acme-q4.xml✓ 14 findings
    findings.csvready
    export.jsonready
  2. 02

    Your client signs off on scope

    The client acknowledges the exact hosts and testing window inside the portal. No acknowledgement, no retests. It's enforced in code, not policy.

    app.acme.com*.api.acme.com
    Acknowledged by Ada (Acme) · Oct 14
  3. 03

    They ship a fix and click one button

    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.

    We've deployed a fix
    → retest queued · 1 req/s per host
  4. 04

    You confirm. They get an attestation.

    The engine never closes findings on its own. You review the evidence, confirm, and the client downloads a dated letter for their auditor.

    Remediation attestation
    F-001 CriticalVerified fixed
    F-002 HighVerified fixed
    F-003 MediumVerified fixed

Security

Built by people who'd try to break it

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 →
  • Scope is a hard wall

    Every retest is checked against the client-acknowledged host list and testing window before a single packet leaves.

  • DNS-rebinding proof

    Targets are resolved once, every address is validated, and the connection is pinned. Private ranges and cloud metadata are unreachable.

  • Credentials stay sealed

    Session tokens in proof requests are encrypted with a per-engagement key (AES-256-GCM, row-bound). The API never returns them.

  • No false 'fixed'

    Expired sessions, WAF blocks and 5xx responses come back inconclusive, never fixed. A human confirms every closure.

  • Tenant isolation in the database

    Postgres Row-Level Security confines every query to one firm. A missing WHERE clause returns nothing, not someone else's findings.

  • Append-only audit trail

    Every retest records who asked, the verdict and why, and which IP the target resolved to. The application role can't edit history.

Pricing

Pays for itself with two saved retest hours

Billed monthly in EUR or USD · plus VAT where applicable · cancel anytime

Solo

$49/mo

  • 1 tester
  • 5 active engagements
  • 100 retests / month
  • Encrypted report delivery
  • Branded client portal
  • Burp / Nuclei / CSV / JSON import
  • Scheduled regression checks
  • Attestation letters
Start free trial
Most popular

Firm

$199/mo

  • 5 testers
  • Unlimited engagements
  • 1,000 retests / month
  • Everything in Solo
  • Jira, Linear & GitHub ticket sync
  • Remediation SLA dashboard
Start free trial

Agency

$449/mo

  • 15 testers
  • Unlimited engagements
  • 5,000 retests / month
  • Everything in Firm
  • API access for scripts and CI
Start free trial

Founding firms

Shape Closeout. Pay half, for life.

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.

6 months free
The Solo plan from day one, with no card. Need Firm or Agency? Choose it under Billing and add a card: nothing is charged until the six months are up.
50% off for life
Your founding price stays for as long as you're subscribed. It's applied at checkout, no code needed.
Your requests first
What founding firms ask for goes to the top of the list, and you hear back from the person building it.
Async, always
Feedback by email, whenever it suits you. We'll never ask you for a call.

What we ask in return: use Closeout on at least one real engagement, and tell us honestly what works and what doesn't.

Apply for a founding spot

We only use these details to review your application. See the privacy policy.

Questions

Does Closeout replace my reporting tool?+

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.

Why deliver the report through Closeout instead of email?+

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.

Is it safe to let a SaaS replay exploit requests?+

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.

What happens to session tokens in stored requests?+

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.

Do my clients pay for seats?+

Never. Client users are unlimited on every plan, so the portal spreads the word for you.

What do founding firms get, and is there a catch?+

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.

Close your next engagement properly

Import a report, invite your client, and run your first automated retest in under ten minutes.

Start free trial