Handler Capacity

Capacity is how much work a Handler can take on. It accounts for the underlying resources used to do that work.

Standard allocates capacity to each Handler individually. Enterprise provides reserved capacity and one capacity pool shared across Handlers. You can buy extra Standard capacity in Full-time Handler multiples; see Additional usage explained for how purchases and rollover work.

---

What Capacity Measures

Handler capacity is a combined measurement of all the work your Handler does — one figure covering everything it takes on, rather than a row of separate meters for you to reconcile.

That matters because a Handler’s work is genuinely varied. Reading a messy email thread, calling out to your order system, running a custom tool, keeping its own notes — these are different kinds of work with different underlying costs, and they don’t arrive in fixed proportions. Combining them into one measurement is what lets an allocation be about how much work a Handler does, rather than about which shape that work happened to take this month.

Plenty of things feed into that figure, and how much each contributes is weighted on our side. We don’t publish the exact weights. They change as models and infrastructure change, so any table we published would be out of date within the month — and it would invite tuning your operations for the table rather than for the work, which is the opposite of the point.

---

What Contributes to It

Some examples of what a Handler’s capacity accounts for:

• Model use — not every model uses the same capacity, and Handle manages that choice for you, weighing speed, cost and intelligence against the situation at hand. A step that needs deep reasoning and a step that just needs a field pulled out of a document don’t draw the same amount.
• Integration use — the calls a Handler makes out to external services on your behalf. A small amount each, but they count.
• VPN use — where an enterprise Handler reaches systems on your own network over a VPN, the traffic it routes through it.
• Code-tool use — the compute a Handler spends running the custom tools written for your operations.
• Internal services — the platform services a Handler leans on to do its job, such as the SQLite database it keeps its own working data in.
• File storage — the documents, attachments and exports that pass through a Handler and the ones it keeps.

That isn’t the complete list, and it isn’t fixed. If you want to know how a particular workload is likely to land, your account team can look at it with you rather than have you work it out from a table.

---

Standard Capacity

Standard capacity belongs to one Handler and cannot be pooled with another Handler’s capacity. Work is subject to available capacity and system load.

• Choose Full-time or Full-time 4X. Full-time 4X gives one Handler four times Full-time capacity, not four separate Handlers.
• Each Handler has its own included capacity. It is allocated to that Handler, not shared across the account.
• Buy additional usage in ½×, 1× or 2× Full-time capacity amounts. Purchased additional capacity is separate from your base plan, and unused additional capacity rolls over between months.
• Annual billing saves 10% on the Standard plan. The annual discount does not apply to additional usage.

Standard does not provide guaranteed reserved capacity. See current pricing for capacity levels and additional-usage prices.

---

Capacity Pooling

Capacity pooling is an Enterprise capability. All Handlers in the pool draw from one shared capacity, so the account is sized as a whole rather than Handler by Handler.

Enterprise combines:

• Reserved capacity for your Handler work.
• Committed capacity for a monthly base load.
• Flexible capacity that can be drawn down across the billing period.
• Locked-in capacity rates with a twelve-month commitment.

Arranging Pooling

Pooled capacity is set out in your enterprise agreement. Your account team works with you on:

• Which Handlers are in the pool
• The monthly committed base and flexible capacity pool
• Reserved capacity and the agreed capacity rates

Talk to us if you are running multiple Handlers and want capacity sized across the account rather than per Handler.

---

The Two Side by Side

Plan	Capacity allocation	Availability
Standard	Per Handler, with no pooling	Subject to available capacity and system load
Enterprise	One pool shared across Handlers	Reserved capacity with agreed committed rates

See also: What LLMs Can I Use With Handle? for how Handle picks a model for each step of the work, and Inspecting a Task for seeing what a Handler actually did with the work you gave it.