Project usage and costs
The Usage view shows you how many credits your live project consumes across hosting, databases, AI features, and backend work. You can pinpoint which features cost the most and ask Lovable how to reduce those expenses.
Anyone with an active or published project who wants to track running costs and reduce credit consumption.
Do this, in order
- 1
Open More, then select Usage from your project menu.
This opens the project credit breakdown chart and detailed resource categories.
- 2
Filter the view by Run credits and select your preferred time range, such as Last 30 days or Last 90 days.
This isolates live app and backend operational costs from credits spent building the app.
- 3
Review the sorted categories beneath the chart, such as Database, AI, Compute, Network, Storage, and Realtime.
The list is sorted from highest to lowest so you immediately see what is driving most of your spend.
- 4
Ask Lovable in the project chat what is driving your run credit usage, or click Optimize your usage below the chart if visible.
Lovable analyzes your backend activity and suggests concrete ways to optimize database queries, adjust instance sizes, or clean up unused files.
Paste this into your project
Review our project's recent run credit usage and backend activity. What is driving our highest costs across database, compute, storage, network, and AI, and what specific optimizations can we make to lower usage?
Words decoded
- Run credits
- Credits spent operating your live app and backend, including hosting, database work, storage, and AI features.
- Build credits
- Credits spent prompting Lovable to create, edit, and update your project.
- Compute
- Behind-the-scenes server work, like handling payments, running scheduled jobs, or sending emails.
- Realtime
- Live data pushed immediately to users without refreshing, like chat messages or live notifications.
Where people get stuck
- Stored files in storage still use credits even if your database is paused.
- Run credit usage does not always appear immediately after your app is used.
- Removing a database to cut costs permanently erases all stored data, so export what you need first.
- Member credit limits only cap build credits; they do not stop a live app from consuming run credits.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.