The alert, before opening
Alert screenshot: failed step, time, store. You get it before the site opens.
Ping
Pathly watches the path. Ping if it’s up. One HTTP request from Europe: status, time, text, headers, JSON. No Chrome. /scan is a one-off. Ping is the watch that stays on.

One URL, one cadence, one latency cap. Pathly sends the request and checks the reply: status, time, body, headers. If it breaks, the alert goes out. No agent, no browser.

Pasting a URL in /scan is a one-minute diagnosis. Creating a Ping is that same URL checked every few minutes, with history and alerts. One opens the door. The other stays.

Ping says whether the server answers. Flow says whether a visitor can still click. Chain says whether the calls behind (login, then API) hold. All three live in the same list.

| Question | Audit /scan | Ping | Flow |
|---|---|---|---|
| Does the server answer? | once | continuously | plus the click |
| Alert if it breaks tomorrow? | no | yes | yes, with screenshot |
| Credit card? | no | not on Solo | not on Solo |



Product proof
Alert screenshot: failed step, time, store. You get it before the site opens.
First page of the monthly PDF report — attach it to the maintenance invoice (Business).
No admin access, no plugin, no FTP. You record the checkout as a visitor. Data in the European Union. One measurement origin.
No card. One URL. First green in under a minute.
Create a Ping, no card