Comparison
Crontap vs GitHub Actions cron
GitHub Actions cron is free and right there in your repo. The catch is in the docs: schedule events can be delayed during high load, sometimes by 15 minutes or more. If you need the run to fire on time, every time, you need a real scheduler.
At a glance
GitHub Actions cron vs Crontap, side by side.
| Dimension | GitHub Actions cron | Crontap |
|---|---|---|
| Cadence floor | 5 minutes | 1 minute (Pro) |
| On-time guarantee | May be delayed during high load (per GitHub docs) | Fires on time |
| Skipped runs | Not retried | Auto-retry on 5xx |
| Cron expression support | Yes (5-field) | Yes (5-field) |
| Per-schedule timezone | UTC only | Yes (any IANA) |
| Failure alerts | Workflow failure email | email / webhook (Slack / Discord / Telegram) |
| Free tier | Unlimited for public repos | Free tier available |
| Cost | Free up to a generous quota | $0 free / $3.25/mo Pro |
How they work
The two approaches in one paragraph each.
GitHub Actions cron
GitHub Actions cron lives in a workflow file inside your repo (.github/workflows/*.yml) under on: schedule: with a cron string. The workflow runs in a fresh Linux runner each fire. Per GitHub's own docs, schedule events 'may be delayed during high load'; community reports describe 15+ minute drift around peak times like top-of-hour.
Crontap
Crontap is an external scheduler. You point it at any HTTP target (an API route, a Cloud Run service, a webhook, even GitHub's repository_dispatch endpoint to fire a workflow on demand) and pick a cadence plus timezone. Crontap fires on time, retries on 5xx, and pages you when a run fails.
Where each side wins
Honest broker, both columns.
GitHub Actions cron wins on
- Free for public repos, generous quota for private.
- Lives next to your code in .github/workflows.
- Full Linux runner available, not just an HTTP target.
- Familiar Actions ecosystem with the same logs and tooling as your CI.
Crontap wins on
- Predictable, on-time fires. GitHub itself acknowledges the drift.
- Auto-retry on 5xx, with logged attempts and a final alert.
- 1-minute cadence on Pro vs GitHub Actions' 5-minute floor.
- Per-schedule IANA timezone.
- Centralized log of every fire across many schedules and many repos.
The math
Cadence and pricing, worked out.
- GitHub Actions cron is free up to your repo's Action minutes quota. Drift is the cost. If your job missing a 9am run is a real problem, that drift becomes the bill.
- Crontap fires on time. If you want every 5 minutes, both can do that on paper. If you want every minute, GitHub Actions cannot (5-minute floor); Crontap Pro can.
Moving from GitHub Actions cron
The migration, in 3 steps.
- Pick the workflow with on: schedule: and a cron expression.
- Replace the schedule trigger with workflow_dispatch: and add an HTTP endpoint that calls GitHub's repository_dispatch API, or move the work into a small HTTP service on your own backend.
- Point Crontap at the new HTTP target with whatever auth header you set.
Decision
Which one fits.
Pick GitHub Actions cron if
Drift of 15 minutes is acceptable, the cron fires once a day, and you want the work to live next to your repo with the rest of CI.
Pick Crontap if
The run must happen on time, you need sub-5-minute cadence, per-schedule timezones, or centralized alerts when things break.
Pair both if
Keep CI cron jobs in Actions; move the time-sensitive schedules to Crontap.
FAQ
Crontap vs GitHub Actions cron, in detail.
- How much can GitHub Actions cron drift?
- GitHub's docs say schedule events 'may be delayed during high load'. Community reports of 15+ minute drift around top-of-hour are common, particularly during US business hours when the Actions queue is busiest.
- Will Crontap re-run a missed run?
- Crontap auto-retries on 5xx responses and alerts you on final failure. It does not re-run runs the platform itself missed (Crontap does not skip; on-time firing is the guarantee).
- Is Crontap more expensive than GitHub Actions cron?
- Crontap is paid above the free tier; for the on-time guarantee, retries, and centralized alerts, that is usually fine. Pro is $3.25/month annual.
- Can I trigger a GitHub Actions workflow from Crontap?
- Yes. Use GitHub's repository_dispatch API as the Crontap target. The workflow you want to run sets on: repository_dispatch: and Crontap fires it on cadence with full retry + alerting on top.
Sources
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s