ShipGauge

Budgets & alerts

Soft alerts and hard blocks on daily or monthly spend

Budgets stop runaway LLM spend. Soft alerts notify; hard budgets block.

When to use

  • Cap a noisy feature_id in production
  • Alert finance/eng before month-end overage
  • Pair with CI gates so regressions don’t ship and don’t burn cash if they do

Configure

  1. Open Project → Budgets / Alerts (or alert settings).
  2. Add a rule:
    • Scope: global, feature, model, or customer
    • Period: daily or monthly
    • Limit (USD)
    • Soft threshold (default ~80%)
    • Soft action: notify
    • Hard action: block (when enabled)
  3. Enable Slack / email / webhook channels as needed (plan-gated).

Runtime behavior

  • Soft: ShipGauge records alerts; notifies configured channels.
  • Hard: ingest/SDK paths signal block (typically HTTP 429). Handle this in configureBudget({ onBlocked }) on Node.

Notifications

Pro/Team unlock Slack and richer alerting. Hobby is limited — see Limits & pricing.

Verify

  • Drive synthetic spend under a low test limit
  • Confirm soft alert fires, then hard block returns 429
  • Check Alerts history in the project

Next