Stacks / AI chat
bolt.diy
Prompt-to-app you host. bolt.diy is MIT — Bolt.new, Lovable, and v0 without the hosted builder seat.
The problem
Bolt.new, Lovable, and v0 are hosted prompt-to-app products. You wanted that loop with a model you bring. bolt.diy is MIT (stackblitz-labs/bolt.diy) — the community fork of Bolt.new that talks to any LLM you configure. This is not Lovable's every visual editor SKU, v0's Vercel deploy graph, or Bolt's hosted runtime. You still pay tokens. Appsmith/ToolJet stay internal tools on a database (/replace/retool).
Replaces
Lovable / Bolt.new / v0
Replace Lovable Replace Bolt.new Replace v0 See all best open-source AI coding assistants
Estimated SaaS saved
$1,200
per year, small team, before lock-in
Start on RailwayBaserow / Appsmith if this is an internal tool on a database, not prompt-to-app
Placeholder: bolt.diy as a UI pointed at an OpenAI-compatible API (LiteLLM or a vendor). Persist config. No one-click template in this repo yet — Start on Railway. Internal tools stay on /stacks/baserow-appsmith.
The stack
Cost table
| You stop paying | Typical / year | Self-host instead |
|---|---|---|
| Lovable / Bolt.new / v0 (small team) | $1,200 | bolt.diy + your models |
Agent setup prompt
Replace Bolt.new, Lovable, or v0 with bolt.diy pointed at models you bring. - Official docs, persist config, point at LiteLLM. Generate one small app you actually want. Do not claim Vercel v0 deploy graphs or Lovable's hosted visual OS. - Internal tools on a grid stay on /stacks/baserow-appsmith. Write AGENT_PROMPT.md.
Also as markdown: /stacks/bolt-diy.md
FAQ
- Lovable, Bolt.new, or v0?
- Same published stack. bolt.diy is the MIT builder you host. You bring the model. Hosted deploy graphs stay behind.
- Is this Appsmith?
- No. Appsmith/ToolJet are internal tools on a database — /replace/retool. This page is prompt-to-app.
- Do I still pay tokens?
- Yes, unless you run local weights. bolt.diy is the UI. It is not free inference.