An uptime check gets HTTP 200 from a login page whose submit button posts to an identity
provider that stopped answering an hour ago. A PylonMon login journey opens a real browser every few minutes,
types a test user's credentials, submits, and waits for the words that prove they are in. The moment that stops
working you are paged with the failing step and a screenshot of what the browser saw.
fill Email = probe@yourapp.example fill Password = •••••• click Sign in expect Welcome back
Steps find things by the text a person sees — the field's label or placeholder, the button's words — and
expect waits up to fifteen seconds for the page that proves the sign-in worked. SSO redirects, two-step
forms and "remember me" flows are just more lines; css:#id is there for the awkward ones.
Fill values are encrypted at rest with a key that never leaves the server, are never returned by the API or shown in the portal again, and are opened only for the browser that runs the journey. Use a dedicated test account with no real data behind it, and rotate its password like any other credential.
SaaS apps behind SSO, customer portals, anything with a sign-in that gates revenue or support. One journey per identity path — password, Google, SAML — so you learn which one broke. Journeys are included on every plan: one on Free, five on Pro ($9), twenty on Team ($30), a hundred on Enterprise, next to uptime, server and cron monitoring, alerting and on-call, at flat prices that never count seats.
Watching checkout too? Checkout monitoring. Step language and limits: the docs.