Bolt.new vs Lovable: both are coding tools on Scriptiii AI Tools. Bolt.new pricing: Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified) Lovable pricing: Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified) Both have 0 upvotes.
Bolt.new
Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified)
Lovable
Freemium. Free tier with paid upgrades. (indexed from the vendor's public page, not independently verified)
Upvotes
0 vs 0
Bolt.new vs Lovable
Quick verdict
Both turn a sentence into a working web app, so the contest is not demo speed — it is where the stack runs. Bolt.new keeps the environment in your browser tab: its README says the AI controls filesystem, Node server, package manager, terminal and browser console through StackBlitz WebContainers, and Bolt Cloud publishes the result with a managed database, auth and file storage. Lovable is hosted: describe the app and it generates frontend, backend, database, auth and integrations, then owns hosting and SSL while your code syncs to GitHub, GitLab or Bitbucket.
Pick Bolt for the runtime and the source — the agent's repository is MIT. Pick Lovable for the platform and the collaboration surface. Neither is wasted for a developer who will eventually own the repo.
How they differ
The split starts at the runtime boundary. Bolt's stated differentiator is that the AI drives a live environment, not just files: install npm packages, run a Node server, call third-party APIs, deploy from chat. Hence a tagline promising "prompts, runs, edits and deploys" and a free tier that meters tokens — the README says interactions pause until the next day once the daily allowance is spent.
Free tier with paid upgrades.indexed from the vendor's public page, not independently verified
Free tier with paid upgrades.indexed from the vendor's public page, not independently verified
Upvotes
0
0
Best for
AI Agents, Coding Agent, App Builder
App Builder, Prototyping, UI Design
Listed since
2026-11-12
2026-11-15
Owner
Unclaimed
Unclaimed
Tagline
StackBlitz browser-based AI builder that prompts, runs, edits and deploys full-stack web apps.
Describe an app in plain language and Lovable builds and hosts it.
Pricing and pricing details come from the maker's submission. They are not independently verified.
Questions
Do Bolt.new and Lovable list the same price?
Both listings report Freemium. Free tier with paid upgrades. Bolt.new: indexed from the vendor's public page, not independently verified. Lovable: indexed from the vendor's public page, not independently verified.
Which has more upvotes, Bolt.new or Lovable?
Both have 0 upvotes.
What does each maker say Bolt.new and Lovable are for?
Bolt.new: StackBlitz browser-based AI builder that prompts, runs, edits and deploys full-stack web apps. Lovable: Describe an app in plain language and Lovable builds and hosts it.
Lovable's is the opposite: the platform absorbs everything around the app. Its docs describe projects containing frontend, backend, database, auth and integrations in editable code, inside shared workspaces with one credit pool. Its site adds hosting and TLS, payments in over two hundred countries and territories, connectors, security scans and audit logs — a productised operations story, not a runtime story.
Billing differs next: Bolt sells AI tokens plus plan-tiered hosting usage, Lovable sells credits priced per credit rather than per seat. Both meters punish long loops. Code custody differs last: Bolt's codebase is MIT with built-in version history and GitHub sync; Lovable states your code and data stay yours and syncs to GitHub, GitLab or Bitbucket. Both hand you a codebase; only one lets you read the agent.
Architecture and flow
These diagrams are conceptual: how each product is documented to be structured, not measured internals. No component counts, latencies or sizes were observed.
Both branches answer one question — who runs the machine. On the Bolt branch it is your tab: a filesystem, a package manager and a Node process, with Bolt Cloud entering at publish time for database, auth, file storage or functions. On the Lovable branch it is the vendor's: workspace, preview and publish target, with certificates, authentication and payments supplied. That asymmetry makes migration cheap one way: a Bolt project is ordinary JavaScript, so continuing elsewhere is a normal developer move, while a Lovable project exports without the conveniences around it.
Feature comparison
Dimension
Bolt.new
Lovable
Licence (code)
MIT, StackBlitz Inc. repository
No licence file in the sources fetched; hosted platform
Where the stack runs
In-browser WebContainers runtime
Vendor-hosted build and hosting
Terminal and package manager
Present, under AI control
Not described as user-visible in the docs fetched
Backend
Bolt Cloud database, server functions, file storage
Backend, database and auth generated with the app
Database provisioning
Created automatically when the project needs one
Part of the generated app per docs
Authentication
Email confirmation, password reset, Google sign-in settings
Handled by the platform per docs
Hosting
Free bolt.host subdomain on all plans
Hosting and SSL handled by Lovable
Custom domain
Paid plan only
Offered; tier not itemised in the sources fetched
Git export
Built-in GitHub sync plus version history
Git sync to GitHub, GitLab or Bitbucket
Collaboration
Sharing and publishing of projects
Shared workspaces with a common credit pool
Billing meter
AI tokens per day, plus plan-tiered hosting usage
Credits, priced per credit rather than per seat
Paid entry point
Pro; free plan shows a "Made in Bolt" badge
Pro, with Business and Enterprise above it
Self-hosting
Source is MIT and readable; the hosted product is the product
Not described anywhere in the sources fetched
Version history
Built in, independent of Git
Project version history described in the docs
Pricing and packaging
Neither listing carries a price: both catalog entries are freemium with "Free tier with paid upgrades", so packaging comes from each vendor's docs.
Bolt documents two consumer tiers, Free and Pro. Everyone can publish to a .bolt.host address; custom domains are Pro only; free sites carry a "Made in Bolt" badge; each plan includes hosting usage and a site stops displaying publicly when the limit is hit; paid plans can raise it. The listing adds that the subscription is bought inside the app for more tokens or private projects. No dollar figure, token count or hosting quota appeared in the pages fetched, so none is quoted.
Lovable names four plans — Free, Pro, Business, Enterprise — priced by credits, not by projects or seats. The plan tables I fetched list a daily chat allowance; 5 daily build credits (capped at 30/month on Free, uncapped daily on Pro and Business); a 20-credit monthly Cloud grant; a 4-credit monthly AI grant; subscription credits from 100/month on Pro and Business; per-member limits, alerts, rollovers, top-ups and auto top-up from Pro upward; volume credits on Enterprise. Verified students and teachers get 50 percent off Pro, 100 credits monthly for up to twelve months.
One inconsistency is worth naming. The catalog's Lovable description records Pro at $25/month for 100 credits and Business at $50/month, and calls free publishing invite-only across five lovable.app domains. The subscription-plans page fetched here confirms the names and the 100-credit Pro starting point but carries no dollar prices and says nothing about invite-only publishing. Treat those figures as the listing's claim, sourced to lovable.dev, and check lovable.dev/pricing before budgeting.
Choose Bolt.new if
You want to drive the runtime, not just the output; a real terminal and Node server in the tab beats reading generated code in a hosted editor.
You care that the agent is open source: MIT plus a public repo makes the build loop auditable.
Your projects are JavaScript-shaped and will be handed to engineers; ordinary files, GitHub sync and history make that routine.
You want a free live URL with managed database and auth, and can live with a subdomain and a badge.
You accept token metering on a beta product — the listing calls Bolt.new beta.
Choose Lovable if
You do not want to own infrastructure: hosting, TLS, auth, payments and integrations are platform responsibilities.
You build with non-engineers in the loop; shared workspaces, one credit pool and per-member limits are collaboration features.
You need multi-country payments, connectors, security scans and audit logs without assembling them.
Your ceiling is an internal tool, dashboard, portal or prototype — the range the docs describe.
You would rather budget in rollover credits than in daily token allowances.
Migration and workflow notes
Leaving Bolt.new is the easier direction: ordinary files, version history, GitHub sync. The trap is the backend — a Bolt Cloud database, auth settings, file storage and functions are platform services, so a repo alone does not carry them; plan to re-provision.
Leaving Lovable is documented via Git sync, with code and data stated to remain yours, but hosting, certificates, payment plumbing and scans become your work.
Iteration economics differ. Bolt meters tokens, so its README advice — state the stack up front, scaffold before features, batch instructions into one message — is cost control as much as craft. Lovable meters credits on top of daily build credits, a chat allowance and monthly Cloud and AI grants, so short prompts against the daily grant behave differently from long chat sessions billed per message. Neither vendor states a per-action credit table in the pages fetched, so treat any "this prompt costs N credits" intuition as unverified. Both hand you code that still needs reading; Bolt's runtime makes that natural, Lovable's makes it optional.
FAQ
Can I use my own domain?
Bolt: on a paid plan only — the free tier publishes to .bolt.host. Lovable: publishing to a hosted address is documented, but the pages fetched did not itemise which tier unlocks a custom domain, so confirm on lovable.dev first.
Will the code end up in my repository?
Both sync to Git: Bolt to GitHub with version history, Lovable to GitHub, GitLab or Bitbucket. Bolt's extra is that the agent's own source is MIT, so the toolchain is inspectable.
Which is actually free to start?
Both, with a meter. Bolt gives a daily token allowance and a bolt.host site with the badge; Lovable gives daily build credits (30/month cap on Free), a monthly Cloud grant and a monthly AI grant.
Do I need to be a developer?
Lovable targets founders, PMs, designers and ops teams and takes over hosting and payments. Bolt rewards people who can read a terminal. Non-engineers can use both; only one makes the terminal the point.
Bottom line
Bolt sells a runnable, inspectable, MIT-licensed build environment that happens to come with hosting; Lovable sells a productised platform where the app, its backend and its operations are one subscription. Pick Bolt for the runtime and the source, Lovable for the platform and the collaboration surface. Both meter usage, start free, and hand you a codebase you still have to read.