Project usage and costs

1. 1

   Go to 'More' in your Lovable project.

   This is the starting point to access project-specific settings and usage details.

2. 2

   Select 'Cloud', then 'Usage'.

   This opens the 'Usage view' which shows a chart of your project's daily run credit consumption and a total for the selected time period.

3. 3

   Review the breakdown of usage by category (Database, AI, Compute, Network, Storage, Realtime).

   This helps you understand which parts of your app are using the most credits, allowing you to identify areas for optimization.

4. 4

   If your project uses too many credits, consider pausing its Cloud backend when not in use, adjusting your instance size, fixing slow database queries, or removing unused files.

   These actions can help reduce your project's credit consumption and manage costs.

Show me my project's run credit usage for the last 30 days, broken down by category. What are the top 3 credit-consuming categories, and what steps can I take to reduce usage in those areas?

Run credits

These are like tokens or points your project uses when it's actively running, covering things like hosting your app, using its built-in backend (Cloud), and making AI calls. They are separate from 'build credits' which are used when you're creating or changing your app.

Cloud

This refers to the built-in backend services Lovable provides for your app, such as databases, AI features, file storage, and the computing power to run your app's code behind the scenes.

Instance size

This is like choosing the power level for your app's backend server. A larger instance can handle more traffic but uses more credits, similar to how a bigger engine uses more fuel.

AI gateway

This is the part of Lovable that handles all the requests your app makes to AI models for features like chatbots or image generation.

Tokens

In the context of AI, tokens are small pieces of text (like words or parts of words) that AI models process. The cost of AI usage is often based on the number of tokens sent to and received from the AI model.

• Not checking your project's usage regularly can lead to unexpected credit consumption.
• Ignoring the breakdown of usage categories means you might miss opportunities to optimize specific parts of your app that are driving costs.
• Forgetting that stored files continue to use credits even when a project is paused can lead to unnecessary expenses.
• Assuming monthly grants roll over, as they reset each month and do not accumulate.