Fixed-price project

Security and launch audit for apps built with AI tools

I read the code of an app built with an AI tool, find what is unsafe to launch, and rank it by how serious it is. A written report starts at $250 and takes 3 days. Fixes cost more.

Price
From $250
Delivery
3 days
at the Audit report tier
Packages
3 tiers

Who it is for

Who this helps

  • Founders who built an app with an AI tool and plan to put real users, data or payments on it.
  • Small teams with an AI-built prototype and no senior engineer to read the code.
  • Owners who paid someone to build the app and want an independent check before launch.
  • Teams that need a clear picture before a demo to a big customer or a hand-over to a new developer.

Signs

Signs you need this

  • You cannot say who is allowed to see which data in the app.
  • Keys or passwords were pasted into code or chat to get something working.
  • The app runs on a laptop or in a preview, but nobody has planned the real deploy.
  • Nobody on the team has read most of the code.
  • There are no error alerts, so a customer would tell you about the first failure.

Scope

What I do

  • Secrets and keys

    I search the code and its history for keys, tokens and passwords. I check that secrets live in environment settings and not in files in the repository, and that debug mode is off in production. If a key was ever committed, treat it as exposed and replace it, even if the file was cleaned up later.

  • Login and permissions

    A login page does not mean each user sees only their own data. I follow every route and API call that takes an id and check whether the code asks who may see that record. OWASP lists broken access control first in its 2025 Top 10, so I look at this first.

  • Database rules

    I look at who can read and write each table. If your app talks to a hosted database straight from the browser, I check that row-level rules exist on every table. I also look for missing unique indexes and foreign keys, how data is deleted, and whether development and production use separate databases and keys.

  • Errors, logs and payment code

    I read how the code handles failures: swallowed errors, no alerts, no health check. OWASP also lists mishandling of exceptional conditions and logging and alerting failures in its 2025 Top 10. If you take payments or use webhooks, I check that the code verifies who sent each request, ignores repeat events and moves slow work to a queue.

  • Deploy and backups

    I check how the app gets from your laptop to a live server: environment settings, separate keys for production, a way to roll back, a health check, and whether a backup has ever been restored. A backup that nobody has tested is only a hope.

  • Code structure and handover

    I check whether another developer could work in the code: folder layout, repeated code, outdated packages with known problems, and whether the parts that handle money, access and deletion have any tests. In the larger packages I clean this up and write a handover guide.

Packages

Pick a package

Fixed price in US dollars. Each package lists what is included.

Audit report

$250

3 days · 1 revision

You want to know where you stand before you decide what to fix.

  • A written report in plain English
  • Security, data and deploy risks ranked by how serious they are
  • A fix plan, in the order I would do the work

Audit and fixes

$900

10 days · 2 revisions

You want the worst problems gone before you launch.

  • The audit and the ranked report
  • Fixes for the most serious problems: keys, login, database rules and errors
  • The fixes made in your repository

Production-ready

$2,200

21 days · 3 revisions

You want the app cleaned up and ready for real users and for the next developer.

  • Fixes for the serious problems found in the audit
  • A clearer code structure that another developer can work in
  • A safe way to deploy, with backups and monitoring
  • A handover guide for you and your team

Process

How it works

  1. Step 1

    Send your code

    You send a GitHub or GitLab invite, or a zip file. You tell me what the app does, which AI tool built it and where you plan to launch. Tell me what worries you most. Keep live passwords and production keys out of what you send.

  2. Step 2

    I audit it

    I read the code and check the six areas above, starting with the parts that handle users, money and data. I work from the code, not from your live servers.

  3. Step 3

    I fix and clean up

    In Audit and fixes and Production-ready, I fix the most serious problems first. In Production-ready I also clean up the structure and set up a safe deploy, backups and monitoring.

  4. Step 4

    You get the results

    You receive a written report that ranks each problem by severity. With the fix packages you also get the changes in your repository. Production-ready adds a handover guide for you and your team.

Proof

Related work and reading

FAQ

Questions about this project

I check six areas: secrets and keys, login and permissions, database rules, error handling, deploy and backups, and code structure. I read the code that handles users, money and data with the most care. I work from the code only, so I do not need access to your live servers.

It is a written document in plain English. Each finding says what is wrong, where it is in the code, why it matters and how to fix it. Findings are ranked by how serious they are, and a fix plan puts them in the order I would do the work.

I need a link to your code (a GitHub or GitLab invite, or a zip file) and a short note on what the app does, which AI tool built it and where you plan to launch it. Tell me what worries you most. Keep live passwords and production keys out of what you send.

A full rewrite, new features and a live attack test of your running site are not included. A review also cannot promise that your app has no flaws. The Audit report package finds and ranks problems but does not fix them. Fixes start with the Audit and fixes package.

No, I will not rewrite your whole app. I start with the risky parts and leave working code alone. If a part cannot be saved, I explain why and quote it before I touch it.

It does not fit if you want new features built, a full redesign or a rewrite in another language. It also does not fit if you cannot share the code. A weekend toy with no real users and no private data may not need a paid audit. Tell me your plan and I will say which package fits.

I review apps from Lovable, Bolt, Cursor, Claude Code, v0, Replit and similar tools. Laravel and PHP are my strongest stacks, and I also review JavaScript and TypeScript apps. Tell me which stack your app uses.

Pick Audit report if you only want to know where you stand. Pick Audit and fixes if you want the most serious problems fixed: keys, login, database rules and errors. Pick Production-ready if you also want a cleaner structure, a safe deploy, backups, monitoring and a handover guide.

Need something different?

If your work does not fit these packages, tell me what you need and I will reply with a plan.

More projects

From $500

Laravel MCP server

An MCP server for your Laravel app, so an AI agent can use only the tools you allow.

  • Token auth, scoped tools
  • Source code and setup guide
  • Works with clients like Claude

From $250

Claude Code setup

Set up Claude Code as a small team, with your rules, sub-agents and skills.

  • Rules, permissions, sub-agents
  • Skills and MCP servers
  • Guide for your team

From $300

HubSpot integration

Contacts, companies and deals kept in step between Laravel and HubSpot.

  • Two-way sync with retries
  • Failed records logged and retried
  • Code in your repository

See all services