Use case
One cron dashboard across your Render services and environments.
Render Cron Jobs are standalone services that run commands from a repo or container, with UTC cron, run history, logs, email/Slack failure alerts, event webhooks, and a $1 monthly minimum. Crontap calls an existing HTTP service and adds IANA timezones, retries, uptime, and heartbeats.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Each Render Cron Job is a separate service and carries at least a $1 monthly minimum charge.
- Render evaluates schedules in UTC rather than a per-job IANA timezone.
- Render does not provide standard automatic retries for Cron Jobs; Workflows retries are a separate product.
- Command execution is a strong native feature, while an external HTTP scheduler requires a reachable route.
The fix
How Crontap solves it
Crontap calls your https://yourapp.onrender.com URL from outside the Render service. Any cadence (every 1 minute on paid plans, every 5 minutes is typical), any IANA timezone, one dashboard for prod and staging side by side. Failures notify connected email, Slack, Discord, or Telegram destinations. Machine webhooks remain under Integrations. For the head-to-head frame, see Crontap vs Render Cron.
*/1 * * * *One concrete pattern from the dataset, archetyped: a Render customer running both a per-minute health-check cron at /crons/minute and a daily aggregate at /crons/day, in two environments (prod in Europe/Madrid and staging in America/Santo_Domingo). Both environments share the schedule shape and the alerting channel; only the URL and the timezone differ. Fast to clone the schedule for a new region, fast to audit when one env falls behind.
Auth is whatever your Render service expects: a bearer token checked in your handler, basic auth, a custom header. Crontap stores arbitrary headers per schedule and sends them on every run. The endpoint stays public-by-DNS but the auth check lives in your code.
FAQ
Common questions
- Can I still use Render Cron alongside Crontap?
- Yes. Mix freely. Keep Render Cron for in-container batch jobs that need to share the same image and config; add Crontap for everything that benefits from being external (cross-env, central dashboard, richer alerting).
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Render Cron also supports minute cadence. Compare execution model, timezone, retries, uptime, and heartbeats rather than claiming a cadence or alerting gap that does not exist.
- How do I get notified if a run fails?
- Choose connected email, Slack, Discord, or Telegram channels under Notifications, or add a machine webhook under Integrations. If the final attempt fails, the payload includes status code, duration, size, error summary, and attempt history.
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