Plan limits and fair use (Using ProbeRun)

On a hosted plan, creating or restoring a Project past the plan’s Project allowance is refused with 402 plan_limit_reached, naming the count, the allowance and the fix; deleted Projects do not count, and nothing already there is ever hidden. On Team and above, Runs are never refused for volume: a monthly fair-use line only triggers an email to your Admins at 80% and 100%, and ingest behaves exactly the same past it. Hobby is the exception: past its monthly live Runs, each live row in a push comes back as a per-row plan_limit_reached error naming the date the month resets, while replay Runs in the same push are still created, so CI that replays recordings keeps working; a server-run Run or trigger is refused with 402 before anything runs. There is never an overage bill. Hobby also counts seats: an invitation, or a sign-in, past its one seat is refused with 402 plan_limit_reached naming Team. Each team is on its own plan, set by ProbeRun; add-ons such as an extra Project are counted in the limits and listed with the plan. Admins read their plan, add-ons and usage with GET /team/usage and under Team > Plan and usage. A self-hosted server has no limits. Details in Plan limits and fair use.

Live work ProbeRun runs for you

On a hosted plan, live work that ProbeRun’s servers run for you (a Run started from the dashboard or API, a batch trigger) has two limits: how many live jobs can be queued or running at once, and how many server-run live Runs a month. Past either, the request is refused with 402 plan_limit_reached before anything runs, naming the limit (live_jobs or server_live_runs), the count, the allowance and, for the monthly count, the reset date. Runs you push from CI, replays and managed monitoring nights never count and are never refused. A finished job frees its slot at once. If ProbeRun pauses live work for maintenance, the same requests get 503 live_runs_paused with a fixed message, and pushes and replays keep working. A self-hosted server has none of these limits.

Model credits

On ProbeRun Cloud you can bring your own model key and nothing is charged for model calls. If you would rather ProbeRun run the model for you, an Admin buys prepaid credits under Team > Credits: $25 for 2,500, $100 for 10,500 or $500 for 55,000, paid through Stripe (card or wallet), and usable a few seconds after payment. A batch Run on ProbeRun’s key uses 1.5 times the model’s list price, at 100 credits a dollar, rounded up to a tenth of a credit; a Run that failed because of ProbeRun is free. Each job reserves credits before it starts and gives back what it did not use. Replays, pushed Runs and structural grading never use credits. Credits do not expire; a purchase can be refunded within 24 hours if none of its credits were used. Your first purchase is checked with 3D Secure, and the credits Runs on ProbeRun’s own runner can spend each month rise automatically with purchase history (Start $250, then $2,500, then $50,000; larger by contract). With no credits left, or past the month’s tier, a trigger is refused with 402 credits_required saying why and what to do. Auto-recharge is off unless an Admin turns it on with an explicit agreement, a threshold, a pack and a monthly cap.

The Credits page leads with what you can spend, then where it came from: granted by ProbeRun, plus bought, minus used, equals what is left (credits reserved by running jobs are shown separately). It says which spending each limit applies to: ProbeRun’s hosted judge spends the balance directly, including credits ProbeRun granted before any purchase; Runs on ProbeRun’s own runner also stay within the month’s room, which opens with the first purchase. What used them lists settled charges: hosted-judge calls per day with the model and the number of calls (a judge call is not tied to one Run), and runner jobs with their Project. Show every hold and release shows the raw ledger.

When your plan does not include a feature

On a hosted plan, a panel whose feature your plan lacks says so in one line, names the plan that includes it, and links Change plan (a mail to billing until online plan changes open) and Ask support. For example, a Team workspace refused Review queue assignment reads “Claiming and assigning Review items is not in your Team plan. It is included on Scale.” Everything else your plan includes keeps working. The API’s 402 entitlement_required body carries the same facts for scripts: reason (plan_lacks), plan, required_plan, upgrade_url and support_url. A self-hosted server shows only its one quiet sentence about the commercial edition, with no plan line; its body says reason: edition_lacks and plan: null. An operator sets the two links with PROBE_UPGRADE_URL and PROBE_SUPPORT_URL.