ContactBook a call

Security

Is my Bolt.new app secure? The checks to run

How to check a Bolt.new app before launch: row-level security on Supabase or Bolt Database, keys in the bundle, Netlify secrets and the Security page.

Cover for “Is my Bolt.new app secure? The checks to run”, with the line: The database is reachable from the browser, so the rules on each table decide who sees what.
The database is reachable from the browser, so the rules on each table decide who sees what. Image: SBD.

A Bolt.new app is as secure as the rules on its database and the place its keys live. Most Bolt apps talk to Supabase or Bolt Database straight from the browser, so anyone who opens the page can send queries with the same key the app uses. That is a normal design, and it is safe when every table has row-level security switched on with policies that limit each user to their own rows. The other common gap is a third-party API key placed in front-end code, which ends up in the JavaScript that Netlify or any other host serves to every visitor. You can check both yourself in under an hour.

This post is for founders who built an app in Bolt.new, often deployed to Netlify, and want to know whether it is safe to put real users on it. It covers how the data is exposed, what Bolt’s own Security page checks, the checks to run by hand, and when to bring in help.

The short answer

Open the Security page in Bolt's database settings and fix everything marked Error. Then, in a private browser window, try to read each table with the public key from your page source. You should get nothing back for tables that hold private data. Finally, search your built files for any key that starts with sk_, re_ or similar. If one is there, move the call to a server function and rotate the key.

How a Bolt app exposes data

Bolt generates a front end, usually React with Vite, and connects it to a database. On current projects that is Bolt Database, and older projects or ones you connected yourself use a Supabase project. Bolt’s documentation says its database Security tab runs the same checks as the Security Advisor in Supabase, so the model underneath is the same.

The browser holds a public key and sends requests directly to the database API. What stops a stranger reading every row is row-level security (RLS): a rule on each table that says which rows a request may see or change. Supabase’s documentation explains that once RLS is enabled, nothing is readable through the API with the public key until you write a policy that allows it. With RLS off, the opposite holds, and the public key can read and write the whole table.

Bolt’s own help page says it enables RLS on tables it creates. It also says two things worth reading twice. Tables you add yourself need RLS turned on as well, and if your app has no sign-in, Bolt may write policies that let any visitor view, add, change or delete data. Those show up as an “RLS Policy Always True” warning. That is fine for a public guestbook and a problem for anything with customer details in it.

We wrote about the same failure in Lovable apps in Your Lovable app is probably public, including the CVE where over 170 apps had open databases. The mechanism is identical in Bolt because the database is the same kind.

The second leak: keys in the bundle

When you ask Bolt to add payments, email or an AI feature, it has to put an API key somewhere. If that key lands in a variable whose name starts with VITE_, Vite copies it into the JavaScript that ships to the browser. Vite’s documentation says this plainly: VITE_ variables are exposed in client-side code and should not hold anything sensitive.

So a Stripe secret key, a Resend key or an OpenAI key in a VITE_ variable is readable by anyone who opens developer tools. Someone who finds an AI key can run up your bill, and a payment or email key can do worse.

Netlify helps here. Its secret scanning checks your repository and build output for the values of environment variables you have marked as secret, and fails the deploy if it finds one, with the file location in the deploy log. It also has smart detection for values that look like keys. The fix Netlify points to is to keep the key on the server, for example in a Netlify Function, rather than switching the scan off. If your build has been failing on secret scanning and someone set SECRETS_SCAN_ENABLED to false to make it pass, treat that as a finding.

The checks to run yourself

Set aside an hour. You need access to the Bolt project, the database dashboard and the Netlify site.

  1. Run Bolt’s Security page. Click the database icon at the top of the project, then Security. Issues are sorted by severity. Fix every Error, read every Warning, and run it again after each database change. The “Ask Bolt to fix” button is useful, but read the policy it writes before you accept it.
  2. List every table. Include the ones you did not ask for: profiles, logs, uploads, tokens. Check RLS is on for each.
  3. Read each policy. For private data, a select policy should compare the row’s user id with the signed-in user’s id. A policy whose condition is true lets everyone in. Insert and update need their own policies, and most apps need no delete policy at all.
  4. Test logged out. Open the live app in a private window. Copy the database URL and public key from the page source or network tab, and query a private table from the console. You should get an empty list. Then sign in as a test user and confirm you can see only that user’s rows.
  5. Search the build for keys. Run npm run build and search the dist folder for sk_, sk-, re_, secret and the first few characters of each key you use. Anything you find is public. Move the call into a Netlify Function or a Supabase Edge Function and rotate the key with the provider.
  6. Check Netlify environment variables. In site settings, mark real secrets as secret so the scanner watches for them, and make sure no secret has a VITE_ name.
  7. Check storage buckets. If users upload files, open the storage settings and confirm private buckets are private and have policies of their own.
  8. Turn on leaked password protection. Bolt Database has it on by default. On a free Supabase plan the setting may not be available, which is why the Security page can show it as a warning.

