Usage limits and alerts

Credits in a workspace are shared across every member and project, so a single project or member can use more than you planned. Usage limits & alerts gives workspace owners and admins control over that spend: set a credit threshold, choose what it applies to, and decide whether reaching it sends an alert, blocks further usage, or both. Open it from Workspace settings → Usage limits & alerts. It is available on all paid plans.

​

Why use usage limits and alerts

Limits and alerts are guardrails for shared credits, so you do not have to watch the balance yourself. Use them to:

• Cap how many credits a member, project, or the whole workspace can use per day or per month
• Get an email or in-app notification when usage reaches a threshold, without blocking anyone
• Block building when a limit is reached, or pause Lovable Cloud, AI features, and metered connector requests in deployed apps
• Set a default limit for all projects or all members, with specific overrides where needed
• Limit usage for everyone in a group, such as a department or a project team
• Get warned when your workspace credit balance drops below an amount you choose, so you can top up before apps pause
• Cap the credits that requests authenticated with an access token can spend
• Let members who reach a limit request an increase that you approve or deny

​

Prerequisites

Before you set up limits, check that your workspace and role qualify:

• Creating limits and alerts needs a paid plan.
• Only workspace owners and admins can create, edit, or delete limits and alerts.
• Members can open the page and see workspace limits, defaults, and the limits that apply to them and to their projects, but cannot change anything.

​

How limits and alerts work

Every rule you create combines four choices: a threshold (the credit amount), a scope (what it watches), a credit type (which kind of usage counts), and an action (notify, block, or both).

​

Two kinds of rules

Usage limits watch what you spend, and low-balance alerts watch what you have left: Usage limit thresholds are always credit amounts. Low-balance alert thresholds can be a credit amount or a percentage of the credits granted to your workspace. Low-balance alerts never block usage.

​

Scopes

Each limit applies to one scope: For projects and users, you can create a default limit that applies to all of them, plus specific limits for individual projects or members. A default gives each project or member its own allowance rather than a shared pool: with a 100-credit project default, every project can spend up to 100 credits of its own. An enabled specific limit overrides only a matching default. The credit type and period must match, so a daily Build limit does not replace a monthly Build default. Defaults for other credit types or periods continue to apply. Group limits give each current member a separate allowance rather than a shared group budget. Adding or removing someone from a group changes which limits apply to them.

​

Credit types

Limits can watch all credit usage or a specific kind of usage: The indentation shows how the types nest, here and in the dialog: Build and Run are parts of General, and Cloud, AI, and Connectors are parts of Run. A limit on a broader type covers everything under it, so a General limit counts all usage and a Run limit counts Cloud, AI, and connector usage.

​

Periods

Each usage limit counts usage over one of two periods: Low-balance alerts have no period: they always compare your current balance against the threshold.

​

Create a usage limit

You create every usage limit from the same dialog: You can set several limits on the same scope as long as they watch different credit types or periods, for example a monthly Build limit and a daily Cloud limit on the same project. Creating a limit that matches an existing one’s scope, credit type, and period does not add a second one: an Overwrite existing limit confirmation shows the current limit’s amount and behavior, and confirming replaces the existing limit with your new settings. If the limit you overwrite blocks usage and your new one does not, blocking carries over. To stop a limit from blocking, edit it instead. An enabled blocking limit starts blocking as soon as you save it if usage in the current period has already reached the amount you entered. Lovable warns you first, explains what is blocked or paused, and asks you to type BLOCK to confirm.

​

Create a low-balance alert

Low-balance alerts warn you before credits run out. They are especially useful when auto top-up is disabled and your deployed apps would pause without credits. When your balance falls below the threshold, Lovable notifies you so you can add credits in time. Each alert appears in the list with its threshold, its notification channels and recipients, an enable switch, and a menu for editing or deleting it. Use the switch to disable an alert without deleting it. You can set several balance alerts at different thresholds, for example an early warning at 50% and an urgent one at 25 credits. Creating an alert at a threshold that already has one overwrites it: Lovable asks you to confirm, then replaces the existing notification settings with your new ones. Enterprise workspaces start with two email balance alerts, at 25% and 10% of granted credits. You can edit, disable, or delete them like alerts you create yourself.

​

What happens when a limit triggers

​

Notifications

Notifications go out on the channels you selected for the limit. Both channels notify workspace owners and admins, and the person closest to the limit is also notified: the affected member for user and group limits, the project creator for project limits, and the token owner for access-token limits. In-app notifications appear in the notifications panel with a link back to Usage limits & alerts. Blocking limits enter an Approaching state at 80% of the threshold. The Requires attention card at the top of the page lists them under Approaching limits, and usage is not blocked yet. If the limit also notifies, Lovable sends an early warning on the selected channels. Lovable sends each notification once: the warning when a blocking limit reaches Approaching, and the main notification when a limit triggers. Lovable does not notify you again while the limit stays in the same state.

​

Blocking

When a blocking limit is reached, the affected usage stops. For workspace and project limits, the blocking switch in the dialog is labeled for the credit type you picked:

