Usage and costs

Every Cloud project consumes Run credits while its deployed app runs: database work, AI calls, file storage, network traffic, and backend compute. The Usage view shows exactly what a project consumes, so you can see what drives spend before adjusting anything. To open it, go to Cloud tab → Usage. Access follows your workspace role, not your project role: workspace owners can always open the view, and workspace admins can on paid plans. On workspaces that haven’t moved to unified billing yet, the view is visible to everyone who can open the project.

​

The Usage view

The Usage view shows the project’s run credit usage: a chart of the credits its deployed app uses per day, with a total for the selected time range. It is the same breakdown you get from Settings → Plans & credit usage → Usage details by selecting Run credits, already filtered to the project. See Cloud costs for what drives this usage. The time range defaults to Last 30 days. You can switch to Last 90 days or pick a custom range of up to 90 days. Run credit usage may not appear immediately after your app is used. Below the chart, usage is broken down by category, sorted from highest to lowest:

• Database: storing and working with your app’s data, such as users, orders, and messages. Split into Database server, the work of reading and saving that data, and Database storage, the amount of data your database stores. Larger instance sizes support more traffic but use more credits.
• AI: AI features in your app, such as chat or image generation, broken down by model.
• Compute: your app’s code running behind the scenes, such as processing payments or sending emails.
• Network: data sent or received by your app, such as API responses, downloads, uploads, images, and media.
• Storage: uploaded or generated files your app stores, such as images, documents, and videos.
• Realtime: live updates sent through your app, such as chat messages, notifications, or collaborative updates.

The number next to each category shows how many credits it used in the selected time range. For example, if Compute shows 1.6, then 1.6 credits of your Cloud spend in that period came from compute usage. Use the breakdown to see which resources drive the project’s Cloud spend, for example before resizing your instance or fixing slow queries.

​

Monthly grants

For details about Cloud and AI gateway usage costs, top-ups, auto top-up, alerts, and usage tracking, see Credits and usage.

​

What drives Cloud usage

Cloud usage usually increases when more people visit your app or when it stores more data and files. Larger uploads and downloads, more API responses and media, more background code, and more Realtime messages all add usage too.

​

What drives AI usage

AI gateway usage is measured when AI features inside your deployed app make model calls. These requests are separate from the Lovable agent that helps you plan, build, and edit your project. Each model call deducts credits based on the model used and the number of tokens processed. AI gateway usage rates are based on the underlying provider model costs. See AI features for your app and the supported model list.

​

Reduce a project’s Cloud usage

If a project uses more credits than it should, work through these in order of impact:

• Pause the project’s Cloud backend when it isn’t actively used, from Cloud tab → Overview → Advanced settings. Lovable also pauses Cloud projects automatically after a period of inactivity, so manual pausing mainly helps for projects with scheduled jobs or other background activity. See Pause Cloud.
• Right-size your instance. A larger instance uses more credits per hour while your app runs. On paid plans, review and change the instance size from Cloud tab → Overview → Advanced settings. See Upgrade instance.
• Fix slow database queries so your database does less work per request. Ask Lovable in chat to find and optimize the slowest queries. See Find and fix database performance problems.
• Remove unused files from storage, since stored files continue to use credits, including while a project is paused.
• Review Jobs: frequent or long-running scheduled jobs add up.
• Remove Lovable Cloud from projects that don’t need a backend at all. This stops all Cloud usage for the project, but it permanently deletes the project’s Cloud data, so export anything you need first. See Remove Lovable Cloud.

​

FAQ