Not sure how you did it but I've worked for a company that enabled you to tag resources with operating hours and stuff got shut down outside of the those operating hours - pretty handy way to cut down on usage because most non-live environments don't need everything running 24x7.

This was mostly properly scaling down things that didn’t need to be up all the time (as far as I understand it, I wasn’t part of the effort). We do already have a system that shuts down services when they’re not needed (based on tags, so presumably sort of the same thing).

My client does this. Really nice if you’re on the East coast. Ireland might have a few morning hours where nothing works in test. India has large chunks of time with the same issue. Surprisingly this hasn’t lead them to mock service locally. They are just less productive.

Why not expand the range? The running of the service can’t be more expensive than the devs right?

I agree - you need a dev environment to do your job. That said, I worked at a place where the AWS dev accounts cost hundreds of thousands of dollars a month - I don't know how many employees were outsourced but no one wanted to pay for the extra uptime of the environments for them.