Every Bolt.new alternatives list answers with another AI builder. Before you pick one: a lot of Bolt projects are a landing page with ambitions, and the subscription you already pay for writes those.
Claude and ChatGPT produce a complete static page from a description and revise it when you say what is wrong. What they cannot do is give the result an address, keep its versions, or collect somebody's remarks. That is the part to bolt on, and it takes one prompt.
One prompt: try the page without a builder
If that describes your project, you already own both halves of the swap. Paste this into Claude or ChatGPT.
Build this as a single static bundle: index.html plus one style.css, no build
step, no framework, no client-side router. Multi-page is fine as separate
.html files that link to each other.
What it is: [one sentence]. Who it is for: [one sentence]. The one action:
[what you want them to do].
Style: [two words], and specifically oversized headline, high contrast, one
accent colour, generous whitespace, system fonts. Real copy, no placeholder
text.Then time it against the same brief in Bolt, including the step where the result gets an address. Yours is the number that decides, so we publish none of our own. The publishing and review prompts are in AI website prompts.
The one line of Bolt's documentation worth reading first
If you do stay on a builder, read this before your first publish. Bolt's Netlify guide explains the terminology plainly: "Bolt calls this feature Publish whereas Netlify calls it Deploy." Then the rule that matters: a new project defaults to Bolt hosting and can be switched to Netlify before the first publish, but once it is published to Bolt hosting it cannot be switched to Netlify without creating a new copy.
Not a scandal, a sequencing detail that costs you a rebuild if you learn it in the wrong order. Decide where the thing lives before you press Publish.
The download path is on the same page: "Run the project build command (usually npm run build). Click Download to download the project."
So the output is portable, which sharpens the question: portable to what? A Bolt project is commonly full-stack, and the part that talks to a database does not become static by being downloaded. The built front end can move. The backend keeps running somewhere.
If it is a full-stack app, this is not us
- The project needs a server, a database or user accounts. Birta serves static browser files, nothing else.
- Your addresses have to stay regular paths. A single-page app can be published. Its in-app navigation has to run through
#: with regular paths, opening or refreshing any path other than the root returns “page not found”. - It needs to take payments on your own site. Not something Birta does yet.
- You need form submissions routed to Slack, Telegram or a webhook. Ours arrive in the project panel and an email digest only.
If the built front end is all you need to keep, it is static files and the rest of this page applies.
What Birta adds after the agent writes it
- Publish from the same conversation, and get back that version's own permanent address.
- Versions and rollback, so undoing is choosing the previous version rather than re-publishing.
- A review link that needs no account. Remarks are pinned to elements on a frozen version; your agent reads the numbered threads and fixes them in the same draft. It cannot reply or resolve, so closing them stays with you.
- A declared lead form, with submissions in the panel plus an email digest roughly fifteen minutes after the first.
All on the free tier. A custom domain needs Solo or Pro, and free keeps the badge.
The honest alternatives
| Instead of Bolt.new | What it is for | Worth knowing |
|---|---|---|
| Lovable | Prompt to app with an optional backend | Its docs are the clearest of the set about what builds as a static frontend |
| Replit | App with server, database and deploy together | Its own hosting is the product, and its docs say Agent-built apps cannot use the cheap static tier |
| v0 | Front-end and UI, Next.js output | Export documented as a flat yes; the output wants a Next.js platform |
| Base44 | Apps with auth and data for non-developers | Two-way GitHub sync requires its Builder plan or higher |
| Bubble | Serious no-code applications | By its own documentation, no way to export the app as code |
| Cursor or Claude Code | An agent working on files you own | Fewest moving parts; the option this page argues for |
| Dyad | Local, open-source app building | Keeps everything off someone else's cloud |
Publish the static half without a build step
Versions, rollback and account-free review come with it, on the free tier.