Plan limits
Entitlements that are not wallet debits.
Plan limits cap how you use the product. They do not add separate dollar lines on the wallet.
| Plan | Models | Projects | Seats | Viewers | Recurring Factory schedules | Parallel agents | Req/min | Sessions/day | Invitations |
|---|---|---|---|---|---|---|---|---|---|
| Hobby | AUTO, AUTO-MAX | 3 | 1 | 0 | 0 | 10 | 60 | 20 | No |
| Pro | AUTO, AUTO-MAX | 200 | 100 max | 250 | 3 | 100 | 2000 | Unlimited | Yes |
| Enterprise | AUTO, AUTO-MAX | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | 10000 | Unlimited | Yes |
Enforcement of these limits is separate from the billing usage ledger.
Viewers are read-only team members. They do not consume a paid seat, which is why the viewer limit is tracked separately from the seat limit.
What happens at a limit
Each limit is enforced where the work starts, and the response differs:
| Limit | When you reach it |
|---|---|
| Projects | Creating a project over the plan's count fails with 429 and code project_limit_reached. Delete or archive a project, or change plan. |
| Seats | Adding a team member over the seat cap fails with 403 and code team_seat_limit_exceeded. |
| Viewers | Adding a read-only viewer over the viewer cap fails with 403 and code team_viewer_limit_exceeded. |
| Recurring Factory schedules | Enabling one more schedule than the plan allows fails with a 409 conflict and code workflow_runtime_conflict; the message names the slots allowed and in use. |
| Parallel agents | An execution over the pool waits in a queue until a slot frees. It is never rejected for capacity, and starting a Run does not consult the pool. |
Next steps
- Billing - see how grants fund usage
- Plans - compare plan allowances and prices
- Usage lifecycle - follow a metered charge