Common ways live Bolt apps break
From Bolt's and Netlify's docs, and failures we've written guides for. Under each one, “Heedza sees this” means the problem stops a page from opening or removes its form, so you get an alert. Heedza only sees what a visitor sees before logging in, so it can’t see problems that happen after a form is sent.
- A prompt drops part of the app. Bolt's docs: "If Bolt only built part of what you asked for, dropped a feature, or seemed to lose track partway through, the most common cause is a single large, multi-part prompt" (Bolt: issues). See also Bolt app lost its sign-up page after a prompt? Get it back. Heedza sees this.
- The project is too big to publish. "Bolt projects must be under 100MB." Above that, publishing fails with Project is too large to deploy (Bolt: Publishing issues). Heedza can’t see the cause. You only notice that your change isn’t on the live site.
- The Netlify connection is lost. If you fork or duplicate a project, you need to reconnect to Netlify, which creates a new Netlify site, so custom domains must be pointed at it (Bolt: Publishing issues). Heedza can’t see the cause. You only notice that your change isn’t on the live site.
- Bolt hosting vs Netlify is a one-way choice per project. Netlify's guide notes that once you publish a project to Bolt hosting, you can't move that same project to Netlify (Netlify: Deploy your Bolt app). Heedza can’t see the cause. You only notice that your change isn’t on the live site.
- The Netlify build fails. See Netlify "Build script returned non-zero exit code: 2". Heedza sees this.
- The build succeeds but the page is blank. See Bolt.new app blank white page on Netlify? Heedza sees this.
- Some visitors can't open .bolt.host at all. Bolt says some networks block uncommon domains like
.bolt.host(Bolt: Publishing issues). A custom domain avoids that. Heedza can’t see this: its own network doesn’t block .bolt.host.
What Heedza checks
Heedza works from the outside, on your public web address. There's nothing to install.
- Your key pages. We open your home page the way a visitor does, follow its links to your sign-up, log-in and payment pages, and check on a schedule that each one opens and shows its form or Pay button.
- Security checks. The free scan looks for secret keys in your page code and
.envor.gitfiles anyone can open. - Alerts. When a check fails, you get an alert (by email, or on paid plans also Slack, Telegram or a webhook (we send the alert to a web address you choose; for developers)) with a picture of the page and a fix written for Bolt, ready to paste into the Bolt chat.
It never fills in forms, never logs in, never types a card number and never clicks Pay. So it can't tell you whether a log-in, email or payment works after the button is pressed.
It works the same for any vibe-coded app, whichever AI tool made it. Build Bolt apps for clients? See Heedza for agencies: up to 30 client sites, with white label client reports and status pages on Business.
Fix it for me (Pro and Business)
Some alerts have a Fix it for me button. Nothing starts until you press it. Heedza then writes the fix and suggests it on GitHub (a pull request). Nothing changes in your app until you approve it, and you can undo it.
It works for a page Heedza checks that stopped working (such as sign-up, log-in or payment), a file that should not be public, and a security setting your site stopped sending. It needs your app’s code in a GitHub project (repository), with the Heedza GitHub app added to it. Other alerts come with a fix to paste into your AI tool. How Fix it for me works