Heartbeat and uptime monitoring

Know your jobs are alive.

Cron jobs, scheduled automations and AI agents fail quietly: they simply stop running, and nobody notices until something downstream breaks. Vivere gives each job a URL to ping. When the pings stop, you get told.

Start free Two-minute quickstart

# at the end of your job
curl -fsS -m 10 --retry 3 https://vivere.dev/p/<monitor-id>

# or wrap it, and get exit code, duration and output too
vivere run --url https://vivere.dev/p/<monitor-id> -- ./backup.sh

Dead man's switch

Set a period or a cron expression plus a grace window. If a successful ping does not arrive in time, the monitor goes down and alerts fire. Recovery alerts when it comes back.

Runs, not just pings

Ping /start first and Vivere records duration, exit code and the last 64 KB of output for every run. Failures show up with the log attached.

Uptime checks too

Point an HTTP monitor at a URL. Expected status, keyword match, timeout and failure threshold, checked every minute on paid plans.

Alerts where you are

Email, webhooks with signed payloads, Slack, Discord, Telegram and ntfy. Retries with backoff, and a test button for every channel.

Built for automation builders

Copy-paste guides for cron, systemd, Windows Task Scheduler, GitHub Actions, Kubernetes, Docker, n8n, Make, Zapier, Python, Node, Go and Claude Code.

Public status page

Mark monitors public and share a status page with 30-day uptime, plus SVG badges for your README.

Why jobs stop without telling you

These pages are the answers to the questions people type at eleven at night. They are useful whether or not you ever use Vivere.

Cron job not running

The five usual causes, in the order worth checking.

GitHub Actions schedule stopped

Disabled after 60 days of repository inactivity, and four more.

CronJob missed its schedule

Miss 100 starts and the controller gives up for good.

What a dead man's switch is

Why alerting on silence catches what error alerting cannot.

Crontab explainer

Free tool: read an expression in English and see its next ten runs.

Grace period calculator

Free tool: how late should you let a job be?

All answers and comparisons

Simple pricing

Free

$0 forever

No card needed

10 monitors
5m minimum period
Email and webhook alerts

Start free

Pro

$9/month

or $79/year

100 monitors
1m minimum period
All alert channels
5 seats for viewers or editors

Choose Pro

Team

$29/month

or $249/year

500 monitors
1m minimum period
All alert channels
100 seats for viewers or editors

Choose Team

Full comparison and yearly prices

Questions

How is this different from Healthchecks.io or Cronitor?

Same idea, a smaller and cheaper product with the automation-platform and AI-agent guides written first, status pages included, and a wrapper CLI that captures output. If you need SMS and phone calls, those tools are the better fit. Side by side: Healthchecks.io, Cronitor, UptimeRobot.

What counts as a ping?

Any HTTP request to the monitor's URL: GET, POST, HEAD or PUT, from anything that can make one. The body of a POST is kept as the run log.

What if Vivere itself goes down?

Then no alerts are sent until it is back, which is worth knowing before you depend on it. Vivere runs on one server, so there is one of everything. An independent check on GitHub's infrastructure requests the site every 15 minutes and emails the operator when it fails, so at least the failure of the failure-detector is noticed by something else. The rest of the honest version is on the about page.

Where is my data?

On servers we operate. Monitor names, ping timestamps, run logs and alert destinations are stored; nothing is sold or shared. See the privacy policy.