About Pulse Protect the journeys your business relies on
Why we built Nekai Pulse.
Pulse keeps watch over the pages and customer journeys that bring your business enquiries, bookings and sales. If something important stops working, you get a clear warning so the right person can act.
[ the business risk ]
A website can look open
while quietly losing business.
A customer may be able to visit your website but still be unable to send an enquiry, make a booking or complete a purchase. Those failures are easy to miss and can cost revenue long before anyone reports them.
Pulse checks the important steps for you. It stays quiet when everything works and gives your team or agency a useful starting point when it does not.

Online versus working
Review check results to see which parts of your website need attention.
What it watches Only as deep as useful
The essentials first.
The experience where it matters.
01
Availability
Confirms that important pages answer successfully and records response behaviour.
02
SSL and domain
Shows your certificate and domain expiry dates at every scan and flags either one 30 days before it runs out.
03
Content and interfaces
Checks that expected content and JavaScript-powered components actually appear.
04
Customer journeys
Uses a real browser to follow forms, bookings, baskets and checkout routes step by step.
[ browser journeys ]
The check that behaves
like a customer.
A browser journey is a short walk through one of the routes that earns your business money: the enquiry form, the booking widget, the product page, the basket, the checkout. Pulse opens a real browser, takes the steps a customer would take, and confirms that each one still works.
Each journey can run on desktop, Android and iPhone-sized browsers, because a booking form can work perfectly on a laptop and fail completely on a phone.
Pulse looks at your website, works out which journeys are worth protecting and builds them for you. There is nothing to script, and nothing to keep up to date: when you change your website on purpose, the journey adjusts to match.
How a journey behaves Reliable by design
Repeatable checks.
Quiet maintenance.
01
A real browser
Journeys run in a genuine browser on desktop, Android and iPhone screen sizes, so a step that only breaks on one of them is still caught.
02
Built for you
Pulse reviews your website, decides which routes matter and builds the journeys around them. Onboarding stays short, whether you have one website or fifty.
03
Fixed steps, repeatable results
The journey itself is a fixed sequence, not an improvisation. The same steps happen in the same order on every run, so a pass or a failure means the same thing each time.
04
Self-healing checks
When your website legitimately changes, Pulse updates its own steps instead of raising an alarm. You do not maintain the checks, and a redesign does not become a week of false alerts.
05
Your analytics stay clean
Journeys block recognised tracking and advertising calls and identify themselves as synthetic traffic, so monitoring does not inflate your reporting.
06
Confirmed before you hear
A failure has to repeat three times, and the recorded evidence has to agree, before anyone is contacted. You receive a screenshot of the failing step and a plain explanation by email, and it appears in your summary report.
What you receive A useful place to begin
A clear result.
Evidence when it fails.
Pulse keeps the normal view quiet. When a check fails, it records the affected step and the available diagnostic evidence, then checks again so recovery is visible too.
Review the check history and share the available evidence with the person responsible for putting things right.

Monitoring results
A calm summary for owners, agencies and the people resolving the fault.
Boundaries Trust includes being explicit
What Pulse is.
And what it is not.
| Pulse does | Pulse does not |
|---|---|
| Monitor authorised websites on a regular schedule | Guarantee that a website will never fail |
| Record failures and make recovery visible | Replace the developer or agency responsible for repairs |
| Explain results in practical, business-facing language | Create noise simply to look busy |
Built around a real website problem
Pulse grew from maintaining a small business website whose booking journey failed while the server stayed online. That experience shaped a service focused on practical checks and evidence, with browser setup handled for the business.
- Scheduled checks, not a guarantee of uninterrupted availability.
- Evidence and recovery checks, not automatic website repair.
- Clear boundaries between current browser steps and planned transaction verification.
One website. Two quiet checks a day.
Begin with the signal
that should always be there.
The free level runs one basic check every 12 hours, covering HTTP 200 responses, SSL and domain expiry.