[verdict][curated prompt][source: lovable.dev]
Can I vibecode Lovable?
// the value is the network, the data or the infrastructure
The wrapper is easy: a CLI that sends your brief to a model, writes the files, and starts the dev server is one sitting of work. The model doing the writing is the actual product, and you cannot rebuild that. Everything Lovable puts around it, the hosted preview, the deploy, the database wired up for you, and a non-developer being able to use any of it, goes with the subscription.
confidence: high
what it is: Prompt a full web app into existence, with hosted previews and one-click deploy
Buildability index · an editorial game
- Price 25 $/month weight: plus 3
- Time closest consolation build: one sitting weight: minus 1
- Category developer tools no weight
- Moat proprietary models · infrastructure scale weight: minus 4
- Confidence high weight: plus 1
- What you lose 4 items weight: minus 2
- Site lovable.dev (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Send a plain-language brief to a model API, have it write a small React app into a local folder, run it, and keep iterating in the same conversation.
what you need
- Node 22
- Anthropic or OpenAI API key
- git
The wrapper is a weekend. The model inside it is not, and neither is handing a working URL to someone who has never opened a terminal.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build me a local brief-to-app generator to replace Lovable. Requirements:
- A Node 22 CLI: `vibe new "a habit tracker with a weekly grid"` scaffolds a Vite +
React + TypeScript app into ./apps/<slug>, then edits it in a loop. Generated apps
persist to plain JSON or SQLite via better-sqlite3.
- Call the Anthropic or OpenAI API with the key from .env and ask for whole files
back as JSON, path plus contents, never prose I have to dig out of a code fence.
- Every round is a git commit on a branch and prints the diff first. `vibe undo` is
a git revert, so nothing the model does is unrecoverable.
- After each round run `npm run build` and `tsc --noEmit`, feed failures back, retry
three times, then stop and show me the error instead of looping.
- `vibe preview` runs the Vite dev server on localhost:5173. No accounts, no
telemetry, nothing leaves my machine except the model calls.
- Keep the transcript, file tree, and last diff in .vibe/session.json inside the app,
resend only the files I named, and print tokens and cost per round.
- Out of scope: hosted previews, one-click deploy, and team collaboration. Do not
build a web UI, the terminal is the interface.
- README: which key to set, what a typical app costs, and the honest warning that the
output is only as good as the model behind it.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- the frontier model, which is the actual product
- hosted preview URLs and one-click deploy
- a database and auth wired up for you
- a non-developer being able to ship anything at all
Why people still pay
People pay because the model is the product and the wrapper is the delivery, and because Lovable turns a brief into a deployed app with a database behind it without anyone opening a terminal. The subscription buys model access, safe execution, and hosting that makes the result shareable.
moat: Proprietary models Infrastructure scale what a moat is
frontier models, context infrastructure, and execution safety
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (2) — and why
- bolt.diy (si apre in una nuova scheda) — MIT source, but its WebContainers runtime needs a commercial licence for production business use.
- Continue (si apre in una nuova scheda) — Acquired and read-only, and an editor agent was never a hosted prompt-to-app product.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- bolt.diy (opens in a new tab) — Open-source prompt-to-app builder, bring your own model.
- Aider (opens in a new tab) — Terminal coding agent that commits its own diffs.
- Continue (opens in a new tab) — Open-source coding agent for IDEs and multiple model providers.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
