Both Pakyas and Cronitor are hosted cron job monitors that page you when a scheduled job fails, misses its window, or runs too long. This page lays out the concrete differences — signal model, state vocabulary, CLI tooling, alert handling, pricing, and integrations — so you can pick the right fit without the marketing gloss.
| Dimension | Pakyas | Cronitor |
|---|---|---|
| Signal model | Execution-signal (dead man's switch) model: jobs ping a URL at start, success, or failure. A single ping URL per check (https://ping.pakyas.com/{public_id}) with /start and /fail (or exit-code) modifiers, plus optional run pairing and duration capture. Ingestion runs on a global Cloudflare edge worker. | Ping/heartbeat telemetry model: jobs send pings to cronitor.link/p/{apiKey}/{monitorKey} (or an anonymous cronitor.link/{monitorKey}) with state=run / complete / fail / ok events. Supports run pairing via a 'series' ID that collates a run's start and finish, and duration capture via a metric=duration value. |
| State vocabulary | Job-accurate states surfaced to users: Waiting for first ping, On Schedule, Late, Missing, Overrunning, Error, and Paused. Avoids server-style 'up/down' language in favor of execution-centric terms. | Surfaces monitors as 'healthy', 'failing', or 'paused', driven by telemetry states (run / complete / fail / ok) plus schedule and performance rules that detect missed runs and overruns. The vocabulary is health-centric rather than splitting Late, Missing, and Overrunning into distinct user-facing states. |
| CLI tooling | First-class CLI shipped as the `pakyas` binary (pakyas-cli crate) for wrapping and pinging jobs from the command line. | Ships 'cronitor-cli' (github.com/cronitorio/cronitor-cli), a Go tool that auto-imports and syncs existing crontabs (sync), wraps commands (exec), and bundles a local 'Crontab Guru' web dashboard; actively maintained. Note it is source-available under the Functional Source License (FSL-1.1-MIT) — free to use but not OSI-approved open source (it converts to MIT two years after each release), not fully open source as sometimes assumed. |
| Alert deduplication / flap handling | Threshold-based dampening: alerts fire only after a configurable number of consecutive missed/failed pings (alert_after_miss_pings / alert_after_fail_pings), with per-check throttle config and recorded suppression decisions to avoid noise on flapping jobs. | Fine-grained, per-monitor noise controls: grace_seconds (wait before alerting, with no alert if it recovers in the window), failure_tolerance (tolerate N fail events first), schedule_tolerance (allow N missed runs), and consecutive_alert_threshold (require N consecutive failures before alerting). Recovery alerts fire on return to healthy. |
| Pricing | Four flat tiers: Free $0/mo (up to 10 checks), Developer $9/mo, Pro $29/mo, Business $99/mo. 14-day trial on paid plans; Free usable indefinitely. Flat pricing, not per-monitor. | Hacker free tier (5 monitors, 1 user, email + Slack alerts). Business is pay-as-you-go: $2/monitor/mo plus $5/user/mo, with 12-month data retention and a 14-day trial. Enterprise starts at $6,000/year. Per-monitor billing means cost scales with the number of jobs you watch. |
| Open-source / self-hosted | Hosted SaaS only — Pakyas does not offer a self-hosted or open-source edition. | Hosted SaaS. The cronitor-cli companion tool is source-available (FSL-1.1-MIT) and the bundled Crontab Guru dashboard runs locally, but the monitoring service itself is not self-hostable or open source. |
| Integrations | Built-in delivery to Email, Slack, Discord, Telegram, Webhooks, SMS, and WhatsApp. | Email, SMS, Slack, Microsoft Teams, Discord, Telegram, Google Chat, Lark, PagerDuty, Opsgenie, Splunk On-Call (formerly VictorOps), and webhooks. Most channels beyond email and Slack require the paid Business plan. |
Cronitor is the more established product with a mature CLI that shines at importing and syncing existing crontabs, broad integration coverage (PagerDuty, Opsgenie, Microsoft Teams, and more), and granular per-monitor alert controls. Its per-monitor, pay-as-you-go pricing can be cheaper if you only watch a few jobs, but it scales linearly and can create pressure to ration monitors or skip low-frequency jobs to control cost — and most alert channels sit behind the paid Business plan. Pakyas counters with flat-tier pricing that encourages monitoring everything, a more granular job-state vocabulary (Late vs Missing vs Overrunning), and every alert channel — including WhatsApp — available on the free tier. The honest tradeoff: Cronitor matches Pakyas on CLI tooling and consecutive-failure alert thresholds, and outclasses it on enterprise integrations and track record, while its cronitor-cli is source-available (FSL-1.1) rather than fully open source; neither service is self-hostable. Choose Cronitor for crontab auto-sync, enterprise alerting, and maturity; choose Pakyas for predictable flat pricing, clearer job-centric semantics, and a more generous free tier.
New to the terminology? See the cron monitoring glossary for plain-language definitions, or explore everything Pakyas tracks on the features page.
Ready to try Pakyas for yourself?
Start monitoring your cron jobs with execution-signal precision — free for up to 10 checks, no credit card required.
Start monitoring free