From Prototype to Production: The 30-Minute Security Pass for AI-Built Apps

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

From Prototype to Production: The 30-Minute Security Pass for AI-Built Apps

Short answer: the day you ship, you don't need a security department — you need a sequence. Run a free outside-in mini-scan (minutes 0–5), order the full scan and read real evidence (5–10), spend the bulk of the half hour fixing what it found (10–25), then rescan to prove the fixes and set up monitoring so next month's deploy doesn't quietly reopen everything (25–30). Each step below says what it can and can't see, because a pass you understand beats a score you don't.

Before the clock starts

One rule governs the whole half hour: every check here is outside-in. Scanners look at your app the way a stranger on the internet does — no login, no source code. That's exactly the view an opportunist attacker gets, which makes it the right first pass. It also means these steps cannot see behind your login, inside your database rules, or into business-logic flaws. Ship-critical apps eventually need those reviewed too; nothing in this workflow pretends otherwise.

Minutes 0–5: The free mini-scan

Start with the widest cheap net. PreShipIt's free mini-scan runs a fast subset of the full check catalog against your live URL: TLS certificate and protocol state, the HTTP→HTTPS redirect, the headline security headers (HSTS, CSP, clickjacking, MIME-sniffing, referrer and permissions policies), cookie flags, technology disclosure, and the two highest-severity probes — a publicly reachable .env file or .git directory.

You get a score, severity counts, and the titles of what it found. That's deliberately a teaser: it's enough to know whether you have a five-minute problem or a five-alarm one, and it costs nothing but the URL. Attest that the app is yours (the same ownership affirmation every PreShipIt scan requires) and run it.

Minutes 5–10: The full scan

If the mini-scan found anything — or if you're actually launching, which is reason enough — run the full $29 scan. The differences that matter in this window:

Read it in priority order. The top of the report is the stuff that's both exposed and consequential; the tail is hygiene. Your fix list for the next fifteen minutes comes from the top.

Minutes 10–25: Fix, in the scanner's priority order

Most findings in AI-built apps collapse into a handful of fixes you've probably seen before: add the missing security headers (usually one config block), set the cookie flags, close the exposed file or endpoint, rotate anything that was ever public — remember, a secret that shipped is a secret that's out; deleting it from the repo is step two, rotating it is step one. Work the list top-down and don't gold-plate: the goal of this window is eliminating known exposure, not achieving elegance.

If a finding surprises you, the report's evidence shows what the scanner actually saw. Trust the evidence over your mental model of the deploy — the deploy is what it is, not what the build log said.

Minutes 25–30: Rescan, then make it stick

Rescan the same URL. A fix you haven't verified is a hope. The rescan confirms the findings actually closed, and your dashboard keeps the score history — the trail of scans and deltas per target — so "we fixed it" is a record, not a memory. One-click rescan exists for exactly this step.

Then close the loop with monitoring. The prototype-to-production gap reopens a little with every deploy: a header dropped in a config refactor, a debug page that slipped back in. PreShipIt Monitor ($49/month) rescans weekly and alerts you when new findings appear or your score drops — the difference between learning about an exposure from an email and learning about it from an incident. If you're shipping once and freezing the app, the rescan may be enough. If the app is alive, monitoring is the step that makes the other twenty-nine minutes durable.

What this pass deliberately leaves out

Thirty minutes, one workflow: scan small, scan fully, fix what matters, prove it, and watch it. That's the whole distance between a prototype that works and a production app you'd defend.

Related: The 10-Minute Pre-Launch Security Pass — the manual, terminal-and-curl version of this workflow, for when you want to run the probes by hand.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report