feat(webapp): billing limits — pause, reject, recovery, and settings UI

[kathiekiwi]

Summary

Adds Billing Limits to the webapp.

Customers can set a monthly spend cap. When usage crosses the limit, billable environments enter a grace period. If the limit is not resolved before grace expires, new triggers are rejected until the organization increases or removes the limit.

The webapp consumes billing-limit state from the billing platform and enforces it across environments, queues, and trigger creation.

Depends on the matching cloud billing PR.

User-facing changes

Billing Limits settings

• New /settings/billing-limits page replaces the standalone billing-alerts page.

• Configure:

  • plan limit
  • custom limit
  • no limit

• Configure billing alerts and notification emails.

• Resolve active billing limits by increasing or removing the limit.

Org-wide banners

Adds banners for:

• grace period
• rejected state
• billing limits not configured
• upgrade prompts

Usage page

Shows the configured billing limit on the spend chart.

Enforcement

• Billable environments are paused when an org enters grace.

• New triggers are rejected once grace expires.

• Billing-limit pauses cannot be manually resumed.

• New environments created during grace/rejected inherit the correct paused state.

• Recovery supports:

  • resuming queued runs
  • cancelling queued runs and starting fresh
  • optional cancellation of in-progress runs when a limit is reached

Infrastructure

• Adds billing-limit workers and reconciliation.
• Adds admin endpoints used by the billing platform.
• Adds BILLING_LIMIT as an environment pause source.

Test plan

• Configure limits, alerts, and emails.
• Verify grace and rejected flows.
• Verify trigger rejection after grace expiry.
• Verify recovery flows (queue and new_only).
• Verify new environments created during grace start paused.
• Verify billing-limit pauses cannot be manually resumed.
• Verify billing limit marker on the usage chart.

Notes

• isConfigured: false means no billing limit has been configured yet.
• mode: "none" means the customer explicitly opted out.
• Grace pauses execution but still accepts triggers.
• Rejected blocks new triggers.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 19f5d47

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• ✅ Review completed - (🔄 Check again to review again)

Walkthrough

This PR implements a billing limits feature that lets organizations configure a monthly compute spend cap. When the cap is reached, a billing platform webhook triggers a grace period during which billable environments are paused; new task triggers are rejected once the grace period ends. A recovery flow lets users increase or remove the limit and choose to resume queued runs or accept cancellation. A Redis-backed worker periodically reconciles environment pause state against billing platform data. The feature adds a new /settings/billing-limits settings page that consolidates limit configuration, alert thresholds, and the recovery panel, replacing the old /settings/billing-alerts route (which now redirects). The unified OrgBanner component replaces the prior UpgradePrompt and EnvironmentBanner components with a selector-driven switch over all banner states. Environment pause-source tracking now distinguishes billing-limit-enforced pauses from manual pauses, gating pause/resume operations accordingly.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 21.53% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title clearly and specifically summarizes the main changes: implementing billing limits with pause, reject, recovery, and settings UI for the webapp.
Description check	✅ Passed	The PR description is comprehensive and well-structured, covering summary, user-facing changes, enforcement, infrastructure, test plan, and implementation notes.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/billing-limits

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

@trigger.dev/build

npm i https://pkg.pr.new/@trigger.dev/build@cb4df39

trigger.dev

npm i https://pkg.pr.new/trigger.dev@cb4df39

@trigger.dev/core

npm i https://pkg.pr.new/@trigger.dev/core@cb4df39

@trigger.dev/python

npm i https://pkg.pr.new/@trigger.dev/python@cb4df39

@trigger.dev/react-hooks

npm i https://pkg.pr.new/@trigger.dev/react-hooks@cb4df39

@trigger.dev/redis-worker

npm i https://pkg.pr.new/@trigger.dev/redis-worker@cb4df39

@trigger.dev/rsc

npm i https://pkg.pr.new/@trigger.dev/rsc@cb4df39

@trigger.dev/schema-to-json

npm i https://pkg.pr.new/@trigger.dev/schema-to-json@cb4df39

@trigger.dev/sdk

npm i https://pkg.pr.new/@trigger.dev/sdk@cb4df39

commit: cb4df39