Zagru PulseSynthetic monitoring and visual regression
Your app's heartbeat. Every day, every screen.
On a schedule, Pulse opens your web application in a real Chromium browser, visits every screen, runs key business journeys, compares each screen with an approved baseline — and keeps every result.
Early access — we are onboarding a small number of design partners.
- screens found on its first full sweep of Zagru One
- 500
- navigation destinations covered
- 140
- deterministic checks
- 12
Illustrative interface
One number. Every screen behind it.
A 0–100 health score for the manager; the failing screen, the step and the diff for the engineer.
Illustration: Pulse's heartbeat line and health score, a matrix of screens that turn green as they pass, one screen that fails, and a slider comparing its baseline with the current capture.
What it does
It answers three questions, every morning.
- 01
It sees what users see
A real browser signs in, crawls the navigation, opens lists, details and tabs, and captures every screen.
- 02
Journeys, not just pages
Key business journeys run end to end — for example, new shipment, assign a carrier, dispatch, proof of delivery — and Pulse knows which step broke, and since when.
- 03
Twelve deterministic checks
Console errors, failed requests, error boundaries, raw translation keys, overflow, basic accessibility, performance thresholds and a masked pixel diff.
- 04
Issues, not noise
Failures with the same signature group into one issue that opens after two failing runs and resolves itself after three passes.
- 05
The right alert, at the right time
E-mail, Slack, Telegram or webhook; a daily digest; quiet hours.
How it works
Schedule. Visit. Check. Score.
Every check is deterministic — cheap to run, and the same answer every time.
Schedule
Probes every few minutes, journeys a few times a day, a full sweep every night.
Open and sign in
A runner opens real Chromium and signs in the way a user would.
Discover and visit
Navigation is crawled; every screen is visited and every journey run.
Check and compare
Twelve checks per screen, and a masked pixel diff against the approved baseline.
Score and alert
Results are stored, grouped into issues, scored 0–100 and sent where your team looks.
Illustrative interface
The morning view.
Health per application and environment, and the issues behind any drop — with their state.
In depth
What "healthy" is made of.
Checks
- HTTP and render readiness
- Error boundaries
- Console errors and failed requests
- Raw or wrong-language translation keys
- Layout overflow and overlap
- Basic accessibility
- Performance timing: warn at 3 s, fail at 10 s
- Visual diff with masking, 0.5% threshold
Health score
- 0–100 per application and environment
- 90 and above healthy · 70–89 degraded · below 70 failing
- Deductions weighted by severity
- 30-day trend and what changed since yesterday
Runs anywhere
- Target: a small 2 vCPU / 4 GB machine
- Remote runner inside your network, outbound-only
- Screenshots stay where the runner runs
- WebP captures with retention limits
As a product
- Multi-tenant and white-label
- Signed licence verified offline
- Monitors any web application through adapters — Zagru One is the reference
- Coming: YAML-defined journeys and a recorder for non-developers
Security and data
It watches your app. Nothing watches you.
Pulse holds credentials to your application, so it is built to keep them — and everything it sees — close.
No AI, by design
Every check is deterministic and repeatable. Nothing is sent to a model.
Data stays with the runner
Screenshots stay where the runner runs, unless you choose central storage.
Write-only credentials
Test-account credentials are encrypted with AES-256-GCM and never shown again once saved.
Outbound-only runners
Runners inside your network connect out, after a one-time enrolment; no inbound ports.
Every change audited
Single sign-on with an allow-list, owner, admin, developer and viewer roles, and an audit record for every change.
No telemetry
No tracking, no external CDNs, no external fonts.
In the suite
Sold on its own. Stronger together.
Pulse opens every screen of Zagru One every day — its first full sweep found 500. Through adapters it watches any web application, so it is sold on its own.
Questions
What buyers ask us first.
Is it a load-testing tool?
No. Pulse is synthetic monitoring and visual regression — it checks that every screen and journey works and looks right. It does not generate load and does not publish public status pages.
Does it use AI?
No. Every check is deterministic, cheap and repeatable — deliberately.
How do you avoid false alarms?
A failure that passes on retry is recorded as passed and flaky. A visual difference is a warning first and becomes a failure only after two consecutive runs without an approved baseline. Issues open after two failing runs and close after three passes.
Can it test applications behind our firewall?
Yes. A remote runner inside your network connects outbound only, and screenshots stay with it.
Which applications can it monitor?
Any web application, through adapters. Zagru One is the reference adapter.
Is it available today?
Zagru Pulse is in early access. We are working with a small number of design partners; request a demo to join.
Know before your users do.
Point Pulse at one application. Tomorrow morning, you'll have its health score.
Or write to hello@zagru.com