CLI-first cron & job monitoring built for automated infrastructure.
No dashboards to babysit. No noisy alerts. Just reliable signals.
Alerts are delivered freely. Interruption is limited by design.
Built for DevOps engineers who live in the terminal.
Low-latency monitoring from anywhere in the world.
A specialized tool, not generic full-stack monitoring.
Forever free. No credit card required.
Includes
Billed monthly Billed yearly ($90/year)
Perfect for side projects
Billed monthly Billed yearly ($290/year)
Everything needed for production
Billed monthly Billed yearly ($990/year)
Designed for critical workflows
Included in all plans. Can receive any job monitoring alert (Late, Missing, Overrunning, Recovered, Critical).
Delivery channels decide where alerts go.
Reserved for failures that violate a job's declared execution guarantees and require immediate human action.
| Plan | Per billing cycle |
|---|---|
| Free | - |
| Developer | 5 |
| Pro | 50 |
| Business | 500 |
Delivered via SMS or WhatsApp. Counts only when a job enters a critical state. No repeats while unresolved.
| Feature | Free | Developer | Pro | Business |
|---|---|---|---|---|
| Reliability | ||||
| Checks | 10 | 20 | 200 | Unlimited |
| Data retention | 7 days | 30 days | 90 days | 1 year |
| Cron schedule support | ||||
| Interval (period) schedules | ||||
| Maintenance windows | ||||
| Error log capture | — | |||
| Job duration tracking | — | |||
| Alert Delivery | ||||
| Email alerts | ||||
| Telegram alerts | ||||
| Slack / Discord | - | |||
| Webhooks | - | |||
| Notification groups | - | |||
| Interruptive Alerts | ||||
| Critical interruptions | - | 5 | 50 | 500 |
| Escalation rules | - | - | ||
| Escalation chains | - | - | - | |
| Status Pages | ||||
| Status pages | 1 | 1 | 5 | 10 |
| Automatic status sync | — | |||
| Private (token-protected) pages | — | — | ||
| Custom domain | — | — | ||
| Remove Pakyas branding | — | — | ||
| Custom CSS | — | — | — | |
| Email subscribers | — | — | ||
| Team & Access | ||||
| Team members | 1 | 3 | 10 | Unlimited |
| API access | ||||
| CLI tool | ||||
| Role-based access (RBAC) | — | — | — | |
| Support | ||||
| Community support | ||||
| Email support | — | |||
| Priority support | — | — | — | |
Pakyas is built specifically for cron and background jobs. Here’s how that changes things.
| Feature | Pakyas | Traditional cron monitors | General uptime tools |
|---|---|---|---|
| Core Philosophy | |||
| Primary purpose | Verify job execution | Detect missing pings | Monitor endpoints |
| Designed for | Cron & background jobs | Simple schedules | Websites & APIs |
| Signal type | Execution + duration | Ping received | HTTP availability |
| Developer Workflow | |||
| CLI-first setup | |||
| Automation / IaC friendly | Limited | Limited | |
| CI/CD friendly | |||
| Fast global ingestion | |||
| Alert Quality | |||
| Duration-aware alerts | |||
| Execution validation | |||
| Low-noise alerts | |||
| When you're interrupted | On broken guarantees | On failures / thresholds | User-configured |
| Failure context | Limited | Limited | |
| Pricing Philosophy | |||
| Per-alert fees | Sometimes | Often | |
| Surprise overages | |||
| Transparent annual pricing | |||
Pakyas validates execution success and duration, not just "pings". It's designed for workflows where knowing if a job finished is as important as knowing it started.
Absolutely. Many teams use uptime tools for their marketing site and Pakyas for their backend jobs and workers.
We process comprehensive execution data and logs per job, not just a single HTTP hit. We're built for production reliability, not just as a simple reminder service.
Start with 10 free checks. No credit card required.
Get started for free