Run a security audit before your launch, not after the breach
You spend weeks on the landing page, the positioning, the launch post. The app behind it has never been tested by anyone who was not on the team. A security audit before launch costs ten minutes and catches what code review cannot: the view from outside.
By Théophile Louvart, founder of Porteur · Updated 16 November 2026 · Markdown
What a launch exposes
Before a launch, your app is visited by you and a handful of beta testers. After the launch, it is visited by everyone who follows the link, and everyone includes people who check for open admin panels, leaked API keys, and unprotected database tables.
- A Supabase table with row-level security disabled is invisible until someone queries it. An attacker knows how to query it.
- An API key in a JavaScript bundle has been there since the first commit. Nobody noticed because nobody looked.
- An /admin route that works without authentication has been fine because the only people who knew the URL were on the team.
- A debug endpoint that dumps environment variables was added during development and never removed.
These are not edge cases. They are the most common findings when a web app is scanned with an automated pentest tool like <a href="https://keybrum.com">Keybrum</a>.
What an automated pentest checks
An automated security scanner visits your app the way a stranger would. It reads the HTML, the JavaScript bundles, the source maps. It maps the API endpoints. Then it attacks them, one by one, following the OWASP Top 10 and the patterns that show up in real breaches.
<a href="https://keybrum.com">Keybrum</a> runs over 300 attack checks in under ten minutes. It tests for leaked secrets in client code, exposed database tables, broken access control, missing security headers, open admin panels, CORS misconfigurations, SQL injection, and server-side request forgery. Each finding comes with proof: the request, the response, and a command you can paste to reproduce it.
The scan needs nothing but the URL. No agent to install, no code to push, no CI pipeline to modify.
When to run it
Before the launch post
The day before you post on Product Hunt, Hacker News, or your newsletter. The launch sends traffic, and traffic includes people who test things you did not expect.
After every major feature
A new API endpoint, a new integration, a new user role: each one changes the attack surface. A scan takes ten minutes; a breach does not respect your release schedule.
In CI, on every deploy
Keybrum has a CLI and an MCP server. Wire it into your pipeline and every deploy gets a security report before it reaches production.
What a report looks like
A <a href="https://keybrum.com/check">free security check</a> takes your URL and runs the passive checks: leaked keys, exposed source maps, security headers, TLS configuration. The full scan adds the active attacks: it tries SQL injection, path traversal, IDOR, authentication bypasses, and server-side request forgery.
Every finding is classified by severity (critical, high, medium, low) and by who can exploit it (anyone on the internet, or any signed-in user). The fix section gives you the exact steps and, for apps built with AI coding tools, a prompt you can paste into your agent.
The common objections
"We'll do it after launch." The breach does not wait for your roadmap. The first scan is the cheapest one: before launch, you have no users to notify, no data to report, no reputation to repair.
"Our framework handles security." Frameworks handle the defaults. They do not handle the row-level security policy you forgot to write, the API key you left in the bundle, or the admin route you protected with a path prefix instead of authentication.
"We don't have the budget for a pentest." A <a href="https://keybrum.com/pricing">full automated scan starts at €49</a>. A manual pentest costs thousands and takes weeks. The automated scan covers the same OWASP categories and runs in minutes. For a product that is about to launch, the automated scan is the right tool.
Pre-launch security checklist
Run a scan
Go to <a href="https://keybrum.com/check">keybrum.com/check</a>, paste your URL, and read the report. Fix anything critical or high before the launch.
Check your environment variables
No secret should be prefixed with NEXT_PUBLIC_ or VITE_ unless it is meant to be public. Search your deployed bundles, not just your .env file.
Test every route without credentials
Open an incognito window and visit every URL you know. If anything loads that should not, you have a broken access control.
Review your database policies
If you use Supabase, check that every table has an RLS policy enabled. If a table has no policy, any authenticated user can read all of its rows.
Remove debug endpoints
Search your codebase for /debug, /admin, /api/health with verbose output, /graphql/playground, and any route that dumps configuration or environment.
Set the security headers
X-Frame-Options, Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options. These are one-time settings that block entire classes of attacks.
Security and growth are the same problem
A growth report tells you where traffic leaks. A security report tells you where data leaks. Both are about the gap between what the site presents and what a stranger actually sees.
The same launch that sends your first thousand visitors sends people who test your /admin path, your API without a token, and your storage bucket with a guessed URL. The growth work and the security work share a deadline: the launch post.
Run the <a href="https://keybrum.com">Keybrum scan</a> the day before. Read the Porteur report the day after. Ship with the two things a solo founder can actually control: a product that works and a product that holds.
Questions
Check my site, free
Run a free security check on your app before launch day.
- Free check, no card
- Read-only, your own accounts
- Readable by your agent
Read next
- GuideSEO before launch: the checklist for the week before
- GuideAn SEO audit checklist for a small site: forty checks in order
- GuideLaunching on Product Hunt: a checklist that fits a week
- GuideSEO before you launch: what to get right while the site is still small
- GuideWeb security and SEO: why a hacked site loses rankings
- GuideApp Store Optimization for a product: search inside the stores
- GuideThe best SEO audit tools, and which one a founder needs
- GuideA Claude SEO skill for your repository: what it should hold, and one to copy