Simple pricing

Start free with real monitors on real jobs. Upgrade when you need more capacity or longer status history — no sales calls required.

Free
Try Gonewatch with a handful of monitors.

$0

No credit card required

  • 5 monitors
  • Email alerts
  • 7 days of status history
Basic
Recommended
For side projects and indie developers who rely on alerts.

$9/mo

  • 25 monitors
  • Email alerts
  • 90 days of status history
Pro
For small teams running many expected events in production.

$24/mo

  • 100 monitors
  • Email alerts
  • 1 year of status history

All plans include email alerts and integration snippets. Paid plans are activated from billing in your dashboard after signup.

Pricing questions

Common questions about plans and billing.

What's included in every plan?

All plans include email alerts on down and recovery, integration snippets (cURL, Node, Python), and a dashboard with activity history. Paid plans add more monitors and longer status history retention.

How does annual billing work?

Annual plans are billed once per year at roughly 17% off the monthly rate. You can switch between monthly and annual billing from the customer portal.

What happens if I exceed my monitor limit?

You won't be able to create new monitors until you upgrade or delete existing ones. Existing monitors keep running and alerting.

Is there a free trial for paid plans?

The Free plan is your trial — use it to validate alerts on real jobs. When you're ready for more monitors or longer history, upgrade from billing in one click.

General questions

How Gonewatch works day to day.

Do I need a credit card to start?

No. The Free plan includes monitors, email alerts, and status history with no credit card required. Upgrade from your dashboard when you need more capacity.

What counts as a monitor?

One monitor tracks one expected event — for example a nightly backup cron, a weekly report job, or a data pipeline step. Each monitor has its own heartbeat URL, schedule (fixed time of day or rolling interval), and grace period.

How do heartbeats work?

After your job succeeds, POST to your monitor's unique URL. Gonewatch records the ping and expects the next one on your schedule — at a fixed time of day or on a rolling interval — with a grace window after each expected window. No agent or SDK is required — a curl in your script is enough.

How fast will I be alerted?

Within a few minutes after your grace period ends without a heartbeat — typically under three minutes. Gonewatch checks monitors continuously, marks the monitor Down at that threshold, and sends your alert email. You are not waiting on your job's next scheduled run to find out.

Can I send data with a heartbeat?

Not yet. Today heartbeats are a simple POST to confirm an event ran. Sending JSON payloads with duration, counts, or other metadata is planned — that data will power metrics and performance history on the roadmap.

What if my job runs late but still succeeds?

As long as a heartbeat arrives before the grace window ends after the expected time or interval, the monitor stays healthy. Tune grace period to match how late your jobs can run without being a problem.

Can I change or cancel my plan?

Yes. Subscribers manage plans, billing interval, payment method, and cancellation through the Stripe customer portal in your dashboard — no need to email support.

Feedback & contact

Gonewatch is early — your input shapes what we build next. Report bugs, request features, or say hello.

Optional. Include it if you'd like us to follow up.

Ready to catch silent failures?

Create a free account, add your first monitor, and paste one URL into your cron or script.

Get started free