Distributed ingest
Runs across multiple nodes, so a single one can go down without losing a ping or a status change.
Never miss a
failed job again.
Monitor cron jobs, workers, and scheduled tasks with instant alerts when a check-in is missed or a /fail ping is sent.
We also support flexible scheduling and multiple check types, from heartbeat checks and simple log-only pings to advanced job-based and rule-based monitoring.
check-87ab ยท live
5min window
HTTPS Ping
60
SEC TO ALERT
Pulzera resets the countdown the moment it receives a check-in.
check-87ab missed its window
now
No ping for 5min. Alert sent to email and #ops.
Works with
cron
systemd timers
Kubernetes CronJobs
Windows Task Scheduler
GitHub Actions
Google Cloud Scheduler
AWS EventBridge Scheduler
Azure Functions timer
Apache Airflow
Quartz Scheduler
… or anything that can send an HTTPS request.
No credit card required
Start on the free plan in minutes - no card, and no agent to install, just an HTTPS call.
Secure sign-in
Sign in with passwords and optional 2FA, passkeys, SSO, or magic links.
Reliable multi-channel alerts
Route alerts to email, Slack, PagerDuty, webhooks, and more. Failed sends retry automatically.
Support for encrypted data at rest
Optionally capture request headers and bodies, encrypted at rest with AES-256-GCM on the Enterprise plan.
Web application
See every job at a glance.
One clean dashboard shows the status, last ping, duration, and history of every check. No dense config, no digging - just open it and know exactly what's running and what's not.
app.pulzera.com
Features
Everything you need to trust the silence.
A job that never ran doesn't throw an exception - it just goes quiet. Pulzera turns that silence into a first-class signal you can route, batch, and act on.
Three ways to check in
Heartbeat for regular check-ins, rule-based for JSON payloads scored by your own rules, and log-only to capture events without alerting.
Job duration tracking
Pair /start/<run-id> and /end/<run-id> to measure runtime and catch jobs that hang halfway through.
Rule engine on payloads
Send JSON with your ping and write a simple rule on its fields to decide pass / fail.
Multi-channel alerts
Route alerts to email, Slack, PagerDuty, webhooks, Pushover, and Gotify. Failed sends retry automatically, so a flip never goes unnoticed.
Simple, fast UI
A clean dashboard with just the features you need and nothing more - readable at a glance, in light, dark, and system themes.
How it works
How a ping - or the lack of one - becomes an alert.
From the request your job sends to the alert that reaches you - here's the path each ping takes.
-
1
Send
Your job sends a one-line HTTPS request to its check's endpoint.
-
2
Accept at node
A node accepts the ping and holds it until it's safely forwarded to the server.
-
3
Process at server
Pings are checked against your rules and schedule. The moment a check changes state - or goes quiet - alerts go out to your channels.
High-level architecture (simplified)
How a ping flows through the distributed ingest cluster.
Ready to stop wondering whether your jobs ran?
Create your first check in under a minute. Start on the free plan - no card, no commitment, deactivate anytime.