10 Best Online Cron Job Services in 2026

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 — and honestly, this part matters more than the list itself — here's what to pay attention to:

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 — so you see the full picture.

The 10 services, compared

10 online cron services reviewed

Starting with the services that combine scheduling and monitoring, then moving to scheduling-only tools.

WatchCron — scheduling with built-in monitoring

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.

Free plan: 3 Cloud Cron jobs + 20 monitoring checks. Paid plans from $7/month (15 jobs) to $49/month (200 jobs). No per-execution charges.

Limitations: 60-second maximum timeout — if your script needs minutes to complete, this isn't the right fit. No job chaining (running one task after another completes). Public URLs only.

Best for: Teams that want scheduling and monitoring in one tool without stitching together separate services.

EasyCron — the execution-per-day model

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.

The free tier gives you 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 and up to 12-hour timeouts.

Strengths: Flexible execution model for diverse schedules, long timeouts on paid plans, regex-based output matching to detect failures in response body, API access.

Weaknesses: No heartbeat monitoring, no uptime checks — scheduling only. The EPD model confuses people (their own site has a calculator to help). Free tier timeout of 5 seconds is almost unusable. Annual billing only.

FastCron — generous free tier, WordPress focus

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.

Paid plans start at $6/month. The Starter tier keeps the same 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) gives you up to 1,000.

Strengths: WordPress plugin, 15 free jobs, per-job timezone with DST handling, multi-channel notifications (Slack, Discord, Telegram), unlimited team members on paid plans.

Weaknesses: Free tier timeout is 15 seconds. Must log in every 90 days to keep free account active. No execution monitoring — you see if the request was sent, but there's no response time tracking or failure trending.

cron-job.org — free, community-run, and limited

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 — just a donation button. 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.

The catch is what you give up for free. Timeout is 30 seconds — which you'll hit faster than you expect. Execution history shows 50 records, kept for just 2 days. Notifications are email-only. There are no retries, no Slack alerts, no execution time charts. And there's no SLA — the service runs on donated infrastructure. During peak hours, job execution can delay.

Strengths: Truly unlimited free jobs at 1-minute intervals. REST API. MFA with YubiKey support. Status badges for embedding.

Weaknesses: No reliability guarantees. 30-second timeout. 2-day history retention. Email-only alerts. No failure retries. Not recommended for production workloads you can't afford to lose.

Google Cloud Scheduler — infrastructure-grade, infrastructure-complex

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 — all 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.

The trade-off is that you're buying into GCP. Setting up your first job means creating a project, enabling billing, activating the API, configuring IAM roles, and then creating the job. No built-in execution dashboard, no failure alerts without Cloud Monitoring, no team-friendly UI outside the GCP console.

Strengths: 99.5% SLA, Pub/Sub and App Engine targets, IAM-based auth (OIDC/OAuth), Terraform support, configurable retries with exponential backoff, 30-minute timeout.

Weaknesses: Requires GCP account with billing (credit card mandatory). No execution logs without Cloud Logging. No built-in alerts — requires separate Cloud Monitoring setup. Overkill for simple "hit this URL every hour."

Crontap — scheduling meets observability

Crontap is trying to straddle scheduling and monitoring at the same time. 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.

The free tier gives you 2 combined items (schedules + monitors) with a 1-hour minimum interval. Pro starts at $2.99/month for 3 items with 1-minute intervals. The pricing scales to Ultra tiers — $19.99/month for 50 items, up to $159.99/month for 1,000.

Strengths: Scheduling + monitoring in one tool at a low entry price. Natural language scheduling. Custom retry policies on paid plans.

Weaknesses: Combined quota means every uptime check or heartbeat eats into your schedule count. Relatively new, smaller user base. 2-item free tier is tight.

CronJobPro — newer entrant, team features

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. 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.

Strengths: Clean UI, team roles, reasonable free tier, Slack/Discord/webhook alerts, API access. Priced in EUR.

Weaknesses: New service — limited track record. 1-minute timeout on free tier. Community and documentation are still growing.

cronhost — simple and straightforward

cronhost keeps it minimal. No frills, no surprises. 3 free 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). The Pro tier at $19/month gives unlimited schedules with 500,000 monthly runs.

Strengths: Free retries that don't count toward run limits. Multi-channel alerts (email, Slack, Discord, Telegram). Simple pricing without per-execution math.

Weaknesses: 30-minute free tier minimum. Monthly run limits could surprise you if jobs run frequently. Smaller service with less market presence.

Runhooks — developer-focused, premium pricing

Runhooks targets developers building production workflows. 3 free jobs with 2,000 monthly runs and 30-day log retention. Paid plans start at $19/month (10 jobs, 20,000 runs), jumping to $59 for 30 jobs and $129 for 100. It supports all HTTP methods, custom headers, and exponential backoff with up to 10 retries.

Strengths: Granular retry configuration (exponential backoff, up to 10 attempts). 99.9% SLA target. Long log retention.

Weaknesses: The most expensive non-enterprise option on this list. $19/month for 10 jobs is steep when FastCron offers 15 for $6 and WatchCron gives 15 plus monitoring for $7. Email and webhook alerts only — no Slack or Telegram.

Cronless — bare minimum

Cronless is as stripped-down as it gets. 5 free 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.

Strengths: Cheap annual pricing. Simple interface.

Weaknesses: Free tier limited to 2 executions per day — almost useless for anything running more frequently. Minimal feature set. Basic monitoring only on paid plan.

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.

The question is 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. A pure scheduling service doesn't catch any of that — it just keeps firing requests and logging status codes.

That's the argument for combining scheduling with monitoring. WatchCron's Cloud Cron captures response bodies, tracks response time trends, and fires alerts through 10+ 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 — EasyCron, FastCron, cron-job.org, Google Cloud Scheduler — 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 3 Cloud Cron jobs 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: That said, 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.