We UC
Back to blog
·6 min read·We UC Team

I built my app with Bolt or Replit and real customers use it. How do I make it safe for production?

Six things to put right once real customers use an app built in Bolt or Replit: separate live data, backups you have restored, secrets, payments, monitoring and a way back.

I built my app with Bolt or Replit and real customers use it. How do I make it safe for production?

An app is safe for production when live customer data is kept apart from the data you test with, you can restore a backup, your keys and passwords are out of the code, payments are confirmed by the server, someone is told when it fails, and you can go back to the last version that worked. Bolt and Replit get an app running and published; these six jobs are what comes after, and most of them can be checked by a non-engineer asking for a screenshot or a dated note.

What changes when real customers start using the app?

The cost of a mistake changes. While you were building, a broken screen cost you an afternoon. Once customers and their payments are in it, a wrong database change can lose records you can't recreate, and a bug is live for everyone until it is fixed. Nothing about the tool you used makes that your fault. It is the point where the app needs the habits that a team running live software has, and you can ask for them one at a time.

Is my test data separate from my customers' data?

It should be, and you can check in a few minutes. Replit's documentation on development and production says a published app uses a production database while the editor keeps using a development one, and that its Agent "is not able to modify the production database". It also says publishing applies the structure changes made in development but doesn't copy domains, functions, procedures, triggers or grants, and that you should only copy development data across if it is safe to use in your live app.

Ask whoever built the app: "Which database does the published version use, and is it a different one from the one we build in?" If the answer is that they are the same, every experiment is happening on live customer records.

Have we ever restored a backup?

A backup you have never restored is a hope and not a backup. On Supabase, which Bolt can use for its database, daily backups are automatic for Pro, Team and Enterprise projects, kept for 7, 14 and 30 days respectively. The same page says backups don't include files stored through Supabase's Storage API, and for free-tier projects it recommends exporting your data regularly and keeping copies off-site.

Bolt's own Supabase help page adds a point that surprises people: restoring an earlier version of your Bolt project leaves the Supabase data as it is. Version history rolls back the code and not the customers' records, so the two need separate plans. It also warns that connecting a different Supabase database replaces the connection and may cause data loss.

The thing to ask for is a dated note saying a backup was restored to a separate copy and the records looked right.

Where are the passwords and API keys?

They should sit in the host's secret settings, not in the code and not in anything a visitor's browser downloads. Keys pasted into a chat or a screenshot while debugging should be replaced with new ones, which takes minutes for most services. Our piece on whether a vibe-coded app is secure goes through secrets, access rules and payment checks in more detail.

Are payments confirmed by the server?

Your server needs to check that every payment message really comes from the payment provider before it marks an order as paid. If you take card payments, also check that the live keys are the ones in use and the test keys are not, and that a failed payment doesn't leave the customer with access. Our article on auditing AI-written code before taking payments covers what a developer should look at.

Who finds out when it breaks?

Someone should be told within minutes, and today it is probably a customer emailing you. The minimum is an error log that is kept and an alert that reaches a named person when the app returns errors or goes down. Without it you learn about problems from the people they hurt.

Can we go back to the last version that worked?

Only if the code lives somewhere other than the tool. Keep the code in a repository you own, such as GitHub, with the live version tagged, so a bad release can be reversed without guessing. Ask who has access to that repository and to the hosting account, and make sure at least two people do, one of them you. Our piece on what to do if the developer has left covers the ownership side.

How much of this can we do ourselves?

The questions, yes. The checking usually needs someone to read the code and the hosting settings. The We UC Rescue audit is a fixed £2,500 + VAT, deducted from the first phase if you go ahead with us on the fix. It covers security, data, hosting, code, payments and integrations, and running costs, and you get a written report, a priced plan and a walkthrough call. Nothing is changed during the audit, so we need read access to your code and hosting, and the report is yours either way.

We UC is a UK software company. The team doing the review also runs Olatti, a UK business phone network, and Quenta, an app that posts receipts into Xero, in production. Two QA engineers test our work, and an engineer reviews every change before it ships.

Common questions

Is a Bolt or Replit app ready for customers as it is?

Some are, and the quickest way to find out is the six checks above. If you can't answer two or more of them, treat those as unknown and not as fine.

Do I need to rebuild it to make it safe?

Usually not. Most of these jobs are changes around the app: separate data, backups, secrets, monitoring. Our piece on fixing or rebuilding a vibe-coded app explains how to decide.

Will you look down on how it was built?

No. You got a working product in front of real customers, which is further than most ideas get.

If customers are already paying and you can't answer most of the six questions, you can book a Rescue audit, or tell us what you've built and we'll say whether an audit is the right first step.