Here is a number that should make every CTO uncomfortable: 80% of development and staging containers sit idle at any given moment. That is not a guess — it is what we see consistently across the hundreds of organizations we work with.
The Hidden Cost of Always-On
The cloud promised pay-for-what-you-use pricing, but the reality is different. Most teams provision containers for peak load and leave them running 24/7. A typical mid-size engineering organization runs 200-500 containers for development, staging, QA, and demo environments. At an average cost of $50-100/month per container, that is $10,000-50,000/month — and the vast majority of those containers are doing nothing most of the time.
Why Traditional Autoscaling Falls Short
Traditional autoscalers can scale down to one replica, but they cannot scale to zero. There is always at least one instance running, waiting for traffic that may never come. Serverless functions solve this for stateless workloads, but they impose cold start penalties of 1-10 seconds — unacceptable for interactive applications, APIs, and development environments.
The Scale-to-Zero Approach
At NovaPulse, we take a fundamentally different approach. Instead of terminating idle containers and cold-starting new ones, we freeze them at the kernel level using cgroup v2 freezer. A frozen container uses exactly 0% CPU and costs nothing to run — but its memory state is preserved. When a request arrives, the container thaws in 11 milliseconds on average. No cold start. No re-initialization. No lost state.
The Numbers
Our customers typically see 85-94% cost reduction on non-production environments. A company running 300 containers at $75/month each ($22,500/month) might see their bill drop to $1,350-3,375/month — savings of $19,000-21,000 per month. Over a year, that is over $230,000 returned to the engineering budget. Scale-to-zero is not just a technical optimization. It is an economic imperative.