Uplance Monitor types Browser
Monitor the flow, not just the page
A real Chromium browser loads your site, clicks through the steps you gave it, and fails on the step that broke — with the step named.
Free for 10 monitors · no credit card
The problem
The homepage is up, the API returns 200, and nobody can complete checkout because a third-party script started throwing on the payment step.
Everything that watches a single URL is green. The only thing that would have caught it is something that actually tries to buy.
What the check looks at
A real browser
Chromium, running your steps — so client-side JavaScript, redirects and third-party scripts are all in scope.
The step that failed
The alert names the step that broke, rather than telling you the site is down.
How long the flow took
End-to-end duration as history, so a checkout that is getting slower is visible before it fails.
Credentials kept out of sight
Anything you have it type is encrypted with AES-256-GCM at rest and never written to logs or check history.
And the alert actually arrives
Most monitoring tools are fine until the one time the alert doesn't arrive. Uplance is built so that can't happen quietly.
- Every alert is written to an outbox before it is sent, and retried for about fifty minutes. A restart doesn't lose it.
- Once a week, a real test event is sent through every channel you've configured, and you're told which ones failed.
- If the alert pipeline is in trouble, the dashboard says so — it isn't buried in a log file.
- If the checker itself stops, the health endpoint returns 503 so an outside heartbeat can page you, and your status page says monitoring has stopped instead of showing stale green.
Common questions
- What can a flow do?
- Go to a page, fill fields, click, wait for something to appear, and assert that it did. Enough to cover a login, a search, a signup or a checkout up to the point of payment.
- Won't this create orders in production?
- Point it at the last step before payment, or at a test account your system treats as a test. A flow that stops short of paying still proves everything ahead of it works.
- How often should it run?
- Less often than an HTTP check — a browser run costs real seconds. Every few minutes is normal for a checkout; pair it with an HTTP monitor on the same site running every 30 seconds.
- Can it run against a staging site behind a password?
- Yes: add the credentials to the flow, or run it from a remote agent inside the network where staging lives.
Also monitored
Know it's down before your customers do.
10 monitors, 30 days of history, no credit card