Feature Requests

Assign more than one schedule window to a single resource — for example, bring an EC2 instance up from 08:00–09:00 on Monday for a morning sync, then again from 15:00–16:00 Tuesday through Friday for an afternoon batch job. Useful for resources that serve different teams or workloads at different times, without needing to provision separate instances for each window.

Define relationships between resources so they start and stop as a unit. For example, ensure an RDS instance is running before its dependent EC2 starts, and that both are stopped together at the end of the day. Removes the risk of orphaned resources and failed boots in multi-tier environments.

Extend the CLI to scan your AWS account and automatically identify underutilised EC2 instances, RDS databases, ECS services, and NAT Gateways. Get actionable schedule suggestions based on actual usage patterns — so you can go from scan to savings in minutes, without manually hunting for waste.