Gonewatch

Gonewatch

Heartbeat monitoring for cron jobs and backups

gabrianmak
@gabrianmak
Published on Sep 22, 2026
Visit site
1 PeerPush
🚀
Awarded
Just Launched
PeerPush

Details

Follow on
LinkedIn
Pricing
Freemium from $9
Platforms
WebAPI

Discovery signals

How AI and people discover Gonewatch on PeerPush

AI-readyAI-readyWhether this product carries the structured data - use cases, audiences, platforms - that lets AI match it to the right questions.
Structured

Described for AI to match

Described for AI with use cases, audiences, platforms and pricing so assistants can match it to the right questions.
Discoverable nowDiscoverable nowWhether this product is queryable through the PeerPush API and MCP right now.
Live

Via the PeerPush API and MCP

Queryable through the PeerPush API, MCP and semantic search from day one.

About Gonewatch

Gonewatch is heartbeat monitoring for expected work — cron jobs, nightly backups, and scheduled GitHub Actions. It is not uptime monitoring of a public URL. You create a monitor with a fixed time of day or a rolling interval, plus a grace window. After the job succeeds, POST to a unique heartbeat URL (curl, Node, Python, or uses: gonewatch/heartbeat@v1). If that ping never arrives, Gonewatch marks the monitor Down and emails you. Paid plans add Slack. A failed job should not ping, so a red X on GitHub or a failed cron stays a miss. GitHub already emails failed workflow runs. It does not email a schedule that never started. Silence is the alert. No agent on the box. Free plan with 3 monitors and email alerts, no credit card. Basic starts at $9/month. Website: https://www.gonewatch.com GitHub Action: https://github.com/marketplace/actions/gonewatch-heartbeat

Screenshots

Screenshot 1 of Gonewatch
Screenshot 2 of Gonewatch

Reviews (0)

No reviews yet. Be the first to rate this product!

Comments (1)

gabrianmak
@gabrianmak

Would love eyes from anyone watching backups, crons, or scheduled Actions. If something is confusing on the first monitor, tell me.