---
title: 'How Much Do Idle Dev and Staging Environments Really Cost?'
description: 'Most teams underestimate what they spend on non-production AWS resources. Here is the math, with realistic numbers, and what it adds up to over a year.'
date: '2026-05-06'
readingTime: '5 min read'
---

## The Number Most Teams Do Not Want to Know

If you have ever pulled up AWS Cost Explorer and felt a small wave of nausea, you are not alone. Dev, staging, QA, and demo environments are where most of the money quietly goes, and almost nobody can tell you what they actually cost. The line item is real. The number behind it usually is not in anyone's head.

So let us put it there. What follows is the math with real instance sizes and real prices. This is not about guilt. It is about the number. Once it is on the screen in front of you, the decision makes itself.

## The Hours Math

A week has 168 hours. Now think about when anyone is actually logged into a staging box. Roughly nine to six, Monday through Friday, which is 45 hours. Add another 5 for the occasional late push or a weekend hotfix and you land at about 50 hours of real use.

That leaves 118 hours, near enough 70% of the week, where the environment is up and humming and nobody is anywhere near it. Stretch that across a year and you get 6,136 idle hours per resource. You pay for all of them.

## What a Realistic Non-Production Stack Costs

Here is a deliberately modest non-production setup in `eu-west-1`:

| Resource                 | Type            | Hourly | Monthly    |
| ------------------------ | --------------- | ------ | ---------- |
| Dev app server           | m5.large        | $0.115 | $84        |
| Staging app server       | m5.large        | $0.115 | $84        |
| QA app server            | m5.large        | $0.115 | $84        |
| Dev database             | db.m5.large     | $0.171 | $125       |
| Staging database         | db.m5.large MAZ | $0.342 | $250       |
| Demo environment EC2     | m5.xlarge       | $0.230 | $168       |
| **Monthly total (24/7)** |                 |        | **$795**   |
| **Annual total (24/7)**  |                 |        | **$9,540** |

This is the small version. Plenty of teams run three to five of these. But before scaling anything up, look at what a schedule does to even this one.

## What You Save by Scheduling

Run the same stack only during business hours plus a bit of slack, say 7 AM to 8 PM on weekdays. That is 65 hours a week, roughly 39% of it:

| Resource             | Monthly (24/7) | Monthly (scheduled) | Saved      |
| -------------------- | -------------- | ------------------- | ---------- |
| Dev app server       | $84            | $33                 | $51        |
| Staging app server   | $84            | $33                 | $51        |
| QA app server        | $84            | $33                 | $51        |
| Dev database         | $125           | $49                 | $76        |
| Staging database     | $250           | $98                 | $152       |
| Demo environment EC2 | $168           | $66                 | $102       |
| **Monthly total**    | **$795**       | **$312**            | **$483**   |
| **Annual savings**   |                |                     | **$5,796** |

That is 61% off the non-production bill, and nobody had to change how they work. The environment is there every business hour, and it is there for the late push or the weekend fix. What stops is paying for it at 3 AM on a Tuesday.

## What Storage Still Costs

One honest caveat. EBS volumes and RDS storage keep billing whether the compute is on or off. For the stack above:

- 6 EBS volumes (100 GB gp3 each) = ~$48/month
- RDS allocated storage (200 GB total) = ~$26/month
- Total storage cost: ~$74/month

Scheduling does nothing for that. But the savings come from compute, which is the bulk of the bill, so the percentages above still hold.

## Scaling Up the Math

That was one team running one small stack. Real companies have many.

Take a mid-size shop with five product teams, each on a similar stack. That is around $2,400 a month bleeding out, roughly $28,800 a year. Schedule it and you keep about $17,000 of that annually.

Now a bigger engineering org, 15 teams with multiple environments apiece. The waste runs somewhere between $8,000 and $12,000 a month, call it $96,000 to $144,000 a year. Scheduling brings back $60,000 to $85,000 of it.

None of these are stretch figures. They are what shows up in real audits at companies that have simply never sat down and thought about non-production scheduling.

## The Hidden Costs Beyond AWS

The dollar figure is only the part you can see on an invoice. Idle environments cost in quieter ways too.

There is the engineering attention. Every environment that is up is one more thing that can break, fill a disk, trip a security scan, or page someone at 2 AM. There is the security surface: every running instance is a door someone might try, and a stopped instance is a door that is not there. And there is the low hum of guilt. A team that knows it is burning $10,000/month spends real energy feeling bad about it. A team that has scheduled its environments stops thinking about the whole thing.

## Why Teams Do Not Do This

Most teams already know they are wasting money. The reasons they sit on it are familiar:

- "We will get to it after the current quarter ends."
- "It is on the list, just not at the top."
- "The savings are not big enough to be worth the engineering time."
- "We might need the environment outside business hours."

The third one comes up most, and it is the one that does not survive contact with reality. Setting up scheduling is a job of hours, not weeks, especially with a managed tool. And the "we might need it" worry disappears the moment you give engineers a button to spin the environment back up on demand.

## What to Do This Week

You do not have to schedule everything. Hit your most expensive resources and you capture most of the savings anyway. Give it 30 minutes:

1. Open AWS Cost Explorer.
2. Filter to EC2 and RDS, group by tag (`Environment` or similar).
3. Sort non-production resources by cost. Identify the top five.
4. Schedule those five to stop overnight and on weekends.

That is most of the available savings, for a sliver of the work.

Whether you do it with [ParkMyAWS](https://parkmyaws.com), [AWS Instance Scheduler](https://parkmyaws.com/aws-instance-scheduler-alternative), or a homegrown Lambda matters far less than just doing it. Every month you wait is another month of waste you will not get back.