ECS services in development and staging clusters are usually sized to mirror production, then left running continuously even though nobody is hitting them outside working hours. Runless schedules ECS services down (and back up) automatically, and gives you a dashboard to manage schedules across every cluster and region you've connected.
Per-cluster, per-service control
Set schedules at the level that makes sense for your environment - an individual service, or bulk actions across a whole cluster or region.
Least-privilege by design
The onboarding role only needs to list/describe ECS services, update their running state, and configure EventBridge forwarding - scoped per resource type, nothing broader.
Cost visibility per service
Savings are calculated from each service's CPU/memory pricing and actual running time, so you can see which services are worth right-sizing next.
Getting started
Onboarding uses a Quick Start CloudFormation stack that provisions the cross-account role, then account linking happens in the Runless portal - most teams are connected in under 20 minutes. See how account linking works for the step-by-step flow, or read about the parallel case for EC2 instance scheduling. If you're currently running your own EventBridge + Lambda scheduler for ECS, see how that compares to Runless.