After deploy, before the first payment
Deployed? Scan it first.
Twelve checks in about 40 seconds: a key leaking in your JS bundle, a path you forgot to close, a checkout redirect still pointing at localhost, a missing privacy page. Every finding comes with evidence you can check yourself: the file, the path, the status code.
What it reads
Twelve things you can’t see from here.
They only show up the first time a stranger, a crawler, or a payment reviewer opens your site.
Each check either passes, fails with evidence, or reports honestly that it could not run. It never guesses: a check that could not complete is marked as such and does not drag your score down.
The difference
What a chat window can’t do.
A chat window can hand you a checklist. It can’t read your files, and it can’t give you the same answer twice.
| A chat window | LaunchGate | |
|---|---|---|
| What it can see | The text you paste. It can’t read the bundle your server returns, the .env file, or your response headers. | Fetch, enumerate and read: every same-origin script, 14 known paths, TLS and response headers. |
| Repeating it | A different answer each time. Sometimes it misses a finding, sometimes it invents one. | The same 12 rules, the same verdict, with a rules version stamped on the report. |
| Proving it | Advice in a chat log. Nothing you can hand to a client. | Every finding carries the exact value that triggered it: the file, the path, the status code. |
| Every deploy | Restate the whole context, then hope it remembers. | A stable report link you can rescan after each deploy and compare. |
If a chat window is genuinely enough for you, don’t buy this. It is built for the case where you need the answer to be the same tomorrow, and to survive someone else reading it.
What you get back
Here’s the report.
A Stripe live key is inside your public JavaScript
Checkout success URL points at localhost
No privacy policy or terms page found
The verdict comes first
One line up front: can you take money today, and if not, which few things have to change.
Every finding carries its evidence
The file name, the matched value, the status code. You can verify each one yourself in a minute.
The fix list is ordered
Blockers first, then the things that quietly cost conversions. Each with an effort estimate.
Printable, and shareable
Save it as a PDF for a client, or send the link. Whoever opens it needs no account.
Pricing
Free to check. Paid to fix.
The free version shows the verdict and all the evidence. You pay for what to change.
Free
$0 / forever
- All 12 checks, one verdict
- Full evidence for every finding
- One fix step unlocked, so you can judge the quality
- 5 scans per day, no account
Pro
$19 / month · or $149 a year
- Every fix step, for every finding
- Unlimited scans and rescanning after each deploy
- Scan history so you can see what regressed
- The PDF export carries every fix step; a free report exports locked
- 7-day trial, cancel from the billing portal
Single report
$29 one-off
- One full report, fully unlocked
- No subscription, no renewal
- Valid for 12 months
- For a one-time launch you will not repeat
Prices in USD. Payment, tax and invoicing are handled by Creem as merchant of record.
Questions
Still wondering?
What exactly does it do to my site?
Only what a visitor’s browser would do: plain GET requests for your page, the scripts that page references, and 14 well-known paths. It never logs in, never submits a form, never sends a write request. Private and internal addresses are refused before a connection is made.
Will it find everything that is wrong?
No, and any tool that claims so is lying to you. It does not execute JavaScript, so content rendered client-side is invisible to it — which is a real limitation for the legal-pages check on single-page apps. What it does not check is written on the report rather than quietly skipped.
What do you keep?
The URL, the findings, and the values that triggered them. Your IP address is stored only as a salted hash, for rate limiting. Reports are deleted after 90 days. No page content is retained beyond the short evidence strings shown on the report. The privacy policy spells this out in full.
Can I scan a site I don’t own?
No. Scanning someone else’s site without permission is what the terms forbid, and it is also just a bad idea. Use it on your own deploys, or on a client site you have written permission to test.
How do refunds work?
Ask within 14 days and you get your money back, no interrogation, as long as the report has not been used for a launch decision you are now reversing. The full policy is on the refund page.
Does it work on staging URLs behind a password?
Not yet. Authenticated scans need a different security model, and shipping a half-safe version of it would be worse than not having it.