For StackBlitz's Bolt
Stuck in Bolt? Press the dot.
Bolt is one of the fastest prompt-to-prototype paths. Relay turns the prototype into a thing you can ship.
When Bolt needs a person.
01
When Bolt's preview works but the deploy doesn't
Bolt's preview environment forgives a lot of config sins. Production won't. The engineer joins, sets up env vars, fixes the runtime, gets the deploy out the door.
02
When you need a backend Bolt didn't generate
Bolt scaffolds a frontend cleanly; the API surface is often missing. A Relay engineer wires it up — Postgres, auth, jobs, all of it.
03
When the build needs to leave StackBlitz
For real users on a real domain, you'll want to host the app yourself. The engineer mirrors the project to a Git repo and deploys it on Vercel or Cloudflare.
Common questions
- Can I keep working in StackBlitz with the engineer?
- Yes. The engineer joins your screen and can suggest changes inline; the StackBlitz project stays under your account.
- What if I want to migrate off Bolt?
- Common move when the prototype starts being used. The engineer mirrors the project to a fresh Next.js or Remix repo and sets up the deploy.
- Do you support Bolt's WebContainers runtime?
- Yes for live debugging. For production, the engineer moves the runtime to a host that can serve real traffic.
Related reading
- Field notes · 9 min readAnatomy of the handoff: what we learned shipping the first 1,000 sessionsA median match in seconds isn’t a marketing number; it’s a system constraint we engineered toward and missed by 16 seconds in the first month.
- Research · 17 min readWhen does an AI build want a person? A study of 4,200 stuck momentsWe logged every press in the first quarter of the private beta. Four patterns explain almost everything.
- Essay · 11 min readThe irreducibly human moment in softwareAn argument for why software engineering doesn’t shrink in the age of AI, it sharpens, and moves to a new place in the build.