EC2 instances used for development, staging, or internal tooling are a classic source of avoidable AWS spend - they're billed by the hour whether or not anyone is using them. Runless schedules EC2 instances to stop and start automatically, with the same dashboard and manual-override controls used for ECS services, so both resource types are managed from one place.
Instance-level and bulk scheduling
Schedule an individual instance or apply a schedule across every instance in a region - useful for QA fleets that scale up and down together.
Manual control, no waiting
Need an instance up outside its schedule for a one-off task? Turn it on manually from the dashboard - the schedule resumes automatically afterward.
Savings tied to instance type
Cost tracking uses each instance's actual type and running time, so the dashboard reflects real savings rather than an estimate.
Getting started
The same cross-account role covers both EC2 and ECS - enable only the resource types you actually use, since access is split into per-service grants. See how account linking works, the parallel case for ECS service scheduling, or how Runless compares to AWS's own Instance Scheduler if you're evaluating the free official alternative.