Migrate from Bolt.new when you need a real build pipeline
Bolt runs your app in a browser sandbox. OOretz Factory runs the build on a real Linux bridge node, actually launches the server, hits it with a POST + GET smoke, and gives you a downloadable Next.js + libSQL workspace. Same prompt, real artifact you own.
Before you start
- ·Your existing Bolt project (the prompt you used, or a link to the StackBlitz preview)
- ·An OOretz Factory account
Steps
- 01~2 min
Capture the Bolt prompt
In Bolt, find the original prompt — it's usually in the chat history. Copy it verbatim. You'll feed this to the factory unchanged as a starting point.
- 02~2 min
Open /admin/factory and paste
In the interview chat, paste your Bolt prompt. The factory will keep the surface as web — the only pipeline that ships verified end-to-end today (desktop and mobile are roadmap).
- 03~8 min
Wait for the build + smoke to complete
Bolt previews are instant because the WebContainer is just running your code in the browser. Factory builds take 4-12 minutes because they actually run `npm install`, `next build`, launch the server, and hit it with a POST + GET smoke against the running app on the bridge.
🪤 GotchaThe factory will NOT skip the build step. Even simple web apps go through compile + launch + smoke verification. The workspace tarball has a SHA-256 hash and is downloadable.
- 04~4 min
Download and run locally
Get the workspace tarball from the Delivery panel. Untar, `npm install && npm run dev`, and the same smoke that gated the pass on the bridge runs locally too (see the generated README for the curl).
✓ Expected outcome
A real Next.js + libSQL workspace — not a sandboxed preview. Run it locally, deploy to Vercel / Cloudflare / Docker / your own infrastructure. Source you own, no hosted dependency.
Troubleshooting
Build is way slower than Bolt was+
Correct — the factory runs a real compile + launch + smoke verification on real hardware. That trade-off is intentional. See ADR 0006 on why we ship structured proof packs.
My Bolt app used a npm package that's not installed+
The factory installs packages declared in the manifest. If the package was only added in Bolt's WebContainer at preview time, mention it in the prompt: "Use [package] for X."