Built with Bolt

Bolt built you a working app that it cannot ship.

Bolt writes the app quickly and treats the build as an afterthought, so the code you have is usually fine and the instructions for turning it into a running site are not. Four faults cover almost everything we are sent.

Book my audit

What usually breaks in Bolt

The deploy fails on a package that was never installed

Something in the generated code imports a library that is not in the manifest, because it was assumed rather than added. In the sandbox it resolved anyway; on a clean install there is nothing to resolve. The log names the module on the line it gave up, which is the one piece of good news here.

A Node version the build does not have

Generated code reaches for syntax and APIs from a recent runtime, and the host defaults to whatever it defaults to. You get a parse error or a missing global in the build step rather than in the app, so it reads like corruption rather than a version mismatch. Pinning the runtime fixes it and nothing else has to change.

API keys that only ever existed in the preview

The values were typed in once where the app was running and never recorded anywhere the deploy can read. The build succeeds because nothing checks them, and the first request that needs one comes back with an authentication error from a service you have paid for. Every key has to be re-entered on the host, by name.

The build output is not where the host looks for it

The framework writes finished files to one directory and the host is serving a different one, so you get a directory listing, a 404 on every route, or an index page with nothing behind it. It is two settings that have to agree, and neither of them is in your code.

Symptoms we see most in Bolt projects

Is my code broken, or is it only the deploy?

Usually the deploy alone, and that is the first thing the audit separates. We run your project from a clean checkout: if it builds there, the fault is in the host's configuration and the repair is short. If it does not, you get the actual error and what it will take, before you decide anything.

Do you need my hosting account?

We need to see the build log and the environment settings, which most hosts let you share without handing over the account. Where a value genuinely has to be set for you, add us to the project and remove us afterwards.

Can you move it to a host that suits it better?

We can, but a failed deploy is not on its own a reason to. A fresh host makes the same four mistakes if the configuration goes with it. If moving is genuinely the cheaper answer for your project, the audit says so with a price attached.

How fast is this, realistically?

Deploy faults are the quickest thing we do, because the build log is evidence rather than guesswork. Most are diagnosed the same day and fixed inside a couple of hours once you approve the price.

How it works

Audit

$199~~$349~~promo

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~~$349~~promo

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~~$349~~promo

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