Why Your Lovable App Uses Credits Even When You Stop Building
A Lovable work app with no AI feature paused for lack of credits after you stopped editing it. What is still spending them?
- Building and running apps share a credit balance.
- A 100-credit allowance is not a promise of 100 prompts or a fixed number of apps.
- After replenishing credits, select Wake up to restart a paused backend.
An app without AI still uses infrastructure
Lovable’s June 13 billing announcement combined build credits with the previously separate Cloud and AI balance. Finishing development does not make a deployed backend free to operate.
A Reddit user whose work app had paused asked why it needed credits despite having no AI feature. They later confirmed it used Lovable’s built-in database. That is the distinction: the app can consume infrastructure without asking a language model anything.
100 credits are an allowance, not a production quota
The official pricing page starts Pro at $25 on monthly billing with 100 monthly credits. The subscription guide lists monthly grants of 20 Cloud credits and four AI credits for Free, Pro and Business. These grants have specific uses.
Usage rules spend those grants before general credits. Build pricing varies with the work performed; Plan mode starts at one credit plus any subagent research. There is no fixed conversion from the allowance to finished apps or prompts.
Look at Run usage when you have stopped editing
Go to Workspace settings → Plans & credit usage → Usage details. Compare Build credits with Run credits and filter by project. Run includes Cloud, app AI and metered connector usage; Cloud covers resources such as databases, storage, networking, compute and realtime services.
For an individual development request, open the response’s options and check Credits used. For an already deployed app, the Run breakdown is the more relevant starting point.
A live page can have a paused backend
Lovable’s recovery guide says published pages keep serving when credits run out. Database, storage and authentication pause when both the Cloud grant and general credits are exhausted. Data is retained, but access and export wait for services to resume.
Daily build credits cannot pay for Cloud. Once eligible credits are available, open More → Database → Wake up. Replenishing the balance and waking the backend are separate steps.
A member’s build limit does not cap hosting
On paid plans, owners and admins can configure Usage limits & alerts. User limits cover Build only. To control operating usage, choose a project or workspace scope.
A usage rule can notify, block or do both. A low-balance alert only notifies. For a customer-facing app, choose the spending threshold together with the consequence of reaching it.