Lovable · active

Lovable

Lovable is an AI app builder. Current pricing describes one credit balance for build, Cloud, and deployed-app AI; official credits-and-usage still says some workspaces are on the previous Cloud and AI balance during rollout. This overview tracks current plans; zero-credit outcomes live on a separate page.

Verified

Last verified Sep 10, 2026, 6:00 PM UTC

Direct answer

Current docs describe one balance, with a rollout caveat

Free includes 5 daily build credits, capped at 30/month, plus temporary Cloud and AI grants. Pro starts at $25/month for 100 monthly credits. Pricing presents one balance for build, Cloud, and AI. Credits-and-usage and the 13 June 2026 billing blog say some workspaces still use the previous Cloud and AI balance until they migrate. At zero credits on the unified model, published pages keep serving; building stops and Cloud/AI can pause.

If the question is what happens at zero credits, use Lovable credits vs hosting. The four-builder matrix is deployment limits.

Official source conflict

Official sources disagree

Unknown — conflicting Whether every Lovable workspace currently uses one credit balance for build, Cloud, and deployed-app AI

  • Source A: Lovable pricing — The live pricing FAQ defines credits as one balance that can pay for building, hosting with Cloud, and AI features in user apps. Paid plan credits are added to that balance monthly and can be used flexibly across those uses.
  • Source B: Lovable credits and usage — Credits-and-usage describes the current model as one credit balance, and on the same page states the update is rolling out gradually. Some workspaces may still see the previous Cloud and AI balance experience. The 13 June 2026 billing blog says unmigrated workspaces keep their current two-balance setup until they move.
  • Applies to: Workspace-dependent during the 13 June 2026 unification rollout. Which model a given workspace is on is account_dependent.
  • Decision impact: Do not publish one-balance as unconditional Fact for every workspace. Zero-credit outcomes on credits-and-usage (pages stay live; building stops; Cloud/AI can pause) apply to the unified model. Unmigrated workspaces still have a separate Cloud and AI dollar balance until they migrate.
  • TraceCheck status: Unresolved — Derived outputs must not treat one side as settled Fact.
  • Current interpretation: TraceCheck records unified billing as the documented current model on pricing and credits-and-usage, and records the same credits-and-usage page plus the 13 June 2026 blog as official evidence that some workspaces have not migrated.
  • Last checked Sep 10, 2026, 10:00 PM UTC

Current plans and access

Access and sources

Category
app builder
Access model
Workspace credit subscription covering build messages, Cloud hosting/backend, and deployed-app AI gateway usage
Decision categories
subscription service
Open source
No
Platforms / access
lovable.dev web builder, Lovable Cloud, GitHub / GitLab / Bitbucket sync
Verification notes
  • Current pricing and credits-and-usage describe one credit balance for building, Cloud, and deployed-app AI gateway usage. The same credits-and-usage page and the 13 June 2026 billing blog say unification is rolling out and some workspaces still use the previous Cloud and AI balance. Do not treat one balance as Fact for every workspace. That model is not the same as Bolt tokens versus Bolt hosting.
  • Official docs: a live published site does not consume credits on its own; Run credits cover backend and AI work the app does while it runs.
  • When the workspace has no available credits: building stops, published pages keep serving, deployed AI features stop, and Cloud backend services can pause with data retained.

Compare cost and limits

See Lovable alongside other tracked AI coding tools, with incompatible quota units kept separate.

Verified change history

Filter global changes

No verified changes match this view. Pending detections are intentionally private.