Cron without a server, and without a URL to keep alive
cron-job.org calls a URL on a timetable, so the code still has to live on a server somewhere. A crontab on a VPS runs the code, but then the server is yours to patch and watch. ClickRuntime runs the script itself, on a schedule, with logs, state and failure alerts.
Host an endpoint just so a pinger can call ithandledPatch and reboot a VPShandledRedirect cron output to a log nobody readshandledFind out a job died weeks agohandled
Why people move cron jobs to ClickRuntime
Code and schedule together
No endpoint to host for a pinger to call, and no server to keep running for crontab. The script runs on our servers.
You hear about failures
Every run is logged with output and errors, and you get an email when a run fails.
State built in
Each automation remembers what it saw last time, so it acts only on new items. No files on disk.
Built from the assistant you already use
Ask in ChatGPT, Claude, Cursor or any MCP client. It writes the automation, tests it and fixes it.
Keys out of the code
API keys are saved in the ClickRuntime dashboard and masked in logs, not in a .env on a server.
Webhooks too
The same automation can have a trigger link, with signature checks for Stripe, GitHub and others.
A 14-step workflow becomes one sentence
Workflow builders make you place every trigger, filter, branch and formatter yourself, then fix it when one breaks. Here you describe the result and your assistant writes the code.
- 01 Shopify trigger
- 02 Filter > $500
- 03 CRM: find
- 04 Router
- 05 Path A: new
- 06 Path B: existing
- 07 Formatter
- 08 AI: summarise
- 09 Text parserfailed
- 10 Slack: post
- 11 CRM: add note
- 12 Error handler
- 13 Set variable
- 14 Delay 2 min
“When a Shopify order over $500 comes in, check the customer in HubSpot. If they're new, post to #sales with an AI summary of the order. Otherwise add a note to their contact.”
Here's the automation. It runs on each new order.
- When
- Shopify · new order (webhook)
- Uses
- Shopify, HubSpot, Slack and AI
cron-job.org and ClickRuntime compared
| Topic | cron-job.org | ClickRuntime |
|---|---|---|
| What runs | cron-job.org: an HTTP request to your URL. crontab: any command on your server | Your Python script, on our servers |
| Shortest interval | cron-job.org and crontab: 1-minute | Every 5 minutes |
| Time limit | cron-job.org: 30 seconds per request | A time limit per run |
| Hosting | cron-job.org: your endpoint, elsewhere. crontab: your VPS | Nothing to host |
| Failure alerts | cron-job.org: email when a request fails. crontab: set up yourself | Email when a run fails, with the error |
| Logs | cron-job.org: response history. crontab: wherever you redirect output | Run log with output and errors, secrets masked |
| State | Your server's database or files | Built into every automation |
| Cost | cron-job.org is free; a VPS is a monthly bill | 250 runs a month free; paid plans from $9 for 2,000 runs |
cron-job.org or ClickRuntime?
Choose cron-job.org when
- You already have an app with an endpoint that does the work, and just need something to call it on time. cron-job.org is free and does exactly that.
- The job needs your server's local files, a local database, or a 1-minute cadence; ClickRuntime's shortest interval is 5 minutes.
- You need to run shell commands or other programs. ClickRuntime scripts can't start processes.
Choose ClickRuntime when
- The job only calls APIs and you don't want a server or endpoint just for it.
- You want logs, failure alerts and memory between runs without building them.
- Someone without SSH access should be able to change the job.
Move from cron-job.org in five steps
Your assistant does the rewriting, you check the result.
- Step 1List your cron jobsRun crontab -l on the server, or open your cron-job.org jobs. Note what each script or URL does.
- Step 2Ask your assistant to rebuild itConnect ClickRuntime to ChatGPT, Claude or Cursor, paste the crontab lines and scripts and say what should happen. It saves a draft you can read before anything runs.
- Step 3Save your keys in the ClickRuntime dashboardSecrets from your server's .env don't move over. Save each API key as a secret in the ClickRuntime dashboard, or sign in through the app's OAuth. Keys never go into the chat.
- Step 4Test itYour assistant turns the automation on, runs it once or sends a test event, and fixes it until the run succeeds. Run both side by side for a few days if you like.
- Step 5Switch the old one offComment out the crontab line, or disable the cron-job.org job, once the automation has run a few times.
These are the cron jobs on my VPS. Move the ones that only call APIs to ClickRuntime.
- Signups to SlackWeekdays 8:00 · Ready
- Order checkEvery 15 minutes · Ready
- pg_dump backupStays on the server · Needs a key
One job, moved from cron-job.org
“Move my cron job to ClickRuntime: every weekday at 8:00 London time, count signups from our API in the last 24 hours and post the number to #metrics in Slack, with the change from the day before.”
Where each cron-job.org piece goes
| In cron-job.org | In ClickRuntime |
|---|---|
| crontab line or cron-job.org job | Automation with a schedule |
| Server time / job timezone | IANA timezone on the schedule |
| .env file | Secrets saved in the ClickRuntime dashboard |
| Files or SQLite for state | state.get and state.set |
| >> logfile 2>&1 | Run log, kept for every run |
| MAILTO or failure email | Email when a run fails |
Send us your crontab and scripts. We'll help you move it.
Email it with a line about what each one does. A person reads it, tells you how it maps to ClickRuntime, and helps until your automations are running.
Email your crontab and scripts
Leave out API keys and other secrets.
What you can add next
Once the first job is moved, these are the changes people usually ask for next. Each is one message to your assistant, not a new service to set up.
- Memory between runs
Only alert when the order check finds something new since last time
“Change my order check so it remembers which orders it has seen and only emails me about new ones.”
- Trigger links
Replace the 15-minute order check with Shopify's order webhook
“Change my order check to use a trigger link that Shopify calls on orders/create, instead of checking every 15 minutes.”
- Built-in AI
Summarise failed orders' error messages into one line each
“Change my order check so failed orders come with a one-line plain summary of the error.”
- Any app or API
Post the daily numbers to Microsoft Teams through its API
“Add to my signups report: also post the number to our Teams channel.”
- Multi-step logic
Retry a flaky API before giving up
“Change my signups report so if our API fails it tries again twice before failing the run.”
- Schedules
Run the check only in business hours
“Change my order check to run every 15 minutes on weekdays from 8:00 to 20:00 London time only.”
Moving from cron-job.org
Can ClickRuntime run a job once a minute?
No. The shortest interval is every 5 minutes. If a job truly needs a 1-minute cadence, cron-job.org or crontab is the better fit.
Can I run shell commands?
No. Scripts are Python and can't start processes. They call APIs over HTTPS. Jobs like backups with pg_dump should stay on your server.
Can I still use cron-job.org to call my endpoint?
Yes, and that's a fine setup if your app already has the endpoint. ClickRuntime is for when you'd rather not host the code at all.
Do I need to know how to code?
No. You describe what should happen and your AI assistant writes, tests and fixes the Python. You can read every version in the ClickRuntime dashboard.
What does ClickRuntime cost?
The free plan includes 250 runs a month with webhooks, code and AI. Paid plans start at $9 a month for 2,000 runs, with unlimited users. A scheduled check that finds nothing new and sends nothing isn't counted.
Will you help me move my cron jobs?
Yes. Email hello@clickruntime.com with what each cron jobs does, or the cron code or config, and we'll help until it's running. Never send API keys or other secrets.