Watchgoose is a cron and scheduled-job monitoring service for teams running backups, automations, and other recurring work that can report a result. When an expected success doesn't arrive after its schedule and grace period, we alert the people who need to know.
Your job does the work. Watchgoose watches for the signals you choose to send.
Create checks for cron jobs, backups, scripts, and other recurring work that can send a signal. Set a simple interval, cron expression, or OnCalendar schedule, plus a grace period for late runs.
Read the cron monitoring guide →Send a success signal only after the work succeeds. The first success arms missed-run monitoring; an explicit failure signal or a missed expected success can alert your team.
Read the monitoring documentation →Choose how your team receives alerts and organise checks by project. Review recent signals and plan-limited ping history when a job fails or goes quiet.
Explore notification channels →Publish an opt-in status page for selected checks, use the project-scoped API, or connect supported clients through the hosted MCP endpoint.
Explore MCP access →Practical details that shape how you monitor the work your team relies on.
Watchgoose is headquartered in the United Kingdom. Hosting and operations stay in Europe. For details on data handling, see our privacy policy.
Watchgoose does one job well: it watches scheduled work and tells you when it fails or goes quiet. No bloated, do-it-all platform to learn and configure, just checks, schedules, grace periods and alerts.
Start with 10 checks on the Free plan. You can monitor real scheduled work before choosing a paid plan.
Publish an opt-in status page for any project, on every plan. Show the current state of up to 100 selected checks under client-safe names, without giving viewers an account.
Anything that can make an HTTP request or send an email can report to Watchgoose. Add one line to a crontab, script or CI step; there is nothing to install on your servers.
The hosted MCP endpoint lets compatible clients work with one owner-approved project. It starts read-only; writing requires explicit authorization and project permission.
Qualifying Open Source projects can receive a needs-matched paid plan at no charge while eligible. We pledge 5% of profit to Open Source projects.
Comparing products? Read our factual monitoring comparisons for dated, sourced details.
Bartek saw clients run into serious trouble when important cron jobs failed unnoticed. An engineer at heart, he built a lean, focused monitoring service to help teams spot missing signals before the silence causes harm.
A long-time FreeBSD developer, Bartek put support for Open Source at the core of Watchgoose. Qualifying projects can use a needs-matched paid plan at no charge while eligible, and the service pledges 5% of profit. He also wanted European companies and developers to have a European monitoring choice. Watchgoose was founded in June 2026 after months of development and private testing. Bartek personally handles development, support, infrastructure, operations and marketing.
Read about our Open Source program and current plans.
Watchgoose made backup job monitoring effortless for us. When our scheduled backup job failed, we knew immediately and were able to fix it before customers noticed. That visibility gives our team confidence that important backups are running as expected and will never fail silently.
Jeff Harris, Founder at 1BSV.netI was discovering too many cases where our clients' cron jobs would silently fail, where no one would find out for days or weeks that a cron job was broken. Watchgoose gave us and our clients the peace of mind that when a cron job breaks we will know instantly and be able to fix it before it turns into a problem.
Mariusz Zaborski, CTO at testclix.comChoose a schedule and grace period for work you already run.
Add a ping to the job. Its first success starts missed-run monitoring; send an explicit failure if your job detects one.
Connect notification channels for the project. When a configured job reports failure or misses an expected success, Watchgoose alerts them.
Review the check's status and available signal history. For current plans and limits, see pricing.
Getting started is self-serve: follow the setup documentation and choose the alerts your team needs. Need help? Email Bartek. Free-plan support is best effort. For paid plans, we aim to reply within 24 hours, including weekends and public holidays.
New paid customers can request a 15–30-minute setup call to set up first checks and integrations and confirm monitoring works. Book a setup call or request one by email.
No. Your scheduler and backup tools still do the work. Watchgoose monitors the signals you add to those jobs; a success ping alone does not verify backup integrity or prove a restore will work.
A check starts watching for missed expected successes after its first success signal. A later missed signal is judged against its schedule and grace period.
Watchgoose was founded in June 2026 by Bartek Rutkowski. He personally handles development, support, infrastructure, operations and marketing. For questions about the service, email support@watchgoose.com.
Watchgoose is Europe hosted, operated & owned. For information about the data we handle, read our privacy policy.
Free includes 10 checks. Startup starts at EUR 17/month and Business at EUR 73/month; USD and GBP pricing is also published, excluding VAT.
You can cancel a self-serve subscription from billing settings or Paddle's management flow. Cancellation stops future renewals but does not automatically refund the current billing period.
Watchgoose is a hosted service; we do not describe the product itself as open source. Qualifying Open Source projects can get a needs-matched paid plan free while eligible, and we pledge 5% of profit to Open Source projects.
