Stay inside quotas and caps

Track counted quotas, abuse limits, fleet caps, and overage behavior.

Track counted quotas

1. Charge each commit that creates a commit to the app owner, whoever makes it.
2. Exclude the template commit from create_app and every rollback from counting.
3. Check usage and reset times with whoami.
4. Relay quota_exceeded plus its verbatim user_message to the person.
5. Merge extra databases or buckets; a second d1_databases or r2_buckets entry fails validation.

Respect abuse and runtime caps

1. Expect sign-in throttles: 5 OTP emails/hour/address, 20/hour/IP, 3 new accounts/day/IP.
2. Run every fleet under the host’s memory and CPU caps; there is no per-plan sizing.
3. Expect idle sleep after about 30 minutes on every plan; on Pro, keep-warm holds selected fleets awake up to the host cap.
4. Track requests, storage, and egress in usage with no enforced caps; never tell the person an app paused over quota.

For the person-side walkthrough, see Limits and quotas.