Lovable credits running out? What an AI-built app really costs to run
When your Lovable credits run out, the published site stays live, but building stops, AI features inside the app stop working, and an app on Lovable's built-in backend can pause until credits are added. That happens because Lovable uses one credit balance for building, chatting, hosting, the built-in backend (Cloud), AI features and connectors (Lovable, Credits and usage). So the real cost of an AI-built app is not only the plan. It is the plan plus everything the live app uses, and each part can be measured and capped.
One balance pays for building and running
Lovable splits usage into Build, Chat, Cloud, AI gateway and Connector. Plan mode costs one credit per message. Build mode is usage-based: its examples run from 0.50 credits for a small styling change to 2.00 credits for a landing page with images. Cloud, AI and connector usage is metered by the resources, models and tokens used.
- Free, Pro and Business workspaces get 5 daily build credits, plus a monthly grant of 20 Cloud credits, 4 AI credits and 1 connector credit. Lovable calls the Cloud and AI grant a temporary offering that may change (Lovable, Project usage and costs).
- Those usage grants do not roll over. Unused monthly plan credits roll over while the subscription stays active, and on monthly plans they expire two months after issue. Top-up credits expire 12 months after purchase.
- The grants and general credits are not separate pools. Once a grant is used, Cloud and AI usage draws on the same credits you build with.
What stops when the balance reaches zero
Lovable's recovery page says sending a new message opens a dialog instead of building, AI features in deployed apps fail, and the backend pauses once the Cloud grant and general credits are both gone. While it is paused, Lovable keeps the data, but you cannot reach or export it until the services run again (Lovable, Out of credits). Owners and admins can add credits; on Free that means upgrading, on Pro and Business a one-time or automatic top-up.
The five costs of a live app
- The builder plan. Lovable's plans page lists Free, Pro, Business and Enterprise. On 15 November 2026 it listed the 100-credit Pro tier at $25 a month and the 100-credit Business tier at $50 a month, and it points to Lovable pricing for current prices (Lovable, Subscription plans).
- Database and hosting. Run credits cover database work and storage, compute, network, file storage and realtime. A larger database instance uses more credits, and stored files keep costing credits even while the backend is paused.
- AI inside the app. Every model call your app makes is priced by model and tokens.
- Email. Lovable says each paid workspace includes 50,000 transactional emails a month, with further emails at 4 credits per 1,000, and hourly caps by plan. Sending needs a domain whose DNS you manage (Lovable, Custom emails).
- The domain. A domain bought through Lovable is paid at checkout, auto-renews by default, and the renewal price can differ from the purchase price (Lovable, Buy a domain).
If your app uses your own Supabase project instead, the database is billed by Supabase, not Lovable. Supabase's Spend Cap is only on its Pro plan and does not cover items such as compute, custom domains or point-in-time recovery (Supabase, Cost control).
How to keep the cost predictable
Lovable gives paid workspaces a Usage limits and alerts page under Workspace settings (Lovable, Usage limits and alerts). Limits can cover the whole workspace, one project or one member, and can notify or block. Low-balance alerts only notify. Lovable also sends a notice when daily run usage is at least twice the 7-day average and at least 5 credits. Choose a block carefully: pausing Cloud stops the backend of every covered project, published apps included, and adding credits does not lift a block until the period resets or the limit changes.
Our own advice, on top of the docs:
- Budget building and running separately. Set a monthly Build limit that blocks, and a Run alert that only notifies, so a busy month of edits cannot take the live app down.
- Check Usage details monthly, by project.
- Pause backends you are not using, delete stored files nobody needs, and review scheduled jobs, as Lovable's own usage page suggests.
- Keep the code in GitHub and take regular data exports, so a paused backend is never the only copy.
When running it elsewhere is cheaper
Once an app is stable, most of its cost is running, not building. On Cloudflare, Workers Free allows 100,000 requests a day, Workers Paid starts at $5 a month per account, requests to static assets are free, and D1 Free includes 5 million rows read a day (Cloudflare, Workers pricing). Cloudflare Registrar says it charges only what is paid to the registry for a domain (Cloudflare Registrar). Moving has its own cost, though: someone has to run the code. Read what moves and what changes on Cloudflare before you decide, and how to export your code and keep it running.
Want a second opinion on the bill?
App Triage ($99 USD) gives you a written diagnosis and plan, including whether moving would cut your running cost. The AI-Built App Audit ($299 USD) is a report-only review. App Rescue and Move to Cloudflare offers a Rescue in place for a fixed $999 USD, or a move to Cloudflare as code you own from $2,999 USD with a fixed quote first.
Sources
- Credits and usage, Lovable docs
- Project usage and costs, Lovable docs
- Low credit balance and out-of-credits recovery, Lovable docs
- Usage limits and alerts, Lovable docs
- Subscription plans, Lovable docs
- Send branded emails from your own domain, Lovable docs
- Buy a domain through Lovable, Lovable docs
- Cost control, Supabase docs
- Workers pricing, Cloudflare docs
- Cloudflare Registrar, Cloudflare docs