Plans & usage
What each plan includes, and exactly how the two run limits behave.
Plans meter runs, never people or features: every plan includes unlimited members, all trackers and notifiers, gated workflows, and the live session view. Two limits apply — how many runs may execute at once, and how many you can start per month.
The catalog
| Plan | Price | Concurrent runs | Runs / month |
|---|---|---|---|
| Free | $0 | 1 | 25 |
| Pro | $29/mo | 3 | 250 |
| Team | $99/mo | 10 | 1,000 |
How the two limits behave
They fail differently, on purpose:
- Concurrency is a queue, not an error. A run started past the
cap is created as
pendingwith a note explaining why, and starts automatically the moment a slot frees. The cap counts runs doing real work —running, waiting on mid-run answers, or holding a preview. A run parked at a gate holds nothing. - The monthly quota is a hard ceiling. It counts runs created this calendar month (UTC, resets on the 1st) across the whole organization. When it's spent, new runs are rejected with a message naming your plan and the reset date.
Watching usage
Dashboard → Settings → Billing shows your plan, live meters — runs this month, active runs, members — and the full catalog, counted by the same code that enforces the limits. The dashboard overview repeats the usage strip.
Private beta. Invited beta users aren't
charged, and upgrades are provisioned by hand — the paid buttons say
"talk to us" for now. On a self-hosted
installation there is no plan at all: limits are whatever you set with
PERACTOR_MAX_CONCURRENT_RUNS and
PERACTOR_MONTHLY_RUN_QUOTA, or unlimited.