CapabilitiesIdle and waking
Scheduled runs
Start a machine or a job on a schedule, like a cron job, without your own server.
Short answer: 6 of 16 providers offer it fully: Agent 37, Blaxel, Cloudflare Sandbox, Modal, Runtime and Vercel Sandbox. With a catch: Sandboxer and boxd. Checked 29 October 2026.
Who offers it
Part of Idle timers, waking and session limits, which explains why it matters.
Fully: Agent 37, Blaxel, Cloudflare Sandbox, Modal, Runtime and Vercel Sandbox. With a catch: boxd and Sandboxer. Not at all: Boat, Daytona, E2B, InstaBox, Lizard, Morph, Sprites and Tensorlake.
- Agent 37Yes
Each firing wakes the instance, runs the turn, then lets it sleep again.
docs-confirmed “Each firing wakes the instance, runs the turn on its own session, and lets the instance go back to sleep.” Source
Cron, a future time, or a delay; each run is recorded.
docs-confirmed “Schedules run a process inside a sandbox automatically, without you triggering it from your client.” Source
A Workers Cron Trigger starts a container task on a schedule.
docs-confirmed “Run a short container task every two minutes with a Workers [Cron Trigger](/workers/configuration/cron-triggers/).” Source
- ModalYes
Schedules attach to functions, which can then start a sandbox.
docs-confirmed “Modal facilitates this through function schedules.” Source
- RuntimeYes
Each run starts a fresh sandbox, and a run can attach volumes.
docs-confirmed “A job runs a command in a fresh sandbox. It runs once, at a time you choose, or on a cron schedule.” Source
Cron triggers a function, which can then start a sandbox.
docs-confirmed “Cron jobs are time-based scheduling tools used to automate repetitive tasks.” Source
- boxdWith a catch
The catch: A schedule runs inside the machine, so it only fires while that machine is awake.
docs-confirmed “Jobs survive reboots. Everything in the `background` or `retrying` state is started again when the machine boots.” Source
- SandboxerWith a catch
The catch: A cron or timer runs inside the machine, so it never fires while the machine is stopped or paused.
docs-confirmed “Neither fires while the sandbox is stopped or idle-paused.” Source
- BoatNo
No scheduler; a cron inside the machine only runs while it is running.
inferred “For example, save one each day from cron:” Source
- DaytonaNo
No scheduler that starts sandboxes; the only scheduling is where a sandbox is placed.
inferred “Every Daytona sandbox runs in a **region**” Source
- E2BNo
No scheduler for starting sandboxes or jobs.
inferred “Persistent storage that exists independently of sandboxes and can be mounted across multiple sandboxes.” Source
- InstaBoxNo
No scheduler for starting machines or jobs.
inferred “| **Operation** | A change to a machine (create, start, stop, pause, resume, delete).” Source
- LizardNo
No scheduler that starts sandboxes.
inferred “Create a sandbox, run commands, then call `kill`.” Source
- MorphNo
No scheduler for starting machines or jobs.
inferred “Each instance runs from a saved snapshot.” Source
- SpritesNo
No scheduler that starts a Sprite.
inferred “A Sprite is not a server that runs until you turn it off.” Source
No cron scheduler; an application is called over HTTP.
inferred “Each one of them will be assigned a unique HTTP entry point based on the name of the Python function.” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.