Symptom

Anyone can call your login route a million times tonight.

Generated code answers every request it receives, as quickly as it can, for as long as somebody keeps asking. That is harmless until a route with a cost attached gets found, and the routes with costs attached are the ones every application has.

No rate limits anywhere

What it looks like

For a long time nothing, and then one of a short list of bad mornings: a sudden invoice from a mail or model provider, thousands of registrations under addresses nobody recognises, password reset messages delivered to your customers in bulk, or a site that has stopped answering because one caller is asking faster than it can reply.

Why it actually happens

A limit is something a person has to decide to add, and nothing in the code complains while it is absent. The routes that need one are the expensive or sensitive ones — sign-in, registration, password reset, checkout, upload, anything that calls a service you pay for — and they are also the routes that have to stay reachable without an account, which is precisely why they are what gets found.

How we find out which one it is

We inventory the publicly reachable routes and mark each one with what a call to it costs: money, mail sent under your name, a record created, work added to a queue. Then we send a deliberate burst at the ones that matter and record what happens — whether anything slows the caller down, what the platform does unprompted, and where the first thing gives way.

What the fix touches

A limit per route, keyed to the account where there is one and to the network address where there is not, with the costly routes set tighter than the rest. Validation is tightened in the same pass, since a request refused for being malformed never reaches the expense. Where a provider is involved we set a spending ceiling there too, so a mistake has a maximum rather than a bill.

Will real users hit the limit?
Not at the thresholds these routes need. A person signs in a handful of times a day and a script attempts thousands, so there is a wide band between the two, and we set the numbers from your own traffic rather than from a default somebody else chose.
Is this worth doing before I have many users?
The attempts do not wait for your users to arrive. Public routes are found by scanners within hours of a domain resolving, and a few limits added now cost less than the first invoice or the first bulk mailing sent to your customer list.
Does my host not handle this already?
Platforms absorb crude volume attacks and that is a real layer, but they cannot know that one particular route is expensive, or that a hundred sign-in attempts against one account is wrong. Those judgements are yours and they belong inside the application.

How it works

Audit

$199$349promo

You send a link, a repo, or both. We reproduce the problem, read the code, and record a short walkthrough: what's broken, why it broke, and what it takes to fix. You get written findings and a fixed quote.

Book my audit

Full Fix

Priced after the audit

Scoped from the audit and agreed before anything starts. We fix the cause rather than the symptom, and hand back something maintainable, with a written note on what changed and why.

Nobody can price this honestly before seeing the code. The audit is what makes a firm number possible.

The audit is a fixed price and you know it before you pay. Everything after it is quoted from what the audit actually found, and you approve the number before any work starts.

Why trust us with it

What we can show you is who does the work, what it costs, and how well we already know the failure you are staring at.

A desk at night, the walkthrough being recorded

A small agency, not a marketplace

This is run by a small web agency. The person who records your audit is the person who does the fix, so you're not being routed to an anonymous bidder.

$199$349promo

The audit stands on its own

Plenty of people take the findings and do the work themselves, or hand them to their own developer. That is a fine outcome and nothing is bundled to stop it.

Book my audit

Fixed price, agreed up front

You approve a number before work starts. If the job turns out harder than we estimated, that's ours to absorb, not a change order.

Built with one of these? You're in the right place.

Lovable
Lovable projects usually break at the Supabase edge: environment variables that never reached production, or row-level security left open on a table that holds real customer data.
Bolt
Bolt ships fast and leaves the build config behind. The deploy fails on a missing package, a Node version, or an API key that only ever existed in the preview.
Replit
Replit apps run fine in the workspace and 500 on a real domain: ports, file paths and secrets that were never wired up for the deployed process.
Cursor
Cursor edits confidently across files it has not read. Two features end up disagreeing about the same state, and the bug moves every time you fix it.
v0
v0 gives you the interface, not the wiring. Forms post to nothing, server actions are still stubs, and auth is a component rather than a session.
Windsurf
Windsurf refactors reach further than intended. Imports, types and routes drift apart until the build stops on something unrelated to what you changed.
Base44
Base44 apps hit their ceiling at data and roles: the model that fit the demo cannot carry a second kind of user without redoing what sits underneath it.
Claude Code
Claude Code writes real code, which means real dependencies, migrations and tests. When it breaks, it breaks somewhere prompting cannot reach.

What it usually turns out to be

It works locally, then 500s once deployed
Nearly always an environment variable, a build step or a file path that only exists on your machine. The code is usually fine.
The AI keeps fixing the same bug
Each pass patches the symptom because the cause sits a layer down, in the data model or in how state is shared. Prompting harder does not reach it.
Forms submit but nothing arrives
The browser gets a success back while the server quietly fails. Without error handling and logs nobody finds out until a customer complains.
Logins drop or leak between users
Session and auth code copied from an example built for a different rendering model. It looks right in testing and breaks under real traffic.

And what nobody notices until later

Security is the part an AI builder is quietest about. None of these stop the app working, which is exactly why they ship.

The database is open to anyone with the URL
Supabase and Firebase hand the browser a key on purpose — the row policies are what actually guard the data. Generated projects routinely ship with those policies off, which turns a public key into a key to everything.
Secrets that shipped to the browser
A service key pasted into a component, or one prefixed NEXT_PUBLIC_ so the build would stop complaining. It is in the page source, readable in devtools, and the bill for it is yours.
Any logged-in user can read every other user's data
The endpoint takes an id and returns that record without ever asking whose it is. Nothing looks wrong while you are the only account; change the number in the URL and you are in someone else's.
Nothing stops the same request a thousand times over
No rate limit and no real validation on the public routes, so login, password reset and checkout can each be hammered until something gives. Generated code almost never adds this on its own.

If you recognised your own problem somewhere above, that is the point. The audit is where you find out which one it actually is.

Book my audit

$199$349promo

Send it over. We'll tell you what's wrong.

One fixed-price audit at $199 instead of $349. A video walkthrough, written findings and a firm quote on what it takes to fix.

Book my audit

Book my audit

$199. Fixed price, agreed up front.

Ask a question first

No payment and no obligation, just an answer.