Pulse: website, API and uptime monitoring
Know your site is slowing down before your customers do.
Pulse checks your websites, APIs and internal services around the clock and learns each one's normal response time. When one starts to slow down or fail, it tells you, without you guessing a threshold for every endpoint.
Pulse runs its checks from your own servers, so it can watch what public uptime checkers cannot reach: an internal service, a segmented network or a site behind a VPN.
The problem
Fixed thresholds miss the slow slide.
Most uptime monitoring asks you to pick a number, such as "alert if it takes more than a second", for every endpoint. Set it too low and you get woken for nothing. Set it too high and you hear about the problem from your customers. And every time your traffic changes, the number is wrong again.
Pulse learns what normal looks like for each endpoint, including its daily and weekly rhythm, and raises an alert when that endpoint stops behaving like itself.
How it works
Check it. Learn its rhythm. Flag the change.
Step one
It checks on your schedule
Pulse checks each target on a schedule you choose: a web page, an API call or a TCP service. The checks run from your own hardware.
Step two
It learns each target's normal
It learns each target's usual response time and how it moves through the day and the week. A batch job that is always slow at 2 a.m. is normal then, and a problem at 2 p.m. Pulse learns the difference without being told.
Step three
It tells you what changed
When a target stops behaving like itself, Pulse tells you which endpoint, which way it moved and what it normally does. You get a short list of alerts worth acting on, not a wall of red.
What you get
An alert that tells you where to look.
A sample alert, so you can see the shape of what Pulse reports.
Departure from normal
Investigating- Target
- shop.example.com.au/api/checkout
- Probe
- on-prem probe "syd-edge-1"
- Raised
- 2026-09-21 14:06:31 AEST
- Availability
- Responding still returning 200
- Status
- Departed from normal
What moved
| Signal | Learned normal | Now |
|---|---|---|
| Response time | 180-240 ms | 735 ms |
| Time to first byte | 60-90 ms | 610 ms |
| Failed probes per hour | 0-1 | 0 |
In words
This endpoint is still up and still returning success, and it is not behaving the way it normally behaves at this hour on a Monday. The delay is arriving before the first byte, which points upstream of the response body.
Sample alert. The values are examples.
Nothing to tune
No thresholds, no per-endpoint rules, no maintenance-window scripting. Adding a target is choosing a URL and an interval.
Yours to run
Probes run on your hardware, inside your network, including in places a hosted checker could never reach. Results stay on the box.
Alerts where you already are
Email, webhook and chat delivery, from the same console as the rest of the range.
Pricing
One flat price, on your own hardware.
Flat and never metered, with a 3-day grace period after expiry before the instance goes read-only.
- 50 monitors
- 1-minute check interval
- 90-day retention
- 10 activated instances
- Annual is AUD $1,990
- Pulse, Shield, Discern, Vitals
- 250 monitors
- One console, one subscription
- On-Prem: AUD $60,000 per year
- Every product, unlimited caps
- Offline licence activation
- No call-home for verification
- Large fleets: Contact us
Prices, meters and grace period are read from one price file. All amounts include 10% GST. Subscriptions are arranged with our team directly, on your own hardware, with a guided setup.
Tell us what you need to watch.
Tell us which sites, endpoints and internal services matter, and we will show you how Pulse learns each one's rhythm and where its probes run in your network.