Your hosting plan doesn't support cron jobs. Or it does, but the server goes down and takes the crontab with it. Or you're running a WordPress site on shared hosting where wp-cron.php only fires when someone visits the page. Whatever brought you here, you need an external cron service to call a URL on a schedule, and you'd rather not spin up infrastructure just to hit an endpoint every five minutes.
That's what online cron job services do. You give them a URL, a schedule, and they handle the rest. Some are free. Some charge per execution. Some bundle monitoring and alerts. We tested ten of them to help you figure out which one fits.
What to look for in an online cron job service
Before the list, here's what to pay attention to. This part matters more than the list itself.
Minimum interval and timeout. If you need a job every minute, a service with a 5-minute minimum won't work. And if your script takes 30 seconds to complete, a 15-second timeout kills the request mid-run.
Failure handling. What happens when your endpoint returns a 500? Some services retry automatically. Some just log it. Some don't even tell you. That gap between "retry 3 times then alert on Slack" and "silently fail" is how problems hide for three days before anyone notices.
Execution history. You want to see what happened: when the job ran, how long it took, what the server returned. Some services keep 50 records for two days. Others give you months of visual charts.
Pricing model. Per job, per execution, flat rate, or free. The models vary wildly. A service that costs $2/month for 3 jobs might cost $50 for 30. Another might be free but disappear tomorrow.
Monitoring integration. Most online cron job services just fire requests. If your server goes down between scheduled calls, the service has no idea. A few combine scheduling with actual monitoring: uptime checks, SSL tracking, failure alerts. You see the full picture instead of just "request sent."
Three types of online cron services
Not every service on this list does the same thing. Understanding the category helps you skip services that don't match your needs.
URL callers hit your endpoints on a schedule. That's their entire job. EasyCron, FastCron, cron-job.org, cronhost, Runhooks, and Cronless all fall here. Some add alerts and retries; none monitor what happens between calls.
Cloud platform schedulers are built into infrastructure platforms. Google Cloud Scheduler fires HTTP requests, Pub/Sub messages, and App Engine routes. AWS EventBridge, Vercel Cron Jobs, and GitHub Actions scheduled workflows serve the same role on their platforms. You only need these if you're already on that cloud.
Scheduling + monitoring combines both: run jobs on a schedule AND watch what happens. WatchCron sits here. Cloud Cron fires your HTTP requests while uptime, SSL, and domain monitoring track the infrastructure behind them. When a cron job returns a 503, you check the same dashboard and see the server went down 20 minutes earlier. Crontap and CronJobPro also offer monitoring features alongside scheduling, though with narrower scope.
The 10 services, compared
| Service | Free Tier | Paid From | Min Interval | Timeout (free / paid) | Alerts | Monitoring? |
|---|---|---|---|---|---|---|
| WatchCronUs | 1 job + 20 checks | $7/mo | 1 min | 60s | 19 channels | Yes |
| EasyCron | ~2 jobs (200 EPD) | $24/yr | 20 min / 1 min | 5s / 12h | Email, Slack, webhook | No |
| FastCron | 15 jobs | $6/mo | 5 min / 30s | 15s / 1h+ | Email, Slack, Discord, Telegram | No |
| cron-job.org | Unlimited | Free only | 1 min | 30s | Email only | No |
| Google Cloud Scheduler | 3 jobs | $0.10/job/mo | 1 min | 30 min | None built-in | No |
| Crontap | 2 items | $2.99/mo | 1 hr / 1 min | n/a | Email, Slack, Discord, Telegram | Yes |
| CronJobPro | 5 jobs | €3.99/mo | 15 min / 1 min | 60s / 5m+ | Email, Slack, Discord, webhook | Yes |
| cronhost | 3 jobs | $5/mo | 30 min / 1 min | n/a | Email, Slack, Discord, Telegram | Basic |
| Runhooks | 10 jobs | $19/mo | n/a | n/a | Email, webhook | No |
| Cronless | 5 jobs | $27/yr | 12 hrs / 30s | n/a | Pro only |
What it costs at scale
The comparison table shows entry pricing. Here's what happens when you scale to dozens or hundreds of jobs. Prices are for the cheapest plan that covers the job count at 1-minute intervals where applicable.
| Service | 10 jobs | 50 jobs | 100 jobs | 500 jobs |
|---|---|---|---|---|
| cron-job.org | Free | Free | Free | Free |
| Google Cloud Scheduler | $1/mo | $5/mo | $10/mo | $50/mo |
| FastCron | $6/mo | $20/mo | $50/mo | $50/mo (1,000 max) |
| WatchCronUs | $7/mo | $19/mo | $49/mo | Custom |
| EasyCron | ~$6/mo | ~$24/mo | ~$48/mo | ~$180/mo |
| CronJobPro | €3.99/mo | €14.99/mo | €49.99/mo | Custom |
| cronhost | $5/mo | $19/mo | $19/mo (unlimited) | $19/mo (unlimited) |
| Runhooks | $19/mo | $59/mo | $129/mo | Custom |
cron-job.org is free regardless of scale, but that price comes with 30-second timeouts, email-only alerts, and no SLA. Google Cloud Scheduler scales linearly at $0.10/job. FastCron and cronhost flatten at higher tiers: once you're on the top plan, adding more jobs costs nothing extra. EasyCron's EPD model means cost depends on frequency, not just job count. The figures above assume hourly jobs; per-minute jobs cost significantly more.
10 online cron services reviewed
Starting with the services that combine scheduling and monitoring, then moving to scheduling-only tools.
WatchCron
We build WatchCron, so read this entry with that in mind. Cloud Cron runs scheduled HTTP requests (GET, POST, PUT, PATCH, DELETE) on any public URL using standard cron expressions. What sets it apart from every other cloud cron service on this list: it also monitors the results. Every execution gets logged with response code, duration, and response body. If something fails, it retries up to 5 times and then alerts through whichever channels you've configured: email, Slack, Telegram, Discord, Microsoft Teams, SMS, voice calls, PagerDuty, OpsGenie, or webhooks.
Cloud Cron sits inside a full monitoring platform: uptime, SSL, port, and domain checks plus status pages and incident management. When a Cloud Cron job fails, you can check whether the endpoint itself went down.
Pros:
- Scheduling + monitoring + uptime + SSL in one dashboard
- Up to 5 automatic retries on failure
- 19 alert channels including SMS, voice, and PagerDuty
- Permanent execution logs with response bodies
- Team access and incident management included
Cons:
- 60-second maximum timeout (not for long-running scripts)
- No job chaining (run one task after another completes)
- Public URLs only
Free plan: 1 Cloud Cron job + 20 monitoring checks. Paid plans from $7/month (5 jobs) to $49/month (unlimited jobs). No per-execution charges.
EasyCron
EasyCron has been running since roughly 2012, which makes it one of the oldest managed cron services still operating. Instead of charging per job, it uses an EPD (Executions Per Day) model: you buy a pool of daily executions, and how many jobs you can run depends on their frequency. One job every minute uses 1,440 EPD. One job per hour uses 24. It's flexible once you understand the math, but the math isn't obvious. We've written a detailed EasyCron comparison if you want the full breakdown.
Pros:
- Flexible EPD model works well for many low-frequency jobs
- Up to 12-hour timeout on paid plans (longest in the space)
- Regex-based output matching to detect failures in response body
- API access for programmatic job management
Cons:
- No heartbeat monitoring or uptime checks
- EPD pricing confusing (their own site has a calculator)
- Free tier timeout of 5 seconds is almost unusable
- Annual billing only
Free tier: 200 EPD with a 20-minute minimum interval and a 5-second timeout. That's enough for maybe 2 jobs running every 20 minutes. Paid plans start at $24/year (8,000 EPD) with 1-minute intervals.
FastCron
FastCron (formerly SetCronJob, rebranded in 2023) has been around since 2009. The free tier stands out: 15 jobs with 5-minute minimum intervals. That's the most generous free job count on this list. There's a WordPress plugin for one-click setup, and the UI is straightforward: paste a URL, pick a schedule, save. Our FastCron comparison covers the technical details.
Pros:
- 15 free jobs (most generous free scheduler tier)
- WordPress plugin for one-click setup
- Per-job timezone with DST handling
- Slack, Discord, Telegram alerts
- Unlimited team members on paid plans
Cons:
- Free tier timeout is 15 seconds
- Must log in every 90 days to keep free account active
- No execution monitoring (no response time tracking or failure trending)
Free tier: 15 jobs, 5-minute intervals. Paid plans start at $6/month. Starter keeps 15 jobs but drops the minimum interval to 30 seconds and extends the timeout to 1 hour. Pro ($20/month) gives you 80 jobs, Business ($50/month) up to 1,000.
cron-job.org
Eighteen years of running cron jobs for free. cron-job.org is a community project that lets you create unlimited jobs with 1-minute intervals at no cost. No paid tier, no premium upsell. For hobby projects, student work, or anything non-critical, it's hard to argue with the price. We covered the trade-offs in our cron-job.org comparison and the alternatives roundup.
Pros:
- Truly unlimited free jobs at 1-minute intervals
- REST API
- MFA with YubiKey support
- Status badges for embedding
- 18 years of operation
Cons:
- No reliability guarantees or SLA
- 30-second timeout
- 2-day history retention (50 records max)
- Email-only alerts
- No failure retries
- Jobs auto-disable after 25 consecutive failures
Google Cloud Scheduler
Google Cloud Scheduler is a cron service for teams already living inside GCP. It fires HTTP requests, publishes Pub/Sub messages, and triggers App Engine routes on cron expressions. The pricing is clean: $0.10 per job per month after 3 free. See our Google Cloud Scheduler comparison for setup details.
Pros:
- 99.5% SLA backed by Google
- Pub/Sub and App Engine targets
- IAM-based auth (OIDC/OAuth)
- Terraform support
- Configurable retries with exponential backoff
- 30-minute timeout
Cons:
- Requires GCP account with billing (credit card mandatory)
- No execution logs without Cloud Logging
- No built-in alerts without Cloud Monitoring
- Overkill for simple "hit this URL every hour"
Crontap
Crontap straddles scheduling and monitoring. It runs cron jobs but also offers heartbeat checks (dead man's switch) and uptime monitoring, all sharing the same item quota. Plain English scheduling ("every weekday at 09:30") sits alongside standard cron syntax. Slack, Discord, and Telegram alerts come built in. We covered it in the Crontap comparison.
Pros:
- Scheduling + monitoring in one tool at a low entry price
- Natural language scheduling
- Custom retry policies on paid plans
Cons:
- Combined quota (every uptime check eats into your schedule count)
- Relatively new, smaller user base
- 2-item free tier is tight
Free tier: 2 combined items (schedules + monitors) with a 1-hour minimum interval. Pro starts at $2.99/month for 3 items with 1-minute intervals. Scales to $159.99/month for 1,000 items.
CronJobPro
CronJobPro launched recently with a modern take on the category. 5 free jobs at 15-minute intervals, multi-channel notifications from day one, and team collaboration with role-based access.
Pros:
- Clean UI with team roles
- Reasonable free tier (5 jobs)
- Slack, Discord, webhook alerts
- API access
Cons:
- New service with limited track record
- 1-minute timeout on free tier
- Community and documentation still growing
Free tier: 5 jobs, 15-minute intervals. Paid plans start at €3.99/month (25 jobs, 1-minute intervals, 7-day log retention) and scale to enterprise tiers with 10,000+ jobs.
cronhost
cronhost keeps it minimal. No frills, no surprises.
Pros:
- Free retries that don't count toward run limits
- Multi-channel alerts (email, Slack, Discord, Telegram)
- Simple pricing without per-execution math
- Unlimited schedules on Pro tier ($19/month)
Cons:
- 30-minute minimum on free tier
- Monthly run limits could surprise you at high frequency
- Smaller service with less market presence
Free tier: 3 schedules with 5,000 monthly runs, 30-minute minimum interval, and 7-day history. Paid plans start at $5/month (5 schedules, 50,000 runs, 1-minute interval). Pro at $19/month gives unlimited schedules with 500,000 monthly runs.
Runhooks
Runhooks targets developers building production workflows.
Pros:
- Granular retry configuration (exponential backoff, up to 10 attempts)
- 99.9% SLA target
- 30-day log retention
Cons:
- Most expensive non-enterprise option ($19/month for 25 jobs)
- Email and webhook alerts only (no Slack or Telegram)
- Limited free tier (10 jobs, 2,000 monthly runs)
Free tier: 10 jobs with 2,000 monthly runs and 30-day log retention. Paid plans: $19/month (25 jobs, 20,000 runs), $59 (100 jobs), $129 (500 jobs).
Cronless
Cronless is as stripped-down as it gets.
Pros:
- Cheap annual pricing ($27/year)
- Simple interface
Cons:
- Free tier limited to 2 executions per day
- Minimal feature set
- Basic monitoring only on paid plan
Free tier: 5 jobs that can run twice daily. Pro ($27/year) unlocks unlimited jobs at up to 2 executions per minute and adds basic website monitoring. If you need a URL called once a day and nothing else, it works. For anything more demanding, you'll outgrow it quickly.
What about Cronhub?
If you're here because Cronhub shut down: yes, it's gone. The service closed completely on June 30, 2026, after announcing its wind-down in March. All user data was deleted. Cronhub offered both scheduling and heartbeat monitoring, making its exit a real gap for users who relied on both. If that was you, the closest replacements that combine scheduling and monitoring are WatchCron, Crontap, and CronJobPro.
Scheduling alone vs scheduling with monitoring
Look, most online cron job services on this list do one thing: fire an HTTP request on a schedule. And for a lot of use cases, that's genuinely enough. If your script processes three orders and takes 2 seconds, a fire-and-forget scheduler handles it fine.
But what happens when things break? Your endpoint starts timing out. The response body says "database connection failed" but the HTTP status is still 200. The SSL certificate expires and the scheduler can't reach your URL anymore. Does a pure scheduling service catch any of that? No. It just keeps firing requests and logging status codes.
The gap between "the request was sent" and "the job actually succeeded" is where most cron failures hide. If your scheduled tasks are important enough to pay for a service, they're important enough to know whether they worked.
That's the argument for combining scheduling with monitoring. WatchCron's Cloud Cron captures response bodies, tracks response time trends, and fires alerts through 19 channels when something goes wrong. Crontap adds heartbeat checks and uptime monitoring alongside scheduling. CronJobPro includes team roles and webhook alerts with log retention. For everything else on this list, you'll need a separate monitoring tool to watch the jobs the scheduler is running.
If you already use a monitoring platform for your infrastructure, adding a separate cron scheduler is fine. You'll catch failures through your existing stack. If you're starting fresh and need both scheduling and observability, a combined tool saves you from managing two subscriptions, two dashboards, and two sets of alert rules.
How to pick the right service
Every online cron job service on this list fits a different scenario. Here's how to narrow it down.
Budget is zero: cron-job.org is the most generous free cron job service: unlimited jobs with no account expiry. FastCron's 15 free jobs offer better timeout and multi-channel alerts but require a login every 90 days. WatchCron's free plan gives 1 Cloud Cron job plus 20 monitoring checks.
WordPress site on shared hosting: FastCron's WordPress plugin makes setup painless. WatchCron's Cloud Cron for WordPress replaces wp-cron entirely and adds failure alerts.
Running on GCP: Google Cloud Scheduler integrates with Pub/Sub, App Engine, and Cloud Run natively. If you're already in the GCP ecosystem, it's the natural choice at $0.10/job/month.
Need monitoring too: WatchCron combines scheduling with uptime, SSL, port, and domain monitoring plus incident management and status pages.
High-volume scheduling on a budget: EasyCron's EPD model can be surprisingly cost-effective for many low-frequency jobs. FastCron offers 80 jobs at $20/month. Both are scheduling-only. Pair with a monitoring tool if you need visibility.
Long-running scripts: Google Cloud Scheduler (30-minute timeout) and EasyCron (12-hour timeout on paid plans) handle scripts that take minutes to complete. WatchCron and cron-job.org are limited to 60 and 30 seconds respectively.
Cheapest paid option at any scale: Check the pricing table above. Google Cloud Scheduler wins at high volume ($0.10/job). FastCron and cronhost flatten at higher tiers. EasyCron's EPD model favors infrequent jobs.
Need specifically a cron-job.org replacement? See our dedicated cron-job.org alternatives comparison. Or test any cron expression with our free cron job calculator.
One Cloud Cron job and 20 monitoring checks on the free plan. No credit card required.
Frequently asked
An online cron job service sends HTTP requests to your URLs on a schedule, replacing server-side crontab. You provide the URL, choose the timing (cron expression or interval), and the service handles execution from its own servers. Useful when your hosting doesn't support cron, or when you want scheduling independent of your server's uptime.
cron-job.org is a free community project with no SLA or uptime guarantee. It works well for non-critical tasks, but job execution can delay during peak hours and the 30-second timeout limits what scripts can run. For production workloads, a paid service with reliability guarantees is safer.
Cronhub announced its shutdown in March 2026 and closed completely on June 30, 2026. All user data was deleted. The service offered both scheduling and heartbeat monitoring. Alternatives that combine scheduling and monitoring include WatchCron, Crontap, and CronJobPro.
cron-job.org offers unlimited free jobs at 1-minute intervals but with email-only alerts and no SLA. FastCron gives 15 free jobs with Slack/Discord/Telegram alerts but a 15-second timeout. WatchCron's free plan includes 1 Cloud Cron job plus 20 monitoring checks with multi-channel alerts. The best choice depends on whether you need reliability guarantees or just basic scheduling.
For HTTP-based tasks (calling URLs on a schedule), yes. Online cron services work independently of your server, so they keep running even if your server restarts. They can't run shell commands directly, only trigger URLs. For shell-based cron jobs, you'd need to wrap them in an HTTP endpoint or use heartbeat monitoring to verify they ran.
Cron scheduling services (EasyCron, FastCron, cron-job.org) execute HTTP requests on a schedule. Cron monitoring tools (Cronitor, Healthchecks.io) watch whether jobs you run elsewhere completed on time via heartbeat pings. Some platforms like WatchCron offer both: Cloud Cron runs your scheduled HTTP requests while cron job monitoring tracks heartbeats from server-side scripts.
Yes. WordPress uses wp-cron.php for scheduled tasks, but it only runs when someone visits your site. An online cron service can call wp-cron.php on a fixed schedule (typically every 1-5 minutes) to ensure tasks like scheduled posts, plugin updates, and backups run on time regardless of traffic.
Most services let you set timezones per job. EasyCron and FastCron both support per-job timezone selection. cron-job.org uses your account timezone for all jobs. WatchCron lets you pick a timezone when creating each Cloud Cron job. If you have jobs targeting servers in different regions, per-job timezone support avoids manual offset math.
It depends on the service. EasyCron and WatchCron check HTTP status codes and can alert you on non-2xx responses. WatchCron also captures response bodies and supports keyword validation, so you can verify the output contains expected text. FastCron retries failed requests automatically. cron-job.org sends email on failure but doesn't retry. For critical jobs, choose a service that combines retries with multi-channel alerts.
Google Cloud Scheduler is the cheapest at scale if you're already on GCP: 3 free jobs, then $0.10 per job per month regardless of execution frequency. For 100 jobs, that's $10/month. EasyCron charges $24.99/month for 200 jobs on its Standard plan. FastCron offers unlimited jobs for $15/month on its Business tier. WatchCron starts at $7/month for 75 checks including monitoring.
Google Cloud Scheduler and AWS EventBridge Scheduler are cloud-native options, but they require a GCP or AWS account and familiarity with IAM, service accounts, and cloud console workflows. Standalone services like EasyCron, FastCron, and WatchCron have simpler web interfaces that don't require cloud platform experience. If you already use GCP or AWS, the native schedulers integrate well with your existing infrastructure. Otherwise, a standalone service gets you running faster.