Skip to main content

Buyer guide

Lovable Credits & Spend Checklist

Which plan and credit tier to buy, what consumes credits across building, hosting, and AI features, and the limits and alerts to set before a workspace grows.

Reading time
3 min read
Sources
11 cited
In this piece
Lovable+27 Positive

A Lovable workspace that runs out of credits stops the AI features in its live apps and can pause apps on the built-in backend. Since June 18, 2026, hosting and the AI gateway have drawn on the same balance as building, and Lovable charges no per-seat fee. Set credit limits per member and per project before more teams draw on that balance.

When you need this

  • You are moving builders from Free to a paid workspace.
  • Several teams will draw on one workspace's credits.
  • Apps built in Lovable now serve users and run backends and AI features.

Evaluation criteria

  1. Pick the plan by its controls

    Pro or Business?

    Look forPro starts at US$25 a month and Business at US$50 for 100 credits, or US$250 and US$500 billed annually. Business credits cost twice as much. The plan adds SSO and restricted projects, plus workspace-only publishing and default training exclusion. Tiers reach 10,000 credits at US$2,250 a month on Pro and US$4,300 on Business.

  2. Know what a request costs

    What consumes building credits?

    Look forPlan mode costs 1 credit per message plus research. Build mode charges by complexity. Documented examples cost 0.50 credits for a style change, 1.20 for authentication, and 2.00 for a landing page with generated images. Chat mode uses a daily allowance first under pricing through October 31, 2026. A /goal run costs more.

  3. Count the running costs

    What do live apps consume?

    Look forSince June 18, 2026, Cloud hosting, the backend, and the AI gateway draw on the same credits as building. Free, Pro, and Business get a monthly grant of 20 Cloud and 4 AI credits first. Budget for them per live app. When credits run out, a published site keeps serving pages, but AI features stop and apps on the built-in backend can pause.

  4. Plan for expiry

    When do credits disappear?

    Look forMonthly credits roll over but expire two months after issue. Annual-plan credits last until a month after the year ends. The 5 daily build credits reset at 00:00 UTC without rollover. Top-ups last 12 months and cost US$15 per 50 credits on Pro or US$30 on Business.

  5. Set limits and alerts

    Who can spend how much?

    Look forOn paid plans, owners and admins can cap credits by member, project, group, access token, or workspace. Set low-balance alerts. By default, Lovable asks before spending more than 20 credits on one message, and it charges nothing for a request stopped before it changes anything. On Business and Enterprise, the Action center (October 16, 2026) lists projects whose credit usage rose sharply.

  6. Watch the fix loop

    Where does spend leak?

    Look forStop a repeated fix and plan again, or assign it to an engineer. Each attempt costs credits. One builder requested a seven-word text change and received unrequested edits four times. Biron Clark found features that looked complete but failed underneath.

Questions to ask vendors

  1. How many builders and projects will draw on the workspace, and which monthly tier covers the pilot?
  2. Which apps run a Cloud backend or AI features, and what do they consume each month?
  3. What limit applies per member and per project, and who is alerted at a low balance?
  4. Do we buy annual billing, given when monthly credits expire?
  5. At what spend on one app do we hand it to engineering?

Red flags

  • No member or project limits on a shared workspace.
  • Comparing Pro and Business on credit price alone, without the controls Business adds.
  • Apps with live users on a workspace that can run out of credits, which can pause their backends.
  • The same bug sent to Build mode again and again with no plan and no engineer involved.

Products in this piece

Sources

Official documentation
9
Public source
2
  1. Lovable pricingOfficial documentationlovable.dev
  2. Lovable docs: Subscription plansOfficial documentationdocs.lovable.dev
  3. Lovable docs: Credits and usageOfficial documentationdocs.lovable.dev
  4. Lovable docs: Usage limits and alertsOfficial documentationdocs.lovable.dev
  5. Lovable docs: Lovable CloudOfficial documentationdocs.lovable.dev
  6. Lovable docs: AI features for your appOfficial documentationdocs.lovable.dev
  7. Lovable docs: Plan a change in Plan modeOfficial documentationdocs.lovable.dev
  8. Lovable docs: Implement changes in Build modeOfficial documentationdocs.lovable.dev
  9. Lovable docs: ChangelogOfficial documentationdocs.lovable.dev
  10. Responsible_Sleep_42 in r/lovable: minor edits that come back changed and cost credits (Aug 17, 2026)Public sourcereddit.com
  11. Biron Clark: Can a Marketer Vibe-Code a Working App? (May 26, 2026)Public sourcedev.to

Keep reading

  1. Buyer guideLovable Internal Tools Playbook: From Prompt to a Tool Your Team Can TrustWorkspace setup, knowledge, backend choice, plan-then-build habits, and the scan, access, and owner checks before an internal tool goes live.
  2. Buyer guideLovable Security & Data Access ChecklistRow-level security, project and app visibility, training defaults, SSO, scans, and the April 2026 exposure, checked before a Lovable app touches company data.
  3. Buyer guideHanding a Lovable App to EngineeringHow Git sync works, where it stops, and the repository, environment, and review setup that lets engineers or coding agents take over a Lovable app.
Read the research