Slot quotas & usage
PathWatch doesn’t bill by per-check execution. Each plan grants slot quotas for each monitor variant; you can have as many monitors as you have slots, and each one runs as often as the variant’s minimum interval allows.
Variants
Each uptime, Lite browser, and Flow browser monitor maps to a
variant — standard, fast, or real-time. The variant
determines:
- The minimum check interval (5 min standard, 1 min fast, 30 s real-time for uptime; longer floors for browser variants).
- The slot pool the monitor draws from.
| Variant | Min interval (uptime) | Min interval (Lite) | Min interval (Flow) |
|---|---|---|---|
| Standard | 5 min | 5 min | 15 min |
| Fast | 1 min | 1 min | 5 min |
| Real-time | 30 s | — | 1 min |
Included slots per plan
| Variant | Free | Starter | Pro | Business |
|---|---|---|---|---|
| Standard uptime | 30 | 50 | 100 | 200 |
| Fast uptime | — | 25 | 50 | 100 |
| Real-time uptime | — | — | 10 | 50 |
| Lite browser (Standard) | — | — | 2 | 5 |
| Lite browser (Fast) | — | — | — | 2 |
| Flow (Standard) | — | — | 1 | 2 |
| Flow (Fast) | — | — | — | 1 |
| Self-hosted browser | — | 1 | 3 | 10 |
Each slot type is independent. Maxing out Standard slots doesn’t prevent you from creating Fast monitors.
Execution targets
The execution target count is a separate metric: it sums the total number of (monitor × region or runner) pairs you have configured. A monitor checked from five regions = five execution targets.
Plans publish an execution-target ceiling on the landing-page pricing. The slot quotas above are the per-variant decomposition that drives the limit.
Usage breakdown
Entitlements → Usage shows three sections:
- Summary — current count for every quota (monitors, runners, status pages, team members, execution targets).
- Variant breakdown — per-variant
used / included / totalwith add-on quantities listed separately. This is where you confirm whether you’re hitting the slot ceiling on a specific variant. - Per-region distribution — how many of your monitors run from each region. Useful for sanity-checking that you’re actually covering the regions you think you are.
Add-ons
Buy more slots with the corresponding +25 or +1 add-ons from Add-ons. Each purchase stacks on top of the included quota:
- Pro (50 Fast slots) + one +25 Fast add-on = 75 Fast slots.
- Plan rollovers respect the same arithmetic.
What happens when you hit a quota
- Creating a new monitor in a variant with zero free slots
fails with
quota_exceeded. The WebUI directs you to either buy the matching add-on or upgrade your plan. - Plan downgrade that leaves you over-quota suspends the excess monitors (oldest-created first stays active; newest get suspended). They don’t get deleted — bring usage under the cap and they auto-reactivate.
Tips
- The cheapest path to “more monitors” is usually a plan upgrade, not stacking add-ons. The break-even on Pro vs. Starter + add-ons is about three +25 packs.
- Use Standard for almost everything. Real-time is for the five or ten monitors that drive your status page; everything else is fine at Standard cadence.
- The execution-target ceiling, not the slot quota, is usually the first thing customers hit. Three regions per monitor × 200 monitors = 600 execution targets, which is over the Business default — buy +25 execution target packs or pare the region list per monitor.