Lovable, Bolt, v0 and Replit Agent can help turn a brief into software. Your choice should depend on the code and operating workflow you can understand and maintain after the first demo.
Evidence correction: this page previously described a same-MVP test and completion times without published outputs or logs. Those claims have been removed. The following is a documentation-based editorial shortlist and an evaluation plan, not a winner determined by testing.
Four candidates, four questions
- Lovable: its documentation describes natural-language application building, editable code, deployment and Git synchronisation. Check whether its selected backend, secrets handling and ownership workflow fit your application.
- Bolt: use the official help centre to verify the current builder, hosting and integration boundaries. Check what survives when you export or change hosting.
- v0: consult the current documentation for generation and deployment. Evaluate the output inside the framework and repository your team will maintain.
- Replit Agent: its documentation covers an integrated build and deployment environment. Evaluate ongoing hosting, environment configuration and your exit path alongside the agent.
Capabilities overlap and change. We have not established comparative speed, code quality or reliability for these current versions. Do not interpret this list as a universal ranking.
Use one acceptance brief
Build a small subscription inventory. A signed-in user can add, edit and delete a tool with a monthly cost. Each user sees only their own tools. Show the total and handle an empty list. Include clear errors for invalid input. Use sandbox data. Explain the framework, database, permissions and deployment steps. Do not implement real payments in this prototype.
Keep the request identical across candidates. Write acceptance checks before generation so the goal does not move to match whichever demo looks best. Save the generated commit, plan, prompts and the fixes you make.
Inspect more than the happy path
- Create two accounts. Confirm one cannot read or modify the other’s records, including through direct API calls.
- Submit empty names, negative or non-numeric costs, long inputs and repeated clicks.
- Reload after saving and confirm persistence. Sign out and try the protected URL again.
- Simulate an unavailable backend. Check that the interface shows a recoverable error rather than claiming success.
- Search generated files for exposed secrets and debug data. Use separate sandbox credentials.
- Export or synchronise the code and run its documented build outside the original preview where supported.
- Ask a future maintainer to change one field and explain the data model.
Evaluate the whole ownership path
Record the time you spend understanding and repairing the output, not just the first generation. Check dependencies, licence terms, database access rules, tests, deployment configuration and how you roll back. An attractive interface is useful; it is not evidence that account isolation or billing is correct.
Prefer a candidate whose code and operations fit the person responsible for them. If you cannot inspect the generated application, keep the first use case small and involve someone who can review its permissions and failure handling.
Budget credits and hosting separately
Read the current plan rather than relying on this article for a price. Generation credits, model usage, runtime hosting, database storage, third-party APIs and collaborators may be separate. Try a small brief before paying annually and check whether failed generation attempts consume your budget.
Before adding real payments
Use sandbox billing, verify server-side identity and price selection, handle signed webhook events and retries, and define subscription cancellation and entitlement behaviour. The SaaS implementation plan provides the checkpoints and official references. A prototype should remain a prototype until those checks pass.
For editor-based development, read the coding assistant evaluation guide. For a site with no application backend, use the website-builder checklist.
