Migration Guide
Migrate from Render Cron Jobs
Platform-independent scheduling. Proper alerting. AI diagnostics.
Step by step
List your Render Cron Jobs
In your Render dashboard, navigate to your project and note each Cron Job service: its command, schedule, and Docker image or build command.
Expose cron logic as HTTP endpoints
Add HTTP routes to your Render web service for each cron task.
// Express
app.post('/cron/cleanup', verifySecret, async (req, res) => {
await performCleanup();
res.json({ ok: true });
});Create JustRun jobs
Create a JustRun job for each Render Cron Job: point it at your Render web service URL + cron route, with the same schedule.
Add a shared secret header
In JustRun, add an Authorization or X-Cron-Secret header. Validate it in your route handler to reject unauthorized calls.
Delete Render Cron Job services
Once JustRun jobs are verified, delete the Render Cron Job services to stop incurring their compute costs.
Common questions
Render Cron Jobs are very cheap. Why switch?
Render Cron Jobs have no failure alerting and no retry policies. JustRun adds AI diagnostics, escalation policies, job chains, and a CLI — at $3–7/mo.
What if my cron job needs environment variables?
Your Render web service already has access to your env vars. The HTTP route handler uses them directly — no change needed.