The nightly backup
Cron entry gets silently dropped after a server migration. Nobody notices until a restore is needed — and there's nothing to restore.
Cron · heartbeat · dead man's switch · Kubernetes
Cron job monitoring and heartbeat monitoring for scheduled work — plus a real Kubernetes HealthCheck operator. Alerted the moment a job, worker, or CronJob goes silent.
Free forever · no credit card · not website uptime monitoring
Ping history · last 10 runs
# before — runs silently, fails silently 0 2 * * * /path/to/backup-script.sh # after — the ping only fires on success 0 2 * * * /path/to/backup-script.sh && \ curl -fsS https://ping.seiri.app/NkdyngWn9z
The scariest failures don't throw exceptions. Here's how "did it run?" shows up in the real world.
Cron entry gets silently dropped after a server migration. Nobody notices until a restore is needed — and there's nothing to restore.
The billing script exits 0 but skips a batch because of a timezone bug. Customers don't get invoiced, and finance finds out at month-end.
An upstream job hangs before the transform step finishes. The dashboard keeps showing yesterday's numbers, and nobody's watching the pipeline itself.
A pod gets evicted mid-run during a node drain. The job shows no error in `kubectl` logs — it just never reached completion.
Own the niche — not “uptime monitoring”
Cornerstone pages for the searches that match what Seiri actually does: cron, heartbeats, dead man's switches, and Kubernetes.
Kubernetes is a first-class surface →Seiri flips monitoring around: instead of polling a URL, your job tells Seiri it's alive.
Tell Seiri the expected schedule — cron expression or interval — and a grace period. You get a unique ping URL and a unique @ping.seiri.app email address.
Add a curl call, send an email, or install the seiri-kube-agent Helm operator and declare HealthCheck CRs for in-cluster workloads.
No ping within the grace period triggers an instant alert to Slack, Discord, email, SMS, or a custom webhook — before anyone notices the impact.
Pick whichever fits how your job runs.
Locked-down networks, legacy cron boxes, and internal servers often can't make outbound HTTP calls — but they can almost always send mail. Every Seiri monitor gets its own @ping.seiri.app address. Send it an email when your job finishes, and Seiri treats it exactly like an HTTP ping.
Install the Seiri HealthCheck Operator into your cluster. It watches HealthCheck custom resources and continuously checks Deployments, Pods, StatefulSets, DaemonSets, and Jobs — reporting phases like Healthy, Unhealthy, and Missing back to Seiri for alerts and dashboards.
healthchecks.monitoring.seiri.appEverything you need to trust that your background jobs actually ran.
Push-based checks catch jobs that never run, hang, or exit early — the failures a URL probe would never see.
A unique @ping.seiri.app address per monitor, for jobs that can send mail but can't make HTTP calls.
Install seiri-kube-agent with Helm. It watches HealthCheck CRs and reports Deployment, Pod, Job, StatefulSet, and DaemonSet health to Seiri.
Slack, Discord, email, SMS, and custom webhooks — with escalation across channels when the first alert goes unacknowledged.
Share a public or custom-domain status page for the jobs and services your team or customers care about.
Create and manage monitors programmatically with scoped API keys — provision monitoring as part of your deploy pipeline.
Start free. Upgrade when you outgrow it. No fake trials — just a generous free tier.
Free forever
For growing teams
For high-volume infra
If something on your infrastructure is supposed to run on a schedule, Seiri is built for you.
Cron jobs, queue workers, and scheduled scripts that run without anyone watching.
ETL pipelines and batch jobs where a stale dashboard is worse than an error message.
seiri-kube-agent HealthChecks across Deployments, Jobs, and clusters — plus heartbeat webhooks for everything else.
Backups, reports, and integrations you can't afford to find out failed a week later.
No. Seiri doesn't poll a URL to see if your website is up. It's built for scheduled work — cron jobs, background workers, and Kubernetes CronJobs — that ping Seiri when they finish. If the ping doesn't arrive on schedule, you're alerted immediately.
You create a monitor with an expected schedule and grace period, then add one line to your job: a curl request to your unique ping URL, or an email to your unique @ping.seiri.app address. If Seiri doesn't receive that ping within the expected window, it sends an alert.
An email heartbeat lets a job check in by sending an email instead of an HTTP request. This works for systems with restricted outbound access, legacy servers, or anything that can send mail but can't easily make an HTTP call. Just send an email to your unique @ping.seiri.app address.
Yes. Install seiri-kube-agent with Helm (needs your cluster’s auth token + cluster ID from cloud.seiri.app). Create HealthCheck CRs for Deployments, Pods, Jobs, StatefulSets, or DaemonSets — phases like Healthy / Unhealthy / Missing show up in Seiri. CronJobs can also still ping ping.seiri.app on completion.
Yes. Every plan includes at least one status page you can share with your team or customers, and Growth and Scale plans support a custom status domain.
Yes — free forever, no credit card required. It includes 10 monitors, a 5-minute check interval, 3 seats, 1 status page, 1 email heartbeat, and 1 API key.
You'll know the moment it doesn't. Set up your first heartbeat monitor in under two minutes.