Lovable: Usage Limits and Alerts for Credit Spending

LovableOct 7, 2026View original changelog

Lovable introduced Usage limits & alerts, a workspace setting that lets owners and admins cap credit spending by workspace, project, member, group or access token. Each rule can send an email or in-app notification, block usage, or both, and separate low-balance alerts warn when the workspace balance runs low. The feature is available on all paid plans, with group and access-token scopes reserved for Business and Enterprise.

Key Takeaways

Credit spending can now be capped per workspace, project, member, group or access token, so one heavy user or runaway project cannot drain a shared balance.
Each rule can notify, block, or both, with an early warning once usage reaches 80% of the threshold.
Separate low-balance alerts fire on a credit amount or a percentage of granted credits, and never block usage.
Credit types are layered (General, Build, Run, Cloud, AI, Connectors), so a limit can target building costs or deployed-app costs independently.
Blocked members can request a higher allowance, and admins approve or deny it for the rest of the period or indefinitely.
Group and access-token scopes require Business or Enterprise, and limits are guardrails rather than exact cutoffs because usage is recorded before it is checked.

Spending guardrails for shared workspaces

Lovable added Usage limits & alerts under Workspace settings, giving workspace owners and admins a way to control how credits are spent in a shared workspace. Each rule combines four choices: a threshold, a scope, a credit type and an action. Owners and admins can create, edit and delete rules, while editors can view the limits that apply to them and their projects without changing anything.

The feature is available on all paid plans. Group and access-token scopes require a Business or Enterprise plan.

Two kinds of rules

A usage limit triggers when credits spent in a period reach a threshold, and can send an email, send an in-app notification, block usage, or do all three. A low-balance alert triggers when the workspace balance drops below a threshold, expressed either as a credit amount or as a percentage of credits granted, and can only notify. Alerts never block usage. Enterprise workspaces start with email alerts at 25% and 10% of granted credits.

Scopes and credit types

Limits can apply to the whole workspace, to all projects or a single project, to all members or a single member, to each member of a group, or to requests made with a specific access token. For projects and members, a default gives each one its own allowance rather than a shared pool, and a specific limit overrides a matching default when the credit type and period match.

Credit types are layered. General covers all usage and contains Build (building, chat, image and video generation) and Run (deployed app usage). Run in turn contains Cloud, AI and Connectors. A broader type covers everything beneath it. Member and group limits only count Build credits, since Run usage belongs to the project. Limits reset on a monthly or daily period at 00:00 UTC.

Alerts, blocks and increase requests

Blocking limits enter an approaching state at 80% of the threshold, with an early warning if notifications are on. Blocking Build stops building and editing, while blocking General stops both building and running. Blocking Cloud, AI or Connectors pauses those features in covered projects, which can affect published apps and their end users. A block lasts until the period resets or the limit is raised, disabled or deleted. Adding credits or upgrading does not lift it, because the limit counts credits already spent.

When a member hits a blocking limit that supports requests, they can ask for a higher amount with an optional reason. Admins approve or deny requests from a Requests tab, either indefinitely or until the end of the period.

Limitations

A workspace can hold up to 500 limits. Usage is recorded before limits are checked, so spending can slightly exceed a threshold. Limits control when usage is allowed and when people are notified, and do not change the plan, credit grants or billing.