Coming soon

Cron Jobs aren't live yet — we're finishing the runtime and the dashboard. Sign up and we'll ping you the moment it ships.

Compute

Cron Jobs

Run scheduled tasks automatically. Set a schedule, we run your code — with logs and retries built in.

Up to 2 vCPU

CPU

Up to 512 MB

Memory

Up to 1 hour

Timeout

Every minute

Min Interval

30 days

History

Configurable

Concurrency

Features

Everything You Need

Built-in tools and capabilities to deploy and manage with confidence.

Cron Schedule Syntax

Use standard Unix cron expressions to define when your jobs run — every minute, hourly, daily, weekly, or any custom interval.

Timezone Support

Schedule jobs in any timezone. Run reports at 9 AM local time or batch processes at midnight in your users' timezone.

Concurrency Policies

Choose Allow, Forbid, or Replace policies to control what happens when a new run is triggered while a previous one is still executing.

Custom Docker Images

Run any script or binary in a Docker container. Bring your own image or use RunSite's built-in runtime images for popular languages.

Execution History

Track every execution with status, duration, and logs. Set retention limits for successful and failed job history.

Failure Alerts

Get notified when a job fails or exceeds its timeout. Configure retry behavior and alert channels for critical tasks.

Execution Lifecycle

Schedule, run, monitor

Every scheduled job follows a predictable lifecycle with built-in safety nets for failures.

1

Schedule Defined

Set a cron expression (e.g. 0 2 * * * for daily at 2 AM) with a timezone. Choose a concurrency policy: Allow, Forbid, or Replace.

2

Container Provisioned

At the scheduled time, RunSite spins up a fresh container from your Docker image with your environment variables and secrets injected.

3

Execution & Timeout Guard

Your script runs inside the container. If it exceeds the timeout limit, the container is terminated and the run is marked as failed with an alert sent.

4

Logs & History Recorded

Exit code, stdout/stderr output, duration, and resource usage are recorded. Failed runs trigger configurable alerts via email or webhook.

Code

Get Started in Minutes

Simple integration with your existing tools and workflows.

# Schedule: 0 2 * * * (daily at 2 AM)
# Timeout: 3600s

#!/bin/bash
pg_dump $DATABASE_URL | gzip > backup.sql.gz
aws s3 cp backup.sql.gz s3://backups/$(date +%F).sql.gz
Use Cases

Built for Your Workload

Common scenarios where this service shines.

Database Maintenance

Schedule backups, cleanup old records, run data migrations, and generate reports on a recurring basis.

Email Digests

Send daily or weekly digest emails, notification summaries, and scheduled marketing campaigns.

Data Sync

Synchronize data between services, pull from external APIs, update caches, and refresh materialized views.

Analytics & Reports

Generate daily analytics snapshots, compute aggregated metrics, and export reports to external systems.

Pricing

Simple, transparent pricing

Pay only for the resources you actually use. Switch between monthly and hourly to see what you'll spend.

Free

Free

  • 1 cron job
  • Hourly minimum interval
  • Basic logging
  • 7-day execution history
Start Free

Starter

€3/mo

  • 5 cron jobs
  • Per-minute scheduling
  • Failure alerts
  • 14-day history
Get Started

Pro

€12/mo

  • Unlimited cron jobs
  • Custom Docker images
  • Extended timeout (1 hour)
  • 30-day history
Get Started
FAQ

Frequently Asked Questions

Common questions about this service.

The default timeout is 3600 seconds (1 hour). On the Business plan, you can request extended timeouts for long-running batch processes. If a job exceeds its timeout, it is terminated and marked as failed.

You can configure a concurrency policy: Allow (run in parallel), Forbid (skip the new run), or Replace (cancel the running job and start a new one). The default policy is Forbid.

Yes. You can trigger any cron job manually from the dashboard at any time, regardless of its schedule. This is useful for testing or running one-off executions.

Failed jobs are logged with their exit code and output. You can configure alert notifications via email or webhook. The execution history shows all past runs with their status, duration, and logs for debugging.

Your app deserves to be online

Free to start. Deploy in under a minute. No credit card needed.