Browser monitoring
Browser monitoringthat does what your customers do.
A page can answer 200 and still be broken. A browser flow opens your site in a real Chromium and signs in, adds to the basket or submits the form, as often as every 5 minutes.
The flow
Built from plain steps, not scripts
Open a page, click, type, wait for some text. You add steps from a list and fill in the blanks. There is no test code to write or keep working.
Passwords typed by a step are stored encrypted and shown as dots once saved.
- Open a page
- Click a button or a link
- Type into a field
- Wait until text appears
- Up to 20 steps in a flow
- The failing step is named
- A picture of the page is kept
- The time each step took
- 30 days of run history
- Run it now from the console
When it fails
The step, the reason and a picture
A flow stops at the first step that fails. You see which step it was, why it failed, and a picture of the page at that moment.
That is usually enough to know what broke before you have opened a laptop.
The alert
Told when the journey breaks
Browser flows alert the same way as every other node: Slack, Discord, a webhook, PagerDuty, a text, an email or your own API.
Standard includes 3 browser flows and Plus includes 6, alongside your API, port, DNS and heartbeat nodes.
- As often as every 5 minutes
- 3 flows on Standard, 6 on Plus
- Alert groups by day and time
- Shown on your status page if you choose
- Works for sign-in, checkout and forms
Questions
Do I need to write Playwright or Selenium scripts?
No. You build a flow from plain steps in the console: open a page, click, type, wait for text.
How often does a browser flow run?
As often as every 5 minutes. You can also choose 10 or 15 minutes, or longer.
Which plans include browser flows?
Standard, at £100 a month, includes 3. Plus, at £250 a month, includes 6. Basic has none.
What do I see when a flow fails?
The step that failed, the reason, and a picture of the page at that moment.
Also in every account