App builders
Bolt.new consultant: getting a Bolt app ready for real users
Bolt.new, built by StackBlitz, gets a full-stack app running in the browser from a prompt, with a database and hosting attached. SBD works with teams whose Bolt app now holds customer data or takes payments, and reviews and fixes its database rules, keys and failure handling. The review is $500 with a written report within a week.
Already built something on Bolt and real users are arriving? Get a vibe-coded app audit, from $500, with a written report on what to fix before launch.
- Tool
- bolt.new
- Usually paired with
- Supabase, GitHub, Stripe, Resend
- Timeline
- Most builds live in 2 to 8 weeks
- Owned by
- You, with accounts, credentials and code in your name.
What we build on Bolt
- Review database rules, secrets and sign-in before launch
- Move API keys out of browser code into server functions
- Set up GitHub sync so fixes have a history
- Add error handling, logs and alerts
What we sync
Workflows we are asked for
- Bolt security review before launch
- Bolt app with row-level security per user
- Bolt app connected to Stripe and Resend through server functions
- Bolt app synced to your own GitHub repository
Tools Bolt usually needs to talk to
-

Bolt and Supabase
Postgres with auth, storage and APIs, and the database under most apps we build or rescue.
-
Bolt and GitHub
A code hosting platform with reviews and automation, used to keep client code and workflow exports in one owned, versioned place.
-

Bolt and Stripe
Payments, invoicing and subscriptions for software and services businesses.
-

Bolt and Resend
Transactional email for developers, with clean deliverability tooling.
What SBD does with a Bolt app
Most Bolt apps send queries from the browser straight to the database, so the rules on each table decide who can read what.
We test the app logged out and as each kind of user, read the policies and server functions, look for keys that reached the browser bundle, and write down each finding with a price for the fix.
SBD has no published case study on Bolt. js and Supabase with roles enforced on the server. It is not a Bolt project, so read it as the standard we would hold your app to.
- Row-level security on every table, with policies that match who should see each row.
- Secret keys moved into server functions and rotated if they were ever exposed.
- Sign-in, password reset and email settings checked end to end.
- Error handling and alerts so a failed payment or email reaches a named person.
- A keep-or-rebuild recommendation when the generated code will not carry the next stage.
What Bolt checks for you, and what it leaves to you
Bolt's help centre, read in November 2026, describes two checks
A database security check on every plan flags settings such as a table anyone can read, and it runs the same checks as Supabase's Security Advisor. A project security audit on paid plans also reviews code, sign-in, input handling and keys, and Bolt fixes what it can. The same pages say some issues need manual changes in connected email or payment services.
Bolt also says it switches on row-level security for tables it creates, and that tables you add need it switched on by you
If the app has no sign-in, Bolt may write policies that let any visitor read or change data. We cover the checks a founder can run in Is my Bolt.new app secure?, and our vibe-coded app audit goes further.
Where Bolt keeps keys, and where they leak
- 01
Bolt's documentation separates secrets from environment variables.
Secrets sit in the database settings and are available only to server functions that run on Bolt's servers. Environment variables live in the project's .env file and can be read by browser code, so Bolt says they should not hold anything sensitive.
- 02
The leak we see most is a payment, email or AI key placed in an environment variable because that was the quickest way to make a feature work.
Anyone who opens developer tools can read it. The fix is to call that service from a server function and rotate the key.
Moving the code out of Bolt
Bolt's GitHub integration syncs both ways
Bolt commits each change to the repository and pulls in commits made outside Bolt, and branches created in Bolt also appear in GitHub. Bolt cannot merge branches, so merges happen through pull requests in GitHub. We set the repository up at the start of a hardening job so every fix has a history.
Bolt can publish to its own hosting or to Netlify
On the free plan, Bolt hosting is capped at 10 GB of bandwidth a month and the site goes offline for the rest of the month if it passes the limit, so check the plan before launch.
When Bolt is the right choice, and when it is not
Bolt suits a new product or tool where the screens are still changing and a developer may take the code later.
A prototype with no real data does not need our review, and we will say so.
Plan a different route in these cases:
- Staff need to change screens themselves without prompts or code. Softr is usually easier for them.
- The tool sits on databases and APIs your engineers already run. Retool fits that better.
- Pricing, permissions or payouts are decided in browser code. That logic has to move to a server, and sometimes a rebuild is cheaper.
How a Bolt engagement with SBD works
Start with the vibe-coded app audit at $500, with a written report within a week that lists each fix with a fixed price.
Harden starts at $1,000 and takes about two weeks, and Rebuild starts at $8,000.
Read next
Sources
- Bolt Help Center, Database security (Security page, RLS on Bolt-created tables, "RLS Policy Always True"), checked 21 November 2026
- Bolt Help Center, Check your project's security (project audit, plans, manual action items), checked 21 November 2026
- Bolt Help Center, Secrets (server functions only, .env readable by browser code), checked 21 November 2026
- Bolt Help Center, GitHub integration (two-way sync, branches, merging in GitHub), checked 21 November 2026
- Bolt Help Center, Billing (plans, free hosting limits), checked 21 November 2026
Standards on every build
Validation, retries, reconciliation, audit logs and alerts come as standard, with credentials and accounts in your name. Read the integration standards
What people ask about Bolt
Is Bolt's security audit enough?
It is a good first pass and you should run it. Bolt's help pages say some issues need manual changes in connected services, and the audit cannot know which data in your app is meant to be private. Someone still has to read the rules against how the business works.
Can we take the code away from Bolt?
Yes. Bolt syncs both ways with a GitHub repository, so developers can work on the code outside Bolt and merge through pull requests.
Start with the one Bolt workflow your team still runs by hand
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call












