No. There is no calendar link anywhere on the site. Scoping, quoting and progress all happen in writing, plus a recorded walkthrough before any code is written. Everything therefore lands on a permanent record you can search later.

What does the $99 audit include?

A written audit delivered within 48 hours: severity-ranked security and production-readiness findings with file and line references, a fixed-price quote to fix them, and a private URL. The $99 credits in full into any fix engagement.

Dinajpur, Bangladesh, at UTC+6. Two people, nobody subcontracted. For a studio that works in writing the offset is an advantage: a brief sent at the end of a US or European working day is answered before the next one begins.

You do, in full, assigned on final payment. No lock-in and no hosting hostage.

Budgets under $1,000, hourly billing, unlimited-revision brochure sites, enterprise procurement and vendor onboarding portals, and anyone who needs a call before they can buy.

rescue · bolt

What breaks in Bolt apps.

Bolt builds and runs the whole app inside the browser, which is what makes it fast to try and awkward to ship. The code assumes an environment that only exists while the tab is open.

The four we find most often.

Secrets that were never server-only
Anything the sandbox needed at runtime tends to end up readable by the client. An API key that worked in the preview is a key that shipped to every visitor.
No build that runs anywhere else
Apps that only ever ran in the sandbox often have no working production build: missing scripts, unpinned versions, and imports that resolved only in the browser runtime.
Auth that checks in the wrong place
Route guards written in components hide the page without protecting the data. The request underneath still returns the rows.
A database with no migration history
Schema changed by hand in a preview leaves nothing to replay. The first time you need a second environment, there is no way to recreate the first.

How the work runs.

The $99 audit comes first. You get a written list of what is wrong, each finding naming a file and a line, plus a fixed quote to fix it. If you take the fix, the $99 comes off the price. If you do not, the list is yours and any developer can act on it.

Audit: $99, back within 48 hours. Credits into the fix.
Rescue: $2,500–$5,000, two to three weeks, 30-day fix warranty.
How we work: Written and asynchronous. A recorded walkthrough before any code. No calls.
The code: Yours in full on final payment. No lock-in.

Questions.

My Bolt app works in the preview but fails when deployed. Why?: The preview runs a browser-hosted environment with different module resolution, different environment variables and no real server. Code that depended on any of those three stops working the moment it leaves. Rebuilding the build and the server boundary is usually most of the job.
Do I have to move off Bolt?: To run in production, yes — you need a real repository and a real deploy. You keep the code and can go on prototyping in Bolt separately.
How long does it take?: Two to three weeks for a rescue, quoted at a fixed price after the $99 audit. The audit comes back within 48 hours.

Other builders: Lovable, v0, Cursor.

Send us the Bolt project.

The audit names what will break before you commit to anything. Repository link and a sentence about what is going wrong is enough to start.

Start a build →Or buy the $99 audit →

Written and asynchronous. Nobody here will ask you to book a call.

What breaks in Bolt apps.

Bolt builds and runs the whole app inside the browser, which is what makes it fast to try and awkward to ship. The code assumes an environment that only exists while the tab is open.

The four we find most often.

Secrets that were never server-only

Anything the sandbox needed at runtime tends to end up readable by the client. An API key that worked in the preview is a key that shipped to every visitor.

No build that runs anywhere else

Apps that only ever ran in the sandbox often have no working production build: missing scripts, unpinned versions, and imports that resolved only in the browser runtime.

Auth that checks in the wrong place

Route guards written in components hide the page without protecting the data. The request underneath still returns the rows.

A database with no migration history

Schema changed by hand in a preview leaves nothing to replay. The first time you need a second environment, there is no way to recreate the first.

How the work runs.

Audit

$99, back within 48 hours. Credits into the fix.

Rescue

$2,500–$5,000, two to three weeks, 30-day fix warranty.

How we work

Written and asynchronous. A recorded walkthrough before any code. No calls.

The code

Yours in full on final payment. No lock-in.

Questions.

My Bolt app works in the preview but fails when deployed. Why?

The preview runs a browser-hosted environment with different module resolution, different environment variables and no real server. Code that depended on any of those three stops working the moment it leaves. Rebuilding the build and the server boundary is usually most of the job.

Do I have to move off Bolt?

To run in production, yes — you need a real repository and a real deploy. You keep the code and can go on prototyping in Bolt separately.

How long does it take?

Two to three weeks for a rescue, quoted at a fixed price after the $99 audit. The audit comes back within 48 hours.