PathJune 2026
Why our plans are counted in browser minutes
An HTTP check and a browser journey do not cost the same, by several orders of magnitude. Putting them on one meter means overcharging for one or bleeding money on the other.
What actually costs
An HTTP check fits in a few dozen milliseconds of compute. A browser journey holds a full Chromium for thirty seconds to two minutes. The ratio between the two is not one to two: it runs into the thousands.
So we keep two separate meters: how many addresses are watched over HTTP, and how many browser minutes are spent in the month. Merging them would force a choice between overcharging HTTP-only customers and losing money on browser-heavy ones.
How to read your usage
- A ten-step journey on a decent site runs in about a minute.
- The same journey on a slow site loaded with third-party scripts can climb to two or three minutes.
- A failing journey costs less than a passing one: it stops at the step that breaks.
In practice, the two hundred monthly minutes on Pro cover five one-minute journeys running once a day, about a hundred and fifty minutes. That leaves room to tighten the cadence on the journey that really matters — usually checkout — rather than on all five at once. The dashboard shows minutes spent and warns before the cap.
Why no unlimited plan
An unlimited plan on an expensive resource is never unlimited: it is secretly capped, or funded by the customers who barely use it. We would rather show the meter. When you near the cap, you find out before we do, and you decide: tighten one journey, switch another off, or move up a plan.
What the free plan does
One browser journey a day, five addresses watched over HTTP, seven days of history, no credit card. Enough to check every morning that your checkout still goes through; not enough to watch a serious shop. That is on purpose: the free plan exists to see whether the tool speaks to you, not to replace a paid one.