Prototype audit
Prototype audit: what will break in production, before your customers find out.
A senior developer reads your code and hands you, within days, the list of flaws, risks and the plan to go to production. Quoted and fixed before we start, and credited to the build if you continue with me.
What I check
- Data access: Supabase rules (RLS), isolation between customers
- Authentication and sessions
- Exposed secrets and API keys
- Payments: Stripe, subscriptions, webhooks
- AI calls: costs, limits, prompt injection
- Errors, backups and monitoring
- Performance and search visibility
- Personal data (GDPR)
What you get
- A written report, issues ranked by severity: critical, important, nice to have.
- A takeover plan: harden, migrate or rebuild, with an estimate per milestone.
- A debrief call to answer your questions.
- The report is yours: you can hand it to another developer.
Also useful when…
- your developer or agency has left, and nobody knows what state the code is in;
- an investor wants a technical review before committing.
In practice
- Read-only access to your repository is enough.
- Non-disclosure agreement signed on request, before any access.
- If the audit finds nothing serious, I tell you so, and that’s good news.
What I build on the same stack: my products · taking over an AI prototype