How to take a Bolt app to production
Built your app on Bolt? What usually needs fixing before real users and payments, how long it takes and what it costs.
By the v1build engineering team · Published · 5 min read
Bolt generates full-stack web apps from a prompt and lets you edit and run them in the browser. It is excellent for getting a working version fast. Moving that version to production means taking the code into your own repository and hosting, then fixing what a prototype doesn’t need but customers do.
What usually needs work
| Area | Typical issue | The fix |
|---|---|---|
| Code ownership | Project lives only in the builder | Export to your GitHub; set up environments |
| Hosting | Preview deploys used as production | Proper hosting with staging and production |
| Secrets | Keys in front-end code or committed to the repo | Move to server-side environment variables and rotate them |
| Authorisation | Checks only in the interface | Server-side permission checks on every request |
| Data | Demo schema, no migrations | A versioned data model with migrations and backups |
| Payments | Checkout without verified webhooks | Webhook verification and reconciliation |
| Quality | Inconsistent generated code, no tests | Refactor hot spots; tests on core flows |
| Monitoring | None | Error tracking and uptime alerts |
Harden or rebuild?
Generated code quality varies with how precisely it was prompted. If the core flows are clean, we harden. If the same logic is duplicated across many files, a partial rebuild of the backend is often faster. We decide that in the review, not before.
Time and cost
| Starting point | Typical time | Typical cost |
|---|---|---|
| Simple app, no payments | 1 – 2 weeks | $3,000 – $6,000 |
| Payments, roles, integrations | 2 – 3 weeks | $6,000 – $12,000 |
| Significant backend rework | 3+ weeks | $12,000 – $25,000 |