Plan limits
Every plan states its limits plainly. The four that shape day-to-day use are the number of monitors, how often a monitor can check in, how long check-in history is kept, and how many people are on the team.
| Free | Starter | Pro | Business | |
|---|---|---|---|---|
| Monitors | 20 | 100 | 300 | 1,000 |
| Fastest check-in | every 1 min | every 30 sec | every 10 sec | every 10 sec |
| Raw ping history | 7 days | 30 days | 12 months | 18 months |
| Team members | 1 | 5 | 25 | 50 |
Everything else is the same across plans: all 16 integration channels, tags, filtering and status badges, the escalation ladder, the full API, and two years of daily uptime and duration statistics for every monitor. Nothing about how CronWarden monitors is gated. The tiers differ only in scale.
What the limits mean
- Monitors is a hard ceiling. Creating one past your limit — in the dashboard or through the API — is rejected until you remove one or upgrade.
- Fastest check-in is the shortest schedule a monitor may have. A schedule (interval or cron) that checks in more often than your tier allows is rejected.
- Raw ping history is how far back individual check-ins are kept. Older raw pings are pruned, but the daily rollups behind uptime and duration charts (per-day success/failure counts, duration and value ranges) are kept for two years on every plan, so the long view outlives the raw detail.
- Team members is how many people can be on the team.
Beyond Business
If you need more than 1,000 monitors, faster check-ins, or longer retention, those are arranged case by case — reach out and we'll size a plan to fit.