Schedule runs with clear launch rules and hard limits
Built for teams that want automation they can explain to engineering and finance in one sentence.
What launches, and when
Each schedule binds to template, GPU profile, and cron trigger. Pulserun launches exactly that workload at the configured times.
Runtime limit
Set max duration per run. Jobs are terminated automatically at limit to prevent runaway overnight spend.
Cost limit
Set max cost per run. If projected cost crosses limit, Pulserun stops the job and records the event for auditability.
Example outcome: budget control
Nightly fine-tuning with a 3-hour and $6 cap guarantees bounded cost while still running every night automatically.
Example outcome: reliability
Cron-triggered launches remove manual start risk, so batch windows are met consistently even across distributed teams.
Want policy to coordinate schedules, migration, and recovery?
See Autopilot policy model →