• A Build limit (Block building) stops the people it covers from asking Lovable to build or edit apps.
• A Cloud limit (Pause Cloud) pauses Lovable Cloud features, such as database, storage, and backend services, in the projects the limit covers.
• An AI limit (Pause AI) pauses AI features inside the apps of the projects the limit covers.
• A Connectors limit (Pause connectors) pauses metered connector requests from the apps of the projects the limit covers.
• A Run limit (Pause Cloud and AI features and connector requests) pauses Cloud and AI features and metered connector requests in the projects the limit covers.
• A General limit (Block all usage) blocks all credit usage for the scope, including building and running apps.

For access-token limits, the switch reads Block Cloud usage, Block AI usage, or Block Run usage instead. It blocks requests made with that token without pausing any project. Only Block building and Block all usage stop people from building in Lovable. The other blocking limits pause features in deployed apps or block a token’s requests, and everyone can keep building. Default limits are enforced per project and per member. When one project reaches a project default, only that project is blocked or paused, and the other projects the same default covers keep working. Workspace limits are the broadest: reaching one affects every project in the workspace. People who reach a limit see a message that names the limit and explains what is blocked. Workspace owners and admins see an option to manage the limit, and Lovable asks everyone else to contact an owner or admin. The block stays in place until the period resets, the limit is raised, blocking is disabled, or the limit is deleted. Adding credits or upgrading your plan does not lift a usage block: the limit counts credits already spent in the period, and that number does not change when you add credits.

​

Request a limit increase

Members who reach a blocking limit can ask for a higher limit without leaving their work. When the limit supports requests, the limit-reached message includes Request an increase: the member enters the New limit (credits) and an optional reason, then selects Send request. The message confirms with Request sent. If they try again while the request awaits review, it shows Request already pending. Workspace owners and admins receive a Limit increase requested notification. They review requests on the Requests tab in Usage limits & alerts, which shows the number of pending requests. Each request lists the requester’s name and email address, the current and requested amounts, when it was sent, and the reason. Select Deny to reject a request, or Approve to raise the limit. Approving opens the Approve usage limit increase dialog, which asks How long should the new limit apply?:

• Indefinitely keeps the new amount until an admin changes or removes it.
• Until end of usage period raises the limit temporarily. It applies through the date shown (UTC), then returns to the configured limit. The dialog preselects this option, and the approve button shows the exact date.

A limit with a temporary increase shows a Temporary until badge on its row. The badge shows the date the limit returns to its configured value, and hovering over it shows the raised amount. Use the filters on the tab to review past requests by scope and status (Pending, Approved, Denied, or Cancelled). Approving a request against a default limit does not raise the default for everyone: it creates an override for the requesting member or project only. Group and access-token limits do not support increase requests.

​

Manage existing limits

The page has two sections. In Workspace, at the top, you find the Usage limits, Balance alerts, and Requests tabs. In Usage limits by scope, below it, you find tabs for All, Projects, Users, Groups, and Access tokens. The Requests and Access tokens tabs appear only to owners and admins, and the Groups and Access tokens tabs need a Business or Enterprise plan. When a limit is triggered or approaching, a Requires attention card at the top of the page lists what needs review: Usage limits with a Usage blocked or Threshold reached badge, Balance alerts with a Threshold reached badge, and Approaching limits. Select a row’s Review action to open the matching tab with its status filter applied. Open the menu at the end of a limit’s row to:

• Edit the limit. You can change the amount in the Limit field and the Behavior settings. The scope, credit type, and period are fixed after creation, so the dialog shows them locked. To change those, create a new limit.
• View usage details on limits for a specific project or member with usage in the current period. It opens Usage details filtered to that project or member, so you can see the usage behind the limit.
• Use the Enabled switch to disable the limit without deleting it. Its status shows as Disabled.
• Delete it.

A specific project or member that is covered by a default limit shows that limit as an inherited row. Editing an inherited row does not change the default: saving your changes creates an override for that project or member. To disable or delete an inherited limit, manage the default itself. To find a specific limit, use the search box on the Usage limits by scope tabs. Search matches who or what a limit applies to: a member’s name or email, a project’s name, a group’s name or one of its members, or an access token’s name. To narrow the list by a limit’s own settings instead, open the Filters menu. For usage limits, it offers:

• Status: Approaching (usage reached the warning level), Triggered (usage reached the threshold), or Disabled. The tabs in the Usage limits by scope section also offer Active (enabled, with usage still below the warning level).
• Period: Monthly or Daily
• Credit type: General, Build, Run, Cloud, AI, or Connectors

The Balance alerts tab filters by status only, and its triggered status is called Threshold reached. Specific limits show their current usage against the threshold, and default rows show the threshold only. A triggered limit that blocks usage shows a Blocking badge in place of Triggered.

​

Limitations

Keep these constraints in mind when planning your limits:

• A workspace can have up to 500 limits.
• Limits apply within one workspace. To control spend across several workspaces, create limits in each one.
• Usage is recorded before limits are evaluated, so usage can slightly exceed a hard limit before the block takes effect.
• Access-token limits apply per token. The dialog offers no default that covers all access tokens at once.

​

FAQ