Every Forge organisation has two limits: seats (number of active members) and runs per month. Understanding how these work helps you plan your usage and avoid unexpected blocks mid-month.
Seat limit
The seat limit is the maximum number of active members your organisation can have at one time. It applies to active members only — pending invitations do not count toward the seat limit until they are accepted.
If you try to invite someone and you are at the seat limit, the invite will be blocked with a clear error. You will need to either remove an existing member or upgrade your plan before the invite can go through.
Run limit
The run limit is the maximum number of runs your organisation can create in a calendar month. The counter resets to zero on the 1st of every month at midnight UTC.
The limit applies to all members of the organisation combined — it is a shared pool, not per-user. If the Marketing team and the Engineering team both use the same Forge organisation, their runs count together toward the monthly limit.
What happens when you hit a limit
When your run limit is reached, the new run form shows a clear error: Run limit reached — your plan allows N runs per month. Upgrade to continue. No partial runs are created — the submission is rejected before any AI processing starts.
Runs triggered via inbound webhooks or the public API are subject to the same limit. If a webhook fires when the limit is already reached, it returns a 429 Too Many Requests response.
Tracking your usage
Go to Settings → Billing & Usage → Billing. The Usage section shows two progress bars: one for seats used vs. the seat limit, and one for runs used this month vs. the monthly limit. The bars turn amber at 70% and red at 90% to give you early warning before you hit the limit.
Runs that count toward the limit
Every submitted run counts, including runs that fail, runs that are cancelled, and runs triggered automatically by webhooks or run chains. Re-runs of completed runs also count as new runs.