Lovable pricing and credits: shared balance, limits and cancellation

Establish the workspace arrangement

Current pricing guidance ties the plan to a workspace and describes shared credits for invited members. Adding people is not the same as adding identically priced seats. Identify the workspace agreement and balance first. This review did not establish a verified paid entry amount, so use the period and fee shown at checkout. If an individual pilot and company work belong to different workspaces, do not assume the same balance covers both. Project location is part of the budgeting assumption because it determines which agreement and administrators govern the actual work.

Track purposes within one balance

Official material describes a balance usable for building, Cloud operation and AI features inside published apps. Reporting those purposes separately does not mean three independent paid wallets exist. User activity can continue after development pauses, so track the published workload too. The vendor says credit value and consumption rates depend on plan and feature. Do not compare nominal counts with another vendor’s tokens or even a different Lovable plan without aligning the work. Measure the same accepted change or operating scenario, then reconcile it with the actual workspace usage record.

• Choosing Lovable: from a web prototype to maintained software

Interpret mode-specific use

Examples on a pricing page are illustrations, not guaranteed prices for your own revision. Record the mode, task complexity and consumption shown for the actual interaction. Rebuilding the same screen without settled requirements can consume both credits and supervision time. Define input, storage, roles and preserved behavior before deciding that capacity must grow. Separate a high volume of necessary work from repetition caused by unresolved assumptions. That distinction makes a purchase explainable and avoids interpreting a larger balance as a solution to an application specification nobody has yet agreed how to verify.

Hypothetical budget: build and run

For a hypothetical contact app, suppose the month contains four small revisions and customer submissions. Track the fixed agreement F, build consumption B, Cloud C and in-app AI A, converting usage according to the actual plan. Four revisions is your planning example, not a guaranteed product allowance. If the app does not use AI, verify whether A is absent from the configuration. Apply included grants once, then model a small and higher-traffic month separately. This exposes ongoing operation that remains even when no one asks the builder to generate another feature.

• Lovable alternatives for app ownership and code handoff

Manage expiry and limits

Credit categories have expiry conditions, and daily grants should not be assumed to roll over like purchased resources. Inspect expiry and eligible use as well as the balance. For a shared workspace, examine member, project and workspace controls and alerts where available. Assign the person who receives a notification and the person who investigates consumption afterward. A limit without that response process leaves the operating decision unresolved. When considering a longer agreement, include whether the purchased resources will be usable within their conditions rather than judging only the apparent discount or total nominal credit count.

Inspect credit treatment on cancellation

The documented web flow stops paid renewal through a move to Free. After the billing period, unexpired subscription and rollover credits are frozen, while purchased top-ups and other categories can have different treatment. Do not summarize this as either every credit remaining freely usable or the entire balance immediately disappearing. Inspect category and expiry in the actual account. Separately review published applications, source synchronization and database operation. Decide what continues, and have another maintainer verify the code and required configuration before treating the financial change as a completed service handoff.

• Bolt pricing: monthly Pro, tokens and publication capacity