On-demand tests, run when you ask

Not a paywall — a design decision, and the API enforces it. Point a schedule at a test suite and you get a refusal, not an upgrade prompt.

The reason is that all four depend on things you do not control. A broken-link check run hourly turns somebody else’s blog post moving into your 3am incident. An exposure scan run hourly is indistinguishable from an attack against your own site. A performance test run hourly burns an API quota to tell you the same thing.

Run them when you ship, when you are investigating, or on the schedule your own CI already has. Every run is kept, so the history is there when you want to compare.

The two halves of Pulse behave differently on purpose. A monitor is cheap, fast, repeatable and safe to run against production forever. A test is slow, deliberate, and sometimes noisy enough that you want to choose the moment.

A few checks have a foot in each camp, and where that happens they are split rather than compromised. Security headers are watched hourly by a monitor; path probing is a manual test. The distinction is the point.

Everything in monitoring is free, on unlimited websites, on every plan. The four test suites on this page are the Pro feature.

One thing that does not change with your plan: test results you have already produced stay visible. Downgrading stops new runs; it does not take away the history you built.