Production readiness audit. For web apps and SaaS systems built with AI: Claude Code, Cursor, Lovable or other tools.
You built it with AI. Before customer data goes in, get it tested.
59 checks across 7 areas, from permissions to the AI agent. In 5 working days you know what is red and what to fix first.
Book the free checkLoad test. Before it opens to traffic, a bridge is tested.
Sample report.
Made-up data.
- Document
- Test report
- Application
- Booking manager
- Stack
- Next.js and Supabase
- Checks run
- 59, across 7 areas
| No. | Area | Rating | Main finding | Check |
|---|---|---|---|---|
| 1 | Data and permissions | Red | One customer can read another customer's bookings | 1.3 |
| 2 | Schema and migrations | Red | The database cannot be rebuilt from the repository | 2.1 |
| 3 | CI and tests | Amber | No tests on payments | 3.3 |
| 4 | Environments | Amber | Staging sends emails to real customers | 4.2 |
| 5 | Observability | Amber | Errors are reported by customers | 5.2 |
| 6 | Backups, secrets and GDPR | Red | Backups on, restore never tested | 6.1 |
| 7 | AI agent | Green | Written rules, destructive commands blocked | 7.4 |
| Outcome | Not ready for real data: 3 areas red, 3 amber, 1 green | |||
1
Public incidents, each with its source.
It has already happened
Three incidents involving apps built with AI tools. None of them took a sophisticated attack.
LovableMay 2025
A scan of 1,645 showcased apps found 170 with data anyone could read, because database permissions were missing or weak (CVE-2025-48757).
Base44July 2025
Knowing a private app's public ID was enough to get in. The flaw was fixed within 24 hours.
Automated scanners check that permissions exist. Whether they are right for your app only shows when you try them with real users, one per role.
2
59 checks, 13 of them blocking.
What I check
Every check passes or fails. If a blocking check fails, the area is red.
| No. | Area | Goal | Checks |
|---|---|---|---|
| 1 | Data and permissions | No user can read or change data that isn't theirs, not even by calling the database directly. Three sample checks
|
10 |
| 2 | Schema and migrations | The production database can be rebuilt from the repository, and every change goes through a versioned file. Three sample checks
|
8 |
| 3 | CI and tests | Nothing reaches production without automated checks that test behaviour. Three sample checks
|
8 |
| 4 | Environments | You can try a change without touching customer data, and roll back in minutes. Three sample checks
|
6 |
| 5 | Observability | A problem reaches you before a customer reports it. Three sample checks
|
8 |
| 6 | Backups, secrets and GDPR | Data can be recovered, keys don't leak, and every piece of personal data has an expiry. Three sample checks
|
11 |
| 7 | AI agent | The agent writing the code works within the limits of a developer who has just joined. Three sample checks
|
8 |
| Total | 59 |
3
Working days.
Five days, from access to report
The audit reads and changes nothing. You can keep developing while I work.
Day 0
Kickoff
A 30-minute call. You give me read-only access to the repo and the database. We sign a confidentiality agreement and a data processing agreement.
Days 1, 2 and 3
Analysis
I run the 59 checks with automated scripts and manual review. I try the permissions with test users, one per role and per customer.
Day 4
Report
A rating for each of the 7 areas, the 10 most serious problems in order, and an estimate for fixing them. With it come the skills, the rewritten agent instructions and the ready-made tickets.
Day 5
Final call
One hour to go through the report together. If you want to continue, you get a fixed price for the hardening.
4
Prices in euros.
Pricing
Fixed price, agreed before we start.
| Service | Duration | Price |
|---|---|---|
| CheckYou show me the app on a video call. I tell you which areas I would look at first and whether you really need the audit. | 30 minutes | €0 |
| AuditA report with the rating of the 7 areas and the 10 most serious problems. For your agent: a set of skills, the instructions file rewritten (AGENTS.md or equivalent) and tickets ready for it to work through. Final call included. If you go on to the hardening, I deduct it from the price. | 5 working days | €790 |
| HardeningI bring every area to green with changes you can read and approve one by one. At the end you have automated checks, a test environment, monitoring and a tested restore. | 2 or 3 weeks | from €2,500 |
| MaintenanceMonthly review of database changes and releases, a test restore every three months, critical updates. | Monthly, cancel any time | from €250 per month |
It starts with the check: 30 minutes, free. Book the free check
5
What I don't do
- New features or rewrites of the app.
- Certifications such as ISO 27001 or SOC 2.
- Legal advice on the GDPR. The technical side, yes: data retention, deletion, access.
- 24/7 on-call.
- Apps without a GitHub repository.
6
About me
I'm Diego Castronuovo, a platform engineer with 15 years of experience in cloud systems and application scalability. My job is keeping production systems running: Kubernetes, Terraform, PostgreSQL, release pipelines, monitoring.
I work with AI agents like Claude Code every day. I know what they do well and where they need limits that don't depend on their attention.
This service grew out of a review of a business app built almost entirely with an AI agent: the product worked, the safety nets were missing.
If your team wants AI agents working on production, in your own cloud, see AI agents for engineering teams.
For any other engineering work, by the day or at a fixed price, see freelance platform engineering.
7
Frequently asked questions
Do I have to give you access to production?
Read-only and time-limited. Before starting we sign a confidentiality agreement and the data processing agreement the GDPR requires. When the work is done you revoke the access.
I used Lovable. Is that still fine?
Yes, if the project is connected to GitHub. Database, permissions and backups are checked the same way as in an app written with Claude Code or Cursor.
Do I have to stop developing during the audit?
No. The audit reads code and configuration and changes nothing.
What changes for me after the hardening?
You keep building with your agent. The rules and checks stay in the repository: if a change exposes one customer's data to another, it is stopped before it reaches production.
8
Start with the free check.
30 minutes on a video call. You show me the app and I tell you which areas I would look at first.
Book the free check