Exposed API keys
Stripe, OpenAI, and database service-role keys committed in code or shipped to the browser bundle. Often present in git history even after "fixes."
For founders shipping AI-built software
AI made the prototype. We make it shippable. We audit AI‑generated codebases, harden them for real users, and stay on as a fractional engineering owner if you need one.
01 — Prototype vs production
AI tools are excellent at the first 80%. The remaining 20% — auth, data, deploys, failure modes — is where companies get hurt. Most "vibe-coded" apps look fine until the first real customer.
prototype
production
02 — What we usually find
These aren't theoretical. This is what comes back after a two-day audit on a typical Cursor / Lovable / v0 / Replit Agent project that's about to ship.
Stripe, OpenAI, and database service-role keys committed in code or shipped to the browser bundle. Often present in git history even after "fixes."
Sessions that never expire, JWTs verified on the client, password resets that leak account existence. Account takeover is a one-line request away.
"If admin, show button" — but no row-level security on the database. Any authenticated user can read or modify any other user's data with curl.
No automated snapshots, no restore drill, no point-in-time recovery. One bad migration or one rm -rf and the company is over.
Code on the laptop differs from staging differs from production. No one is sure what's running. Rollbacks involve guesswork.
First sign of a problem is a customer email. Errors swallowed in try/catch, console.log on the server, no Sentry, no alerting.
Files that grew by accretion, prompt by prompt. Three slightly-different ways of doing the same thing. Each new feature breaks two old ones.
The honest answer is sometimes: don't keep building on this. We'll tell you when that's true, and what a tactical rewrite looks like.
03 — How we work with you
Fixed scope, fixed price, no retainers you can't escape. Every engagement starts with a conversation about whether you actually need it.
Best for founders with an AI‑built MVP about to put real users or paying customers on it.
Best for apps going live with users, payments, or customer data — and you need it solid in a few weeks.
Best for teams running production software without a senior technical owner — yet.
Also available: Technical due diligence for investors and acquirers reviewing AI-built codebases.
04 — Method
We are calm, we don't gatekeep, and we don't rewrite things that work. If your codebase shouldn't be maintained, we'll say so on day three — not three months in.
30-min call. Read-only access to repo, hosting, database, and analytics. We sign your NDA before you send anything.
Two senior engineers walk the codebase, deploy path, and data layer. We don't run tools and call it a report.
Prioritized findings with severity, effort, and concrete fixes. Written for a founder, with a deeper appendix for engineers.
You either green-light the sprint, hand it to your team, or — if appropriate — we tell you to stop and rebuild a slice.
Optional monthly engagement: re-audits, on-call, architecture calls. Predictable cost. Cancellable any month.
05 — Pricing at a glance
We scope tightly so you can budget honestly. If a project is going to cost more, we tell you before we start it.
06 — Who we work with
You don't need to be technical to work with us. You do need a codebase you can give us read access to.
Solo founder
You can't tell whether the app is dangerous to put real customers on. You want a clear answer in a week.
Small agency
You want a senior pair of eyes on the code before delivery, and a written report that protects your relationship.
Investor / acquirer
You need an honest read on the engineering risk before a term sheet or before close. We don't pull punches.
07 — Frequently asked
Ready when you are
We'll write you a short, honest assessment in a week. If we don't think you need an audit, we'll tell you that for free.