Use case
Skip Sidekiq and clockwork for simple HTTP triggers.
Hatchbox is a great Rails plus Node deploy platform. For background jobs, Sidekiq and Que are still the right answer. For simple HTTP-triggered cron (run this URL every 5 minutes), an external scheduler is faster to set up than wiring whenever or clockwork.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Sidekiq plus Sidekiq-Cron is overkill for an app that just needs three HTTP triggers a day.
- Whenever-driven crontab on the Hatchbox host is fragile across deploys; the crontab line drifts.
- Multi-app shops on Hatchbox need cross-app scheduling that lives outside any one host.
The fix
How Crontap solves it
Crontap calls your Hatchbox app URL (https://yourapp.6rr52.hatchboxapp.com or your custom domain) on a cron in any IANA timezone. Failures alert to email / webhook (Slack / Discord / Telegram).
*/5 * * * *FAQ
Common questions
- Can I still use Sidekiq for background jobs?
- Yes. Mix freely. Use Sidekiq for queue-based work that needs retries, batches and worker concurrency. Use Crontap for simple HTTP triggers where the work fits in one request.
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Free tier available for slower cadences.
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