Studio
Black Friday

Up to 70% off kits30% off services

Ends in
All Tools
Product · Free checklist

Code Audit Checklist

Fifteen yes-or-no questions for founders with an app already built, by a freelancer, an agency, an AI app builder or your own team. No code reading needed. Five minutes, a score across ownership, shipping, security, quality and product health, and what to fix first. Answers stay in your browser.

Who built the app? (optional)

1.Ownership and access

  1. Is the code in a repository your company owns, not a developer’s personal account?
  2. Are hosting, database, domain and app store accounts in your company’s name?
  3. Do you know where every API key and password lives, and can you rotate them?

2.Can you ship it?

  1. Could a new developer run the app on their machine in under an hour from the README?
  2. Is deploying automated, from the main branch, without someone copying files to a server?
  3. Is there a staging or preview environment where changes are checked before customers see them?

3.Security and data

  1. Is the database backed up automatically, and has anyone restored a backup to prove it works?
  2. Do login, passwords and sessions use a proven library or service rather than hand-written code?
  3. Is every request checked on the server, so one customer can never see another customer’s data?
  4. Have dependencies been updated in the last three months, with no known critical vulnerabilities?

4.Quality and visibility

  1. Do errors in production reach a person automatically, through Sentry or similar?
  2. Are sign-up, login and payments covered by automated tests that run before each deploy?
  3. Can someone explain where the main parts of the code live without reading all of it?

5.Product health

  1. Can the core flow be completed with a keyboard alone, and does it pass an automated accessibility check?
  2. Do the main pages load in under about 2.5 seconds on a phone?

Want a developer to read the code?30% OFF

Our $349$499 Product Scope can be a code audit: we read the repo, run it, check security, data and deploys, and tell you plainly whether to continue, fix or restart, with a fixed price for each path. The fee comes off the build.

Why half-built apps stall

When a founder brings us an app someone else started, the code is rarely the first problem. These are the gaps we find most often, usually in this order:

  • The repo or hosting is in someone else's name. The developer went quiet, and nobody else can deploy, or even log in.
  • Nobody else can run it. No README, secrets on one laptop, and a deploy process that lives in one person's head.
  • Backups that were never restored. The setting is on, but nobody knows whether the data would come back.
  • Data hidden in the screen, not on the server. Fast builds, and AI-generated ones in particular, often return every customer's records from the API and only filter them in the browser.
  • No tests on the money paths. Every change risks sign-up, login or checkout, so changes slow to a crawl.

Planning the next version? Write it down with the free PRD template and sort it with the MoSCoW prioritization tool.

Frequently asked questions

What the checklist covers, how it scores and what to do next.