Lovable

You will love Lovable if you want to hand someone a prompt and get back a deployed app with auth and a database already wired, and the daily trait is that the backend comes with the app, so a prototype that works on Tuesday is the same URL a customer sees on Friday.

What wears on you is that credit consumption is variable with no upfront estimate, and there is no terminal, so the moment you need to run a script you are somewhere else. Pick it for MVPs in TypeScript with a deadline. Pick Claude Code for an existing repo where the shape is already decided.

The meter is the worst thing. A Build mode message can run for up to ten hours. The credit check-in defaults to 20 credits; Pro starts at 100 for $25. An agent that gets lost on a bug can spend a fifth of the month before it asks.

The consequence: lower the check-in threshold before the first real task, and treat any message that runs past an hour as a bug report. A cost estimate before the run would change this verdict. What it does right: the undo button and the diff view are real guardrails, and you will use both.

Build mode's verification is documented: it observes build errors, inspects console and network output, and reproduces issues through browser testing, which is a closed loop most builders on this board do not have. Context is the project the platform already hosts, so gathering is trivial and edits land on files the platform owns.

The cost model is unprincipled: credits scale with files touched, exploration and tool use, with no estimate in advance, so the loop's thoroughness and its price are the same variable. The observation: a builder that verifies its own work and cannot estimate its own cost has solved the harder problem first.

Pro runs to $2,250 a month and Business to $4,300, a ladder nobody publishes for a product people are not paying for, and a self-serve ladder that high means the sales team is the pricing page. The moat is Lovable Cloud: once auth, data and hosting live there, the code is portable but the app is not, which is the switching cost every hosted builder wants and few have built.

Likely acquirer: a cloud or design-tool vendor that wants the funnel and the backend it feeds. Position: long, hedged by Git export, and watch whether Cloud pricing rises faster than credits.

The demo is a working app from one prompt. Procurement: Business is $50 a month with SSO and role-based access, so $3,000 a month for sixty seats before top-ups; Enterprise adds SCIM and audit logs at a volume price. The meter is variable credits with no estimate in advance, so budgeting is a guess until a team has a month of history.

Engineers cannot open a terminal, so this is for product teams, not the platform team, and nothing runs in CI. Onboarding is a login. Approved with conditions: a fixed credit budget for the product team, and Enterprise only if audit logs are required.

I cannot run it, read it, or point it at my own model, and even the agent does not get a shell, so the whole thing is a web app that writes web apps. What I can bend: the MCP server at mcp.lovable.dev takes a plain http entry in my mcpServers config, so an agent I control can drive Lovable as a tool while I keep the real work at home.

That is a better handle than most closed builders offer, and it means the platform is scriptable from outside even if not from inside. Grudging respect for shipping that before most editors did. Nothing to fork.