Skip to main content

​
Limits & quotas reference

Starfire limits are configuration-driven. The effective value can depend on the deployment, plan, organization policy, user override, workload, model, and current Alpha rollout. Because those values can change independently from the documentation, this page defines the limit categories and precedence model instead of hardcoding numbers that can become stale.

​
Effective limit precedence

A narrower limit can reduce access even when a plan would otherwise allow more.

​
Limit categories

​
Find the current value

Use the product surface closest to the workload:
  • account or billing UI for personal plan allowances
  • organization administration for team policy
  • Developer Portal for API quotas
  • FORGE UI for build-related limits
  • Control Center for platform/operator configuration

​
Soft vs hard limits

A soft limit can warn or throttle without permanently blocking the account. A hard limit rejects new work after the threshold is reached until the limit resets or an authorized configuration change occurs. When a request is rejected because of a limit:
  1. Identify the resource/workload.
  2. Confirm the active personal or organization context.
  3. Check the applicable plan entitlement.
  4. Check organization policy.
  5. Check explicit user/application overrides.
  6. Check whether a hard credit ceiling or concurrency limit is active.
  7. Retry only if the limit is temporary or resettable.
A provider can also impose its own upstream limit. Starfire can surface or absorb some provider throttling, but provider limits and Starfire product quotas are different layers.