Plan limits and fair use
On ProbeRun Cloud your team is on a plan. A plan sets how many Projects you can have and a monthly fair-use line for Runs. Add-ons, such as an extra Project or ten more monitored Scenarios, raise or extend your plan and are set by ProbeRun, not from the dashboard. The numbers for each plan are on the pricing page; this article explains how they behave. A self-hosted server has no plan limits at all.
See where you stand
An Admin sees the plan and current usage in the dashboard under Team > Plan and
usage: each limit as used against included, “Unlimited” where there is no limit, this
month’s Runs against the fair-use line, and the notices sent. A limit you are at says so in
words (“At the limit: a new Project is refused.”). The same numbers come from
GET /team/usage: the plan name, its add-ons, each limit as used and allowed (add-ons included)
(allowed: null means unlimited), this month’s counted Runs against the
fair-use line, any fair-use notices sent this month, and your support target.
When the New project form is refused, it shows the message and the fix in place and keeps what you typed.
Projects: a hard limit, refused with the fix
Creating a Project, or restoring a deleted one, when your live Projects
already equal your plan’s allowance is refused with 402 and code
plan_limit_reached. The response names the limit, how many are in use, how
many the plan allows, the plan, and what to do:
{"detail": {"code": "plan_limit_reached", "limit": "projects", "used": 2,
"allowed": 2, "plan": "...", "message": "Your plan includes 2 Projects and 2 are in use.",
"fix": "Delete a Project you no longer need, or add one.",
"upgrade_url": "mailto:billing@proberun.com?subject=Plan%20change",
"support_url": "mailto:support@proberun.com"}}
- Deleted Projects do not count, so deleting one frees a place.
- Nothing is created or restored when the request is refused.
- Two creates at the same moment cannot both squeeze past the limit.
- Moving to a smaller plan never deletes or hides anything. Projects over the new allowance stay readable and keep accepting Runs; only new Projects are refused.
Your CI never creates Projects (probe push and the GitHub Action send Runs
to an existing Project), so this limit can never turn a CI run red.
Hobby: one seat, and live Runs that stop at the line
Hobby is the one plan with two hard limits. Every other plan keeps uncounted seats and the fair-use line below.
- Seats. Hobby includes one. Inviting a second person, or a second person signing in
through a group or automatic provisioning, is refused with
402 plan_limit_reached,"limit": "seats"and"upgrade_to": "team". Removing a member or revoking an outstanding invitation frees the seat. - Live Runs. Past the month’s live Runs, each live row in a
probe pushcomes back as a per-row error startingplan_limit_reached:that names the date the month resets. Replay Runs in the same push are still created, so CI that replays recordings keeps working. A Run or trigger the server would execute is refused with402before anything runs (this includes a server-side replay, since the server cannot know before running it). There is never an overage bill.
Runs on Team and above: a fair-use line that never blocks
Runs are not metered. Each plan has a monthly fair-use line, counted per team
per calendar month in UTC. Replay Runs (those with a replay determinism
outcome of matched or diverged) are not counted; repeated live Runs
(probe run --runs N) are.
Going past the line never refuses, slows, truncates or drops a Run, and the ingest response is exactly the same as under the line, so nothing in CI can notice.
What does happen:
- At 80% of the line, and again at 100%, ProbeRun records one notice (once per threshold per month) and emails your team’s Admins.
- At 100%, the ProbeRun team is emailed too, so we can talk to you about the right plan. That conversation is the only consequence.
- The count starts again at zero on the first of each month (UTC).
- If an email cannot be delivered, the notice records it and your ingest is unaffected.