Set alerts and operating limits for all four categories. Alerts never authorize charges, and customer limits cannot expand purchased allowances or override service safety controls.
⇄Network transfer
Set transfer limits and alerts for outbound usage, including exports and large responses.
Measured transfer · included allowance at launch
⌘Compute & operations
Set workload limits and alerts for database operations and request processing.
Measured work · included allowance at launch
▤Retained data
Get alerts as your database or evidence storage fills, and set retention-related usage limits.
Retained storage · measured over time
⟐Request pressure
Set rate and concurrency alerts and stricter limits; service safety controls still apply.
Protective limits · independent of billing
No surprise overage charges.
Paid overages are off by default. Billing admins can review published rates, approve excess usage, and set a spending cap. Without approval, new work beyond included limits is throttled or declined without extra charges. Approved excess use is itemized by resource. Alerts and operating limits never grant billing permission.