Quotas
A hosted Stack has two limits on simultaneous work and one limit on registered Projects. The two work limits are ceilings on settings you control. The watched-Projects cap is enforced when you register a Project.
Run Cap
The Run Cap is the plan ceiling on General Concurrency, the number of general admission slots your Stack may fill. Its default is 1 on a hosted Stack.
You can choose a lower General Concurrency setting. The admission gate uses the lower of your setting and the Run Cap, called Effective Concurrency. Targeted and fleet Dispatch use these slots, and an Interactive Turn tries a free general slot before using reserved capacity.
Reserve Cap
The Reserve Cap is the plan ceiling on the Interactive Reserve, extra headroom beyond General Concurrency that only an Interactive Turn may use. Its default is 1 on a hosted Stack.
The admission gate uses the lower of your Interactive Reserve setting and the Reserve Cap, called the Effective Reserve. Setting the reserve to 0 removes the extra headroom, so an Interactive Turn waits whenever all general slots are occupied.
What Happens When a Concurrency Cap Changes
Changing a Run Cap or Reserve Cap doesn't interrupt work already in flight. The new ceiling applies to later admission decisions.
A plan downgrade may put a saved setting above its cap. Zozo preserves the setting and applies the lower effective value. If the cap rises again, the admission gate can return to the value you chose without requiring you to re-enter it.
Watched-Projects Cap
The watched-Projects cap limits how many GitHub repositories you can register for your Stack's Dispatcher to watch. Its default is 3 on a hosted Stack.
The Control Plane enforces this quota when a Project is registered. Re-registering a Project that's already watched doesn't increase the count. When the count is full, registering a new Project fails until you stop watching another one.
Usage Reporting Doesn't Gate Admission
These quotas are static plan limits, not spending caps. Zozo reports token and cost usage for visibility, but that usage doesn't decide whether new work may start. Concurrency admission compares effective capacity with current work, and Project registration compares the watched count with its cap.
Related
- Understand Your Quotas: see what happens when work or a Project reaches each limit.
- Work Model: follow work through admission and Dispatch.
- How Dispatch Decides: see which work receives the next available slot.
- Two Surfaces: compare enforcement on your Stack with enforcement by the Control Plane.