Vibe-coded app rescue and AI code audit Project rescue

Your app was built with Lovable, Bolt, Replit, Cursor or v0 on Supabase or Firebase, and now it loses orders, exposes customer data, or has been stuck at “75% done” since the contractor stopped replying. We start with a 5-day diagnosis: we check the code, access rules, keys and payments, find the holes and tell you plainly what to save, what to rewrite and what it costs.

Price
from $1,500
Timeline
from 1 week

Price and deadline are fixed in the contract before work starts

What is included

  • 01A 5-day diagnosis: audit of the code, database and access
  • 02Security check: Supabase RLS policies or Firebase security rules, secret keys in browser code, public storage
  • 03Money and orders check: payments, payment-provider callbacks, lost records
  • 04Recovery of access and code: server, domain, database, app stores
  • 05A plan: what we save, what we rewrite and in what order
  • 06The price and timeline of every step before you commit to anything
  • 07Stabilization: critical bugs, vulnerabilities, monitoring
  • 08Relaunch: refactoring, automated tests and the features you were promised

Who it is for

  • Founders whose app was built with AI tools and no engineers, and started breaking or leaking under real users
  • Companies whose contractor vanished while the code, server and domain were still in the contractor’s name
  • Businesses where the payment went through but the order never appeared
  • Projects that have been “almost done” for months and never reach launch

Three levels and prices

Pick the level that fits the task and budget. The exact scope is assembled in the configurator and fixed in the contract.

Diagnostics

Code and access audit, rescue plan in 5 days

$1,500–3,500

≈ UZS 18M · from 1 week

Stabilisation

Critical bugs, vulnerabilities, monitoring

$6,000–15,000

≈ UZS 72M · from 4 weeks

Relaunch

Refactoring, automated tests, new features

$15,000–50,000

≈ UZS 180M · from 10 weeks

UZS amounts are indicative, at the Central Bank of Uzbekistan rate on 14.11.2026. Contracts are in USD, or in UZS at the rate on the invoice date.

In detail

Does this sound familiar?

The app came together fast: AI wrote the code, the demo looked finished, the first customers arrived. Then the failures began. A payment goes through but there is no order. A customer sees someone else’s data. A secret key sits in the website code, where anyone who opens the browser’s developer tools can take it, or the database answers anyone who holds the public key. Every fix breaks something else, and the contractor writes “almost there” for months, then goes silent. You are not alone: security researchers have repeatedly found AI-built apps with databases open to the whole internet. In most cases a project like this can be brought to stable production — if you start with a diagnosis rather than more blind fixes.

What happens during the 5-day diagnosis

On day one we get access and take inventory: where the code lives and who owns the domain, the server, the database and the app store accounts. Day two is security: is the database exposed, are Supabase row-level security (RLS) policies or Firebase security rules actually in place, which API keys ended up in browser code or the repository, are permissions checked on the server and not only in the interface. Day three is money and data: do payment callbacks arrive, are orders created twice, do backups exist. Day four covers code quality, outdated libraries and tests. On day five you get a report in plain language: what is broken, what it risks, what we save, what we rewrite, and the cost of each step.

What drives the price: three tiers

Diagnosis is the entry point for every rescue: an audit of code and access, plus a plan. Its price depends on the size of the product and the number of systems around it, not on how many problems we find. Stabilization closes what is dangerous today: critical bugs, lost orders and vulnerabilities, plus monitoring, so that an outage raises an alert before customers notice it. Relaunch is for when the product has to grow: refactoring, automated tests on sign-in and payments, and the features the previous contractor promised. Documentation, performance work and getting the app back into the App Store and Google Play are priced as separate line items. After the diagnosis, the next step is your call.

Mistakes that make a rescue more expensive

The first is hiring yet another contractor to “just finish it” without an audit: new changes on top of code nobody understands multiply the breakage. The second is rewriting everything from scratch out of frustration: often most of the product can be kept, and the diagnosis shows exactly which part. The third is fighting the previous contractor before the domain, server and database are in your name: recover access first, settle accounts later. The fourth is sitting on a leak: if keys may have been exposed, they are rotated on day one, not after the release. The fifth is running ads into an app that loses payments: every such day costs money and reputation.

What the contract says

2%

for every day we are late

If we are late, your invoice drops by 2% a day, up to 10% of the contract. So we only name deadlines we can keep.

1

company per niche per city

For a year we do not take on your competitor in your city. What we build for you does not end up next door.

10%

refund after an outside review

Bring your own engineer. They check the code against the contract. If a contracted item is missing, we refund 10%.

Questions

How much does a project rescue cost?

We start with a diagnosis from $1,500, a 1-week engagement in which the code and access audit takes 5 working days. You get a list of problems ranked by risk, a plan and the cost of the fixes. Stabilization and Relaunch cost more; their prices are in the tier table. Scope and price are fixed in the contract only after the diagnosis, once it is clear what needs fixing.

How quickly can you start, and when do we see results?

The diagnosis starts as soon as we have access to the code and server; if there is no access, recovering it comes first. The report and plan arrive after 5 working days. Stabilization and relaunch run under a contract with a deadline: you see a working version every two weeks, and for every day of delay the invoice drops by 2%, capped at 10% of the contract value.

Should we rewrite from scratch or fix what we have?

We decide on the facts from the diagnosis. If the data model is sound and the bugs are local, we fix: faster and cheaper. If access rights, payments and data are tangled at the architecture level, patching costs more than a new core, and the report says so. Most often the answer is in between: we keep the interface and part of the logic and rewrite the dangerous parts.

The contractor disappeared and we have no source code or access. What now?

Do not delete anything, and avoid arguing over chat. We regain control through you as the owner: the domain via the registrar, servers and cloud via the provider, apps via the App Store and Google Play accounts. If there is no source code at all, we assess what can be recovered from the running product and the database and price a rebuild. Everything recovered is put in your name.

Our app was built with Lovable, Bolt or Cursor and no developers. Will you take it on?

Yes, this is a common case. AI-written code often looks tidy, but the same gaps come up again and again: the database is exposed, row-level security is off, API keys sit in browser code, permissions are checked only in the interface, and payment status is taken from the client side. We know where to look and check all of it in the first days of the diagnosis.

Are we obliged to continue with you after the diagnosis?

No. The report, plan and estimate are yours to take to any team. We do not stop your product during the diagnosis. If we continue together, price and deadline are fixed in the contract, and your own engineer can check the code against it: if they find an unfulfilled item, we refund 10%. Bugs in our work are fixed free of charge for the lifetime of the product.

Other solutions

Practice: Support & Growth