Bolt.new app review
Bolt.new app audit: is your app safe to launch?
Bolt.new checks and fixes its own code when you publish. The useful question is what is left after it has.
You built your app with Bolt.new, ran its security audit, and it says everything is up to date. Before you take payments or let real customers in, you want to know what that audit can vouch for and what it cannot. That is the question our vibe coded app audit answers, and this page covers how it applies to apps built with Bolt.new.
4 findings, a fix for each
Ranked by what an attacker could do with them
- CriticalRow-level security is off on 3 tablesDatabase: orders, invoices, profilesFix included
- HighService key shipped to the browserFrontend bundle: supabase.tsFix included
- HighAdmin role checked in the client onlyRoute: /admin/usersFix included
- MediumNo rate limit on sign-inAuth: password sign-inFix included
Launching a Bolt.new app that takes payments or personal data?
We review what Bolt's audit cannot: your rules, your connected services and the fixes it made. You get a ranked list of what to do first.
What Bolt.new already does for you
Credit where it is due: Bolt.new does a good deal of security work by default. Apps on Bolt Cloud keep their data in Supabase; Supabase says every Bolt Cloud project that needs a backend runs on it. According to Bolt's database security documentation, Bolt switches on row-level security for the tables it creates, turns on leaked-password protection, and checks your database against the same rules as Supabase's Security Advisor, on every plan.
On paid plans, Bolt's project security audit goes further. From the Publish menu it reviews the whole project: who can see and change data, what the app exposes publicly, sign-in and sessions, misuse such as changing prices or skipping steps, visitor input, and exposed keys. It then fixes most of what it finds by itself, and you can run it up to 30 times a day. Use it before every publish.
Where Bolt.new apps still go wrong
- 1
Apps without sign-in that let every visitor change the data
Bolt's own database documentation warns that on a site with no sign-in it might write policies that let any visitor view, add, change and delete the data. The database check flags these as "RLS Policy Always True". That is fine for a public guestbook and a serious problem for anything else: visitors should usually be able to read or submit, not edit or delete.
- 2
Tables Bolt did not create
Bolt switches on row-level security for the tables it creates. Tables you add yourself, with SQL or in a Supabase project you connected, need it switched on by hand. If one was missed, it is open to anyone with your public key; here is what Supabase's "RLS Disabled in Public" warning means.
- 3
Fixes nobody has read
Bolt's audit fixes most of what it finds on its own, changing your code and database as it goes. That is quick, but it means changes to your access rules that nobody on your side has reviewed, and restoring an earlier version from history also removes the security fixes made after it. A later prompt about something else can loosen a rule again.
- 4
Settings in the services you connected
Bolt says some issues need your action in a connected service, such as your email or payment provider, and lists them in the chat. They are easy to put off. Typical examples: Stripe still in test mode or with webhook signing missing, live keys in the wrong place, or an email domain without the records that keep your messages out of spam.
- 5
Rules only you know
Bolt's audit looks for one user reaching another's data and for misuse such as changing prices or skipping steps, which is genuinely useful. It cannot know your intended rules: that a team member may see their own company's records but not another's, or that a refund should end access. Gaps there look like correct code. We cover the common patterns in broken authentication in AI-generated code.
Is Bolt.new production ready?
Bolt.new can build apps that run in production, and Bolt Cloud gives you hosting, databases and domains. Whether your app is ready is a different question, and security is only half of it. The other half is the part no builder decides for you: error monitoring, backups you have restored, separate test and live data, and a payment flow that holds up when cards fail and webhooks arrive twice. Our production-readiness review covers that half, with the full checklist.
Check your own Bolt.new app
- 1Before every publish, run the project security audit (Publish, then Run security audit) and read the summary of what it changed. On a free plan, use the database security check on the Security tab of your database settings.
- 2Look for any "RLS Policy Always True" warning and decide, table by table, whether every visitor really should be able to change that data.
- 3Open the published app in a private window, signed out, and try the pages that should need an account.
- 4Sign up as a second test user and try to open the first user's records by changing IDs in the address bar or in the requests the app sends.
- 5Search the built JavaScript in your browser's developer tools for sk_live, sk- and sb_secret. Any hit is a key to rotate.
- 6If you take payments, run a test purchase, refund and cancellation in Stripe's test mode and check the account ends up in the right state each time.
If a policy looks right and still misbehaves, the usual causes are in why Supabase RLS is not working.
How we review a Bolt.new app, and what it costs
- Audit, $149, back in 48 hours. A senior engineer reads the policies, functions, keys and the changes Bolt's own audit made, checks them against what the app is meant to allow, and tests access as a stranger and as a second user. You get a severity-ranked report in plain English with a fix for every finding.
- Fix Sprint, typically $600 to $1,500, one to two weeks. We fix the critical and important findings, test them again and issue an updated report showing each one closed.
- Production hardening, from $2,500, scoped per project. Prototype to production: authentication, keeping customers' data apart, payments, monitoring, backups, and anything that genuinely needs rebuilding.
The $149 audit fee comes off the price of whatever you do next, and we sign an NDA on request. The full audit, including what it does not cover, is on the vibe coded app audit page.
We build on the same backend
Bolt Cloud apps run on Supabase, and so do two of our own production systems:
- Run Courier: web, iOS and Android apps on one Supabase backend with row-level security, twelve Edge Functions, Stripe payments and six role-based dashboards where each role sees only its own data.
- Talent Acquisition platform: a React and Supabase hiring system with row-level security across seven user roles.
Find out what Bolt's audit cannot tell you, before your customers do.
$149, 48 hours, and the fee comes off any fix work you choose afterwards.