Crons & Jobs

Scheduled work, on demand or on a clock.

Fire a function or a job on a cron expression, or run a one-off command inside your project image - migrations, cleanups, backfills - with your app env vars already in place. Every run keeps its status, timing, and logs.

Start freeHow it works

Free to start, no credit card.

#every night at 02:00
$cron: 0 2 * * * -> fn:nightly-report
>run #128 ok 1.4s
#one-off, right now
$job: python manage.py migrate
>run #129 ok 3.2s (12 migrations)

Cron schedules

Trigger a function or a job on any cron expression. Nightly reports, hourly syncs, weekly cleanups - set it and forget it.

One-off jobs

Run a command inside your project image on demand: database migrations, data backfills, maintenance scripts - with env vars already wired.

Fully logged

Every run records its status, exit code, duration, and output, so you always know what ran and what happened.

How it works.

1

Pick a function or job

A serverless function, or a command in your project image.

2

Schedule or run it

Give it a cron expression, or trigger a one-off job now.

3

It runs with your env

Your app env vars are already in place at run time.

4

Review every run

Status, timing, exit code, and logs are kept for each run.

One connected platform

Pairs well with

Functions

The serverless target most crons fire at.

Containers

Run jobs inside your project image, env wired.

Workers

Schedule an agent to run and report on a cadence.

Common questions

What schedule format do you use?
Standard cron expressions - the same five-field syntax you already know. Nightly at 02:00 is 0 2 * * *. You can also trigger any job manually, right now, without a schedule.
Do scheduled runs see my environment variables?
Yes. A job runs inside your project image with the same env vars as your app, so database URLs, API keys, and config are already in place.
Where do the logs go?
Every run - scheduled or one-off - records its status, exit code, duration, and full output. The history is kept per cron and per job so you can audit what ran.
Can I run database migrations this way?
That is exactly what one-off jobs are for: run python manage.py migrate, a backfill script, or a cleanup command inside your project image on demand.

Try it on your next deploy.

Free to start, no credit card. Connect a repo and you're live in seconds.

Start freeBook a demo