Scheduled runs
Each plan covers a number of scheduled runs per 30-day month, worked out from your cron schedules. Less frequent jobs leave room for more of them.
Pricing
Start free.
Scale when it pays off.
Transparent monthly plans for reliable HTTP cron jobs. Begin with five free jobs, then upgrade only when your automation needs more runs, longer timeouts, or deeper history.
Free plan included
Cancel anytime
No hidden fees
Plans
Pick the plan that matches your runtime.
All prices exclude VAT. Paid plans are billed monthly and can be changed from the billing portal.
| Compare plans | Free €0 forever | Starter Free €5.99 then per month First month free | Most popular Pro Free €12.99 then per month First month free | Business €12.49 €24.99 then per month 50% off first month | Enterprise €49.99 €99.99 then per month 50% off first month |
|---|---|---|---|---|---|
| Limits | |||||
| Active cron jobs | 5 | 25 | 50 | Unlimited | Unlimited |
| Scheduled runs / month How many times your jobs can be scheduled to fire in a 30-day month, added up across all active jobs. Reserved from your schedules up front, so it never runs out mid-month. A job running every 5 minutes uses 8,640 runs a month. Hourly uses 720. | 3,000 | 10,000 | 30,000 | 90,000 | 300,000 |
| Shortest schedule Set by the monthly run allowance rather than by a separate rule. A job firing every 15 minutes reserves 2,880 runs a month, so a plan has to be able to afford it. | Every 15 min | Every 5 min | Every 2 min | Every minute | Every minute |
| Request timeout A request still running after this is cancelled and recorded as a timeout failure. It applies to every job on the account. | 20 seconds | 60 seconds | 150 seconds | 300 seconds | 600 seconds |
| Heartbeat monitors Watches work that runs somewhere we cannot reach, like a crontab on your own server. Your script pings a URL when it finishes, and we alert you when that ping stops arriving. Monitors have their own allowance and never use your scheduled runs. | 2 | 10 | 25 | 75 | 200 |
| Automatic retries A failed run is retried this many times before the failure is final and the alert goes out. | None | Up to 1 | Up to 2 | Up to 3 | Up to 5 |
| Run history per job How many past runs are kept per job, with their status code, duration and stored response. | 5 runs | 20 runs | 30 runs | 40 runs | 50 runs |
| Job chaining Run one job when another finishes, up to five deep, instead of guessing at a safe gap between two schedules. A follower is priced against its parent schedule, so it costs runs like any other job. | Not on this plan | Included | Included | Included | Included |
| One-off requests / month A request scheduled for a single moment instead of a repeating pattern. These have their own allowance and never draw from your scheduled runs. | 5 | 20 | 60 | 150 | 400 |
| Alerts | |||||
| Email alerts / day Capped because email has a sending reputation to protect: a mailbox provider throttles a sender that floods, and that lands on everyone. Resets at 00:00 UTC. Digests do not count against it. | 5 | 20 | 50 | 100 | Unlimited |
| Webhook, Slack, Discord, Telegram / day No daily cap on the paid plans. These have no shared sending reputation, and their providers publish per-second rate limits that CronEngine already respects by backing off when asked. Free keeps a cap on every channel. | 5 | Unlimited | Unlimited | Unlimited | Unlimited |
| Notification channels per job How many destinations a single job may deliver to at once. Every channel type is available on every plan; this is how many one job may use together. | 1 | 1 | 2 | 3 | 3 |
| Notify on every run A message for each run, not only for failures and recoveries. Useful for a job you want positive confirmation from. | Not on this plan | Included | Included | Included | Included |
| Keeps running after repeated failures On Free, a job that fails 20 times in a row is paused automatically so a broken endpoint stops burning runs. Paid plans leave it to you. | Not on this plan | Included | Included | Included | Included |
| Email, webhook, Slack, Discord, Telegram | Included | Included | Included | Included | Included |
| Alert after N consecutive failures Hold the alert until a job has failed a number of times in a row, so one flaky minute does not wake anybody. | Included | Included | Included | Included | Included |
| Weekly or monthly email digest A summary of your runs that does not count against the daily cap above. | Included | Included | Included | Included | Included |
| Also included | |||||
| Custom headers, request body and auth GET, POST, PUT, PATCH and DELETE, with bearer or basic auth. Credentials are encrypted at rest. | Included | Included | Included | Included | Included |
| Response body storage Up to 10 KB of each stored response, kept with the run so you can see what the endpoint actually said. | Included | Included | Included | Included | Included |
| CSV export of run history | Included | Included | Included | Included | Included |
| Ready to start? Change or cancel at any time from the billing portal. | Start for free | Get Starter | Get Pro | Get Business | Get Enterprise |
Upgrade or downgrade
Move plans from the billing portal. If a lower plan cannot fit your usage, CronEngine warns you before switching.
Alerts and digests
Daily caps apply separately to immediate alert channels. Weekly or monthly email digests summarize your runs without consuming those caps.
Ready?
Five jobs are free forever.
Start small, let the scheduler prove itself, then upgrade only when your jobs need more runs or a longer timeout.
Create your free account