⚡
Integration
DeployDoc for Bolt
Catch the deploy failures that hit when a Bolt project moves from the in-browser editor to a real host.
Educational recipeEducational recipe — paste your build log or project zip.
What commonly breaks on Bolt
- VITE_ env vars set in Bolt's UI but missing on the deploy target.
- Supabase keys configured for the Bolt sandbox project, not your own.
- API keys hard-coded during prototyping then accidentally shipped.
- Generated server code mixing client and server runtimes.
What DeployDoc checks
- VITE_ env vars referenced in code vs defined on the host.
- Hard-coded provider keys in shipped bundles.
- Client/server runtime mismatches in generated handlers.
- Supabase URL pointing to a Bolt-sandbox project ref.
Can automate
- • Static env-var diff.
- • Secret-prefix scanning of compiled output.
- • Build-log triage.
Cannot automate
- • Editing your Bolt project from outside Bolt.
- • Pushing fixes back to a StackBlitz container.
- • Provisioning new Supabase projects.
Get started with Bolt
Run a diagnosis on a recent failed build, or connect Bolt for one-click fixes where supported.