What the checks do not cover

These steps catch the two problems that expose the most data with the least effort. They do not tell you whether your sign-up flow can be abused, whether an admin page checks the user’s role on the server, whether there are rate limits on forms and AI calls, or whether you have backups you have tried restoring. Bolt’s documentation is also clear that the database Security page checks the database only, and it points to a separate project security check for code.

When to get a second pair of eyes

If the app holds customer data, takes payments, or you are about to show it to investors or a first large customer, an outside review is worth more than another feature. Our vibe-coded app audit starts at $500 and you get a written report within a week, ranked by risk, covering the database rules, keys, auth, storage, rate limits and backups. If the fixes are more than you want to take on, Harden starts at $1,000 and we make the changes, and Rebuild starts at $8,000 for apps that need a proper server layer.

The same review applies to apps built in other tools. If part of your app came from Replit or was finished in Cursor, see Replit app to production and Cursor app security review. For how we use Supabase on client builds, see the Supabase integration page.

Questions we get asked

Bolt says it enables RLS on tables it creates. Is that enough?

It covers the tables Bolt made, and the policies may still be wide open if the app has no sign-in. Tables added through SQL or the dashboard need RLS switched on by you. The logged-out test in a private window tells you what is true today.

Is the public key in my page source a leak?

No. It is designed to be public, and Supabase and Bolt expect it in the browser. It becomes a problem only when RLS is off or a policy allows everyone. The service role key is different and must never reach the browser.

My Netlify deploy fails with a secrets scanning error. Should I turn scanning off?

Read the deploy log first, because it names the file where the value was found. If a real secret is in your front-end bundle, move it to a function and rotate it. Use the omit settings only for values you have confirmed are meant to be public.

Do I need to move off Bolt?

Usually not. Many Bolt apps are fine once the database rules are right and secret keys sit behind a server function. A rebuild makes sense when the app needs business logic the browser should not be trusted with, such as pricing, permissions or payouts.

Sources and further reading

  • Bolt
  • Supabase
  • Vibe coding
  • Security
  • MVP audit

Keep reading

Cover for “Supabase row-level security for AI-built apps”, with the line: The public key reaches every table, so each table needs a rule that says whose rows are whose.

Security

Supabase row-level security for AI-built apps

How row-level security protects a Lovable, Bolt or v0 app on Supabase, the policy mistakes AI builders make, and the checks to run in under an hour.

Cover for “Taking a v0 app to production: security checks”, with the line: Every server action is a public endpoint, so each one has to check who is asking.

Security

Taking a v0 app to production: security checks

Before a v0 app gets real users: auth inside every server action, NEXT_PUBLIC_ variables, Supabase rules, preview deployments and GitHub branch checks.

Cover for “Your Lovable app is probably public”, with the line: The anon key is in the browser. Without row-level security it is a master key.

Security

Your Lovable app is probably public

Over 170 Lovable-built apps had open databases in one disclosure. How the leak works, the three named breaches of 2026, and the twenty-minute check to run.

Find out what is worth automating

About 95% of AI pilots never reach the profit line. We start with the work your team still does by hand and measure each build by the hours it saves.

See how we work

Cookie preferences

Choose what this site may use on your device. You can change this at any time from “Cookie settings” in the footer.

Strictly necessary

Keep the site working and remember the choices you make here. These cannot be switched off, and none of them track you.

Always on
What this includes (4)
NameProvider PurposeDuration
sbd-consentThis site Remembers your cookie choices12 months
Vercel Web AnalyticsVercel Inc. Counts page views in aggregate. Sets no cookie and stores nothing on your deviceNone
ticker-dismissed, sbd-note-offThis site Remembers that you closed a notice or language tipUntil the tab closes
sbd-voice-resume, sbd-voice-prefillThis site Carries a voice conversation across pages, only if you start oneUntil the tab closes

Analytics

Tell us which pages are read and where visitors leave, so we can improve them. IP addresses are anonymised and nothing is used for advertising.

What this includes (2)
NameProvider PurposeDuration
_gaGoogle Analytics (Google LLC) Distinguishes visitors with a random ID13 months
_ga_FPXDMQPRV1Google Analytics (Google LLC) Keeps the session state for this site13 months

Functional

Embedded services that set their own cookies. Without them the site still works; you get a link to open the service instead.

What this includes (1)
NameProvider PurposeDuration
Booking calendarCal.com Inc. Shows live availability and books the call on the booking pageSet by Cal.com

Advertising

Not used. This site has no advertising, retargeting or social media tracking, and we never sell data.

Not used

Questions about your data: hello@smallbaydigital.com