Devora Cloud · Blog
Autoscaling by the hour, only for the spike
Devora Cloud · Reviewed on
Autoscaling turns an extra copy on when CPU rises and off when the spike passes. You pay for the hours that copy was on.
Paying a whole month for a second machine because of one afternoon is what autoscaling avoids. The extra copy exists while the spike exists.
The ceiling stays the plan’s. Hobby does not go past 2 copies on. Pro does not go past 3. Enterprise does not go past 5. The protection copy kept off is not part of that count.
What to watch
The project’s CPU and memory, in the dashboard. A site sitting at 0% CPU does not need an extra copy. Resident memory with low CPU is normal: the process is up, it is not saturated.
How to ask the AI
With the token active, ask it to look at the metrics before turning a copy on. The AI should not scale in the dark. If the spike is a code error, another copy repeats the error.
Frequently asked questions
Are autoscaling and load balancing the same bill?
Both charge the extra copy by the hour, while it is on. You turn load balancing on to share traffic. Autoscaling turns on and off with the spike.