CronWatch
PulseGate's liveness check found it on 27 Sep 2026; it is registered on GitHub and has been in the index since 27 Sep 2026. How this is checked
CronWatch is an MIT-licensed library that records scheduled-job runs in an application’s own database and alerts when jobs are missed, fail, get stuck, run slowly, or exceed budget. It supports TypeScript and Ruby on Rails applications and includes an MCP server for agent-assisted setup and triage.
Inferred · not functionally tested
Overview
6 featuresPurpose: Detecting missed, failed, stuck, slow, or over-budget scheduled jobs without running a separate monitoring service.
Inferred · not functionally tested
Audience: developers maintaining TypeScript or Ruby on Rails applications
Inferred · not functionally tested
Functions: monitoring, agents
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI, WEB · deployment: browser, cli, self_hosted, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: cronwatch.dev · rubygems.org · github.com. These links do not verify the individual claims.
In the Other observability space, CronWatch takes a focused approach. Inferred · not functionally tested: It focuses on detecting missed, failed, stuck, slow, or over-budget scheduled jobs without running a separate monitoring service. Inferred · not functionally tested: It is built as an open-source project for developers maintaining TypeScript or Ruby on Rails applications. Basis unknown · not verified: CronWatch is open source under the MIT license. Basis unknown · not verified: It ships for the web, the command line, and API, and it can be self-hosted.
CronWatch first shipped in 2026. Development happens publicly on GitHub with 7 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include run recording, missed-run alerts, and failure alerts. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Run recording
- Missed-run alerts
- Failure alerts
- Stuck-job detection
- Slow-run detection
- Budget alerts
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- CLAUDE.md
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed27 Sep · 03:22 UTCcronwatch seen via RubyGems newly publishedSource: RubyGems newly published · Open
Frequently asked questions about CronWatch
- What is CronWatch?
- Inferred · not functionally tested: CronWatch focuses on detecting missed, failed, stuck, slow, or over-budget scheduled jobs without running a separate monitoring service. It is catalogued under Other observability on PulseGate.
- Who is CronWatch for?
- Inferred · not functionally tested: CronWatch is an open-source project built for developers maintaining TypeScript or Ruby on Rails applications.
- Is CronWatch free?
- Basis unknown · not verified: Yes — CronWatch is open source under the MIT license and free to use.
- What platforms does CronWatch run on?
- Basis unknown · not verified: CronWatch runs on the web, the command line, and API. It can also be self-hosted.
- Is CronWatch still maintained?
- PulseGate's liveness check found it on 27 Sep 2026. Its GitHub repository shows 7 commits in the last 90 days.
- How long has CronWatch been around?
- CronWatch first shipped in 2026.
- Is CronWatch open source?
- Basis unknown · not verified: Yes — CronWatch is open source under the MIT license, developed on GitHub.
- Does CronWatch have an API or integrations?
- Inferred · not functionally tested: Yes — CronWatch exposes an MCP server.
Similar projects
Closest matches by what these projects do