# Run a cron job in the cloud: the options compared

> A cron job is a script that starts on a schedule, does its work and exits. GitHub Actions runs one free on a public repository, but no more often than every 5 minutes and sometimes late; Render bills per second; on Livops a cron service runs every minute if you like, in UTC, for a flat 19 credits a month (19,000 so'm). Here is how they all compare.

Source: https://livops.dev/en/hosting/cron-job-hosting

By Livops team, the people who build and run Livops. Updated 20 November 2026.

A cron job is a script that runs on a schedule — a nightly report, a backup, a price sync every fifteen minutes — and exits when it is done. It does not need a server that is up all day, but it does need something that is up at the right minute, which a laptop is not. This page lists what a scheduled job needs in production, compares the usual places to run one with each provider's own numbers, and ends with the exact `livops.json` for a cron service on Livops.

## What does a cron job need in production?

### A schedule in a time zone you know

Most hosted schedulers read cron in UTC: GitHub Actions does by default[1], Render[3], Railway[6] and Vercel[8] always do. "Every day at 9" in UTC is 14:00 in Tashkent. Write the hour in UTC, or use a scheduler that takes a time zone.

### A job that finishes

A scheduled job starts, works and exits. Railway asks scheduled services to exit as soon as their task is done[6], and Render stops a run after 12 hours[3]. A process that never exits is a worker, not a cron job.

### No overlapping runs

If a run takes longer than the interval, the next one can start on top of it. Platforms handle this differently: Render runs at most one at a time and delays the next scheduled run until the active one finishes[3]; Railway skips the new run[6]. Either way, write the job so that running it twice does no harm.

### Secrets in the environment

API keys and database passwords belong in environment variables, not in the script or the repository.

### Knowing when it failed

A job that fails at 03:00 fails silently unless something keeps its output and its exit status. You want each run's log and a way to run it once by hand.

## The options at a glance

| Option | What it is | Shortest interval | What it costs | What you still maintain |
| --- | --- | --- | --- | --- |
| Livops | A `cron` service; servers in Uzbekistan | 1 minute, UTC | 19 credits (19,000 so'm) a month, flat | Your code |
| GitHub Actions | A workflow on a `schedule` trigger | 5 minutes[1] | Free on public repositories; private ones draw on $12 a month included on GitHub Free, then $0.006 a minute on Linux[2] | The workflow file |
| Render | A cron job service | Not stated in its docs[3] | From $0.00016 a minute (0.5 CPU, 512 MB)[4], at least $1 a month per cron job[3] | Your code |
| Railway | A service with a cron schedule | 5 minutes[6] | Hobby plan: $5 a month, including the same amount of usage[7] | Your code |
| Vercel | A schedule that calls a function | Once a day on Hobby, once a minute on Pro[9] | Hobby free; Pro $20 a month per developer seat[11] | A function that fits the time limit |
| Fly.io | A Machine started on a schedule | Hourly, daily, weekly or monthly[12] | Billed by the second while it runs[13] | Your code, the image |
| PythonAnywhere | Scheduled tasks | Hourly or daily[14] | Developer plan: $10 a month, 20 tasks[14] | Your code |
| A VPS in Uzbekistan | `crontab` on your own machine | 1 minute[15] | 82,000 so'm a month: 1 vCPU, 2 GB, 30 GB HDD (SmartCloud)[16] | The system, updates, logs, alerts |

Other providers' prices are from each provider's own page, read on 20 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.

## Each option

### Livops

A `cron` service runs a command on a schedule and gets no public URL. It sits in the same project as your bot, app and database, and a database's address is written into its variables by itself. The schedule is set in `livops.json` or in the cabinet, read in UTC, and can be as frequent as once a minute. Payment is in so'm through Payme or Click, with no card. The price is flat: a cron job costs what a bot costs, whether it runs once a day for ten seconds or every minute. For a job that runs rarely and briefly, the per-second platforms below, or GitHub Actions, cost less. You do not get root.

### GitHub Actions

The cheapest option for many jobs: standard GitHub-hosted runners are free in public repositories, and a private repository on GitHub Free draws on $12 of included compute a month[2] — about 2,000 minutes on a standard Linux runner at $0.006 a minute[2]. It also has the most caveats. The shortest interval is 5 minutes[1]. Scheduled runs can be delayed under high load, the start of every hour is one such time, and if the load is high enough some queued jobs may be dropped[1]. Schedules run only from the default branch, and in a public repository they are disabled after 60 days without repository activity[1]. It does take a `timezone` with an IANA name[1], which most platforms here do not. Good for housekeeping; risky for anything that must run on the minute.

### Render

A cron job is its own service type, billed by the second of running time, with a minimum monthly charge of $1 per cron job[3]. The smallest size is $0.00016 a minute for 0.5 CPU and 512 MB[4]. Render guarantees at most one active run at a time, and stops a run after 12 hours[3]. Cron jobs cannot use free instances[5]. For short jobs this is hard to beat on price.

### Railway

A Railway service can run on a cron schedule; runs must be at least 5 minutes apart, the schedule is in UTC, and a new run is skipped while the previous one is still running[6]. Railway bills usage by the second on top of the plan; Hobby is $5 a month including that much usage, paid by credit card[7].

### Vercel

A Vercel cron job is an HTTP GET request that Vercel makes to a path of your production deployment, configured in `vercel.json`; the time zone is always UTC[8]. On Hobby a job may run only once a day, and a schedule for 01:00 can fire any time between 01:00 and 01:59; Pro runs them to the minute[9]. The work is a Vercel Function, so it inherits the function limits — at most 300 seconds on Hobby and 800 on Pro[10]. Vercel now calls Cron Jobs a legacy feature, to be migrated to its newer Schedules[9]. A fit for a job that is already an endpoint of a Vercel app.

### Fly.io

`fly machine run --schedule` starts a Machine at hourly, daily, weekly or monthly intervals[12], and Machines are billed by the second while they run[13]. Cheap for a daily job; no use for one that runs every five minutes. A card is needed after the trial[13].

### PythonAnywhere

The Developer plan, $10 a month, includes 20 scheduled tasks that run hourly or daily[14]. The free Beginner account has none[14].

### A VPS

`crontab` is the original: five fields from the minute up, plus shortcuts such as `@daily` and `@reboot`, and `CRON_TZ` to write the times in another zone[15]. Output is mailed to the crontab's owner unless `MAILTO` says otherwise[15] — which, on a machine with no mail set up, means nobody sees it. The cheapest 2 GB machine at SmartCloud is 82,000 so'm a month[16]. A VPS is the cheapest per job once you have many, and the most work: the system, its updates, the logs and the alerts are yours.

## A cron service or a scheduler inside your app?

There are two ways to run something at 09:00. A **cron service** starts a fresh process on schedule and nothing runs between runs; a crash in one run does not affect the next. A **scheduler inside an always-on process** — APScheduler in a Python bot, `node-cron` in a Node app — costs nothing extra if that process exists anyway, but its jobs stop when the process does, and a deploy at 08:59 can skip 09:00.

On Livops both work. A scheduler in your bot or worker reads the container's clock, which is UTC; add `TZ=Asia/Tashkent` under **Variables**, or name the zone in the code:

```python
from apscheduler.schedulers.asyncio import AsyncIOScheduler

scheduler = AsyncIOScheduler(timezone="Asia/Tashkent")
scheduler.add_job(send_report, "cron", hour=9, minute=0)  # 09:00 in Tashkent
scheduler.start()
```

`TZ` changes only the clock your code sees. The `schedule` of a `cron` service is always read in UTC.

## Where can you run a cron job for free?

- **Livops** has no free tier for cron jobs, bots or apps. On an account that has not paid yet, the first paid app runs for 15 minutes on a zero balance, once; static sites are free.
- **GitHub Actions** is free on standard runners in public repositories; a private repository on GitHub Free gets $12 of compute a month[2], with the 5-minute minimum and the delays above[1].
- **Vercel** Hobby is free[11], with one run a day, timed to within the hour[9].
- **Railway**'s Free plan includes $1 of usage a month; a trial gives $5 of credit for 30 days with no card[7].
- **Fly.io** has no free tier, but waives a personal organization's bill under $5 a month[13].
- **Render** cron jobs cannot use free instances[5].
- **PythonAnywhere**'s free account has no scheduled tasks[14].

## Cron jobs on Livops

1. Put `livops.json` in the repository root before you create the project — the type is taken from the file when the project is created, and changed in the project's settings after that:

   ```json
   {
     "kind": "cron",
     "start": ".venv/bin/python job.py",
     "schedule": "0 4 * * *"
   }
   ```

   That runs `job.py` every day at 04:00 UTC, which is 09:00 in Tashkent. For Node, `"start": "node job.js"`. A cron service requires a `start` command.

2. In the cabinet, create the project from the GitHub repository, or upload the folder or a `.zip`. Put API keys under **Variables**, marked as secret where they are secrets.
3. Deploy. Every `git push` to the branch deploys again; if the build fails, the running version is left alone.

The schedule is standard five-field cron, `minute hour day month weekday`:

| Expression | When |
| --- | --- |
| `*/15 * * * *` | every 15 minutes |
| `0 * * * *` | at the start of every hour |
| `30 4 * * *` | every day at 04:30 UTC |
| `0 9 * * 1-5` | weekdays at 09:00 UTC |
| `@daily` | every day at midnight UTC |

- `*`, lists (`1,15`), ranges (`1-5`) and steps (`*/10`) work, and so do `@yearly`, `@annually`, `@monthly`, `@weekly`, `@daily`, `@midnight` and `@hourly`. Sunday is `0` or `7`.
- The smallest interval is 1 minute. A seconds field, month and day names (`JAN`, `MON`), `L` and `#` are not supported.
- **The time zone is UTC.** Tashkent is UTC+5: for 09:00 in Tashkent, write `0 4 * * *`.
- You can also set the schedule in the cabinet. While `livops.json` names a schedule, the file wins on every deploy; take it out of the file and the cabinet's value is back.
- A database added to the project writes its address — `DATABASE_URL`, `REDIS_URL` and the like — into every service in the environment, the cron job included.
- Over [MCP](https://livops.dev/en/docs/mcp), `list_cron_runs` shows the run history and `run_cron` runs the saved command once, so you can test the job without waiting for the schedule. The [assistant](https://livops.dev/en/docs/assistant) can set the schedule for you.

A cron service costs what a bot costs: **19 credits a month (19,000 so'm)**, whatever its schedule. One credit is 1,000 so'm, and bought credits never expire. See [Pricing](https://livops.dev/en/docs/pricing) for plans, and [Cron and workers](https://livops.dev/en/docs/cron-workers) for the full reference.

## Questions

**What is the cheapest way to run a cron job?**

For a light job in a public repository, GitHub Actions, where standard runners are free. For a private one, GitHub's free plan includes a monthly allowance, and Render bills a cron job per second with a 1 dollar monthly minimum. Livops charges a flat monthly price, which is better value the more often and the longer the job runs.

**How often can a cron job run on Livops?**

Every minute at most. The schedule is standard five-field cron with lists, ranges, steps and shortcuts like @daily and @hourly. There is no seconds field, and month and day names such as JAN or MON are not supported.

**Which time zone does a Livops cron schedule use?**

UTC, always. Tashkent is UTC+5, so 09:00 in Tashkent is 0 4 * * *. Setting TZ=Asia/Tashkent changes the clock your code sees, not the schedule.

**Where do I set the schedule on Livops?**

In livops.json, as the schedule field, or in the cabinet. While the file names a schedule, the file wins on every deploy; take it out of the file and the cabinet's value is back.

**Can my cron job use the project's database?**

Yes. A database added to the project writes its address, such as DATABASE_URL, into every service in the environment, the cron job included.

**Is there a free tier for cron jobs on Livops?**

No. Static sites are free; a cron job, like a bot or an app, is paid, at 19 credits a month (19,000 so'm). Credits are bought in so'm through Payme or Click, with no card.

**Who wrote this comparison?**

The Livops team. Every price and limit of another provider on this page links to that provider's own page, with the day we read it.

## Sources

1. [GitHub Docs — Events that trigger workflows (schedule)](https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows). Checked 20 November 2026.
2. [GitHub Docs — GitHub Actions billing](https://docs.github.com/en/billing/concepts/product-billing/github-actions). Checked 20 November 2026.
3. [Render — Cron jobs](https://render.com/docs/cronjobs). Checked 20 November 2026.
4. [Render — Pricing](https://render.com/pricing). Checked 20 November 2026.
5. [Render — Deploy for free](https://render.com/docs/free). Checked 20 November 2026.
6. [Railway — Cron jobs](https://docs.railway.com/reference/cron-jobs). Checked 20 November 2026.
7. [Railway — Pricing](https://railway.com/pricing). Checked 20 November 2026.
8. [Vercel — Cron jobs](https://vercel.com/docs/cron-jobs). Checked 20 November 2026.
9. [Vercel — Cron jobs usage and pricing](https://vercel.com/docs/cron-jobs/usage-and-pricing). Checked 20 November 2026.
10. [Vercel — Functions limits](https://vercel.com/docs/functions/limitations). Checked 20 November 2026.
11. [Vercel — Pricing](https://vercel.com/pricing). Checked 20 November 2026.
12. [Fly.io — fly machine run](https://docs.fly.io/flyctl/machine-run). Checked 20 November 2026.
13. [Fly.io — Pricing](https://docs.fly.io/about/pricing). Checked 20 November 2026.
14. [PythonAnywhere — Pricing](https://www.pythonanywhere.com/pricing/). Checked 20 November 2026.
15. [Ubuntu manpages — crontab(5)](https://manpages.ubuntu.com/manpages/noble/man5/crontab.5.html). Checked 20 November 2026.
16. [SmartCloud — VDS plans](https://smartcloud.uz/cloud-services/vds/). Checked 20 November 2026.
