Skip to content
Runtime
Start free

Up to 4× cheapercron and background jobs.

Get started
A 90-second job every hour2 vCPU, 8 GiB, 90 seconds every hour for 30 days, CPU busy the whole run, at each runner's published price, read 22 Oct 2026.How runs are billed →

  • Runtime$1.98

  • Blacksmith$4.32

  • Depot$6.48

  • CircleCI$6.48

  • GitHub Actions$8.64

  • Buildkite$8.64

Runs your command

Next to the namesyou know.

RuntimeBlacksmithDepotCircleCIGitHub Actions
Cost a monthThe same job$1.98$4.32$6.48$6.48$8.64
Billed by the secondNot publishedPartly
Cron in your time zonePartlyPartlyPartly
Retries a failed run itselfPartlyPartlyPartly

Each runner's 2 vCPU price as its own pricing page said it, 22 Oct 2026; schedules, retries and seats as its docs said them, 6 November 2026. How runs are billed

Built to run on time.Nothing to keep up.

  1. 01A fresh sandbox every runStarted for the run, stopped after it; its exit code and output kept.
    • run 41exit 0
    • run 42✓ exit 0
    • run 43at 03:00
  2. 02Your time zoneFive cron fields and an IANA zone, so daylight saving is followed.
    cron
    0 3 * * *
    timeZone
    Europe/Berlin
    next run
    03:00 Berlin
  3. 03Failed runs try againIn a fresh sandbox, up to 5 attempts; one alert, then one on recovery.

    nightly-reportRecovered

    1. Failed
    2. Tried again
    3. ✓ Exit 0
  4. 04Data between runsUp to four volumes; each run reads what the last one wrote.

    /data/report.csv✓ written by run 42

    /data/state.json✓ written by run 42

    a run's own diskgone after it

  5. 05Your agent schedules itCreate, run now, reschedule and read logs over MCP, the SDK or the CLI.

    $ runtime job create report --cron "0 3 * * *" -- python3 report.py

    ✓ scheduled · next 03:00

  6. 06Billed by the second$0.025 an active vCPU-hour, $0.0075 a GiB-hour.

    Billed 90 sGitHub Actions rounds up to 2:00

    0:001:002:00

Keep your jobs.Change one import.

  1. 01Sign inStart free, no card.Start free
  2. 02Change one lineIn app.py.
    Removed: import modalAdded: from withruntime import modal
  3. 03It runsSame code, a smaller bill.✓ Live on Runtime

Ready for production.From your first job.

28,000+

SDK installs last month, on npm and PyPI

  • FirecrackerThe isolation behind AWS Lambda
  • Your own keyEncrypted per organization
  • Secrets stay outsideAdded on the way out
  • SSO and audit logSAML, OIDC and SCIM

Questions.Answered.

Anything else? Ask us

What does a job cost?

Nothing for the job; each run as a sandbox of its size for exactly the time it runs: $0.025 per active vCPU-hour and $0.0075 per GiB-hour. The free usage comes first, and scheduled jobs run on an account that holds credit. More

What if runs are missed?

The job runs once for all of them, then keeps to its schedule. A job never has two runs going at once. More

How long can a run last?

Up to 60 minutes. The timeout is 30 minutes unless you set it; at the timeout the run and every process it started are stopped. More

How do I keep data between runs?

Attach a volume. Each run gets it in turn and reads what the run before it wrote; nothing on a run's own disk carries over. More

What if a run fails?

It can try again in a fresh sandbox, up to 5 attempts, and after the failures you choose one alert goes out by webhook or email; another says when it recovers. More

Your jobs,up to 4× cheaper.

Get started
Get started