Dragon Sky FinOps: 62% lower infrastructure cost.
Linked revenue metrics with infrastructure cost and found unused resources automatically every day with Python, cutting infrastructure cost by up to 62%.
Problem
Infrastructure cost was high relative to game revenue, which hurt profitability.
Approach
Revenue metrics and infrastructure cost were monitored together. Python found unused resources across every cloud automatically each day.
Implementation
- Azure
- Python
- Billing monitoring
Scale · 10 servers · 5 databases
Dragon Sky had a profitability problem: infrastructure cost was high relative to revenue.
Revenue metrics and infrastructure cost are monitored together.
Python finds unused resources automatically every day.
As unused resources are removed, the cost line comes down.
Infrastructure cost fell by up to 62%.
Read every step
- Dragon Sky had a profitability problem: infrastructure cost was high relative to revenue.
- Revenue metrics and infrastructure cost are monitored together.
- Python finds unused resources automatically every day.
- As unused resources are removed, the cost line comes down.
- Infrastructure cost fell by up to 62%.
Result
Infrastructure cost fell by up to 62%.
- -62%
- Maximum infrastructure cost reduction
- 10
- Servers
- 5
- Databases
MEASUREMENT Lower is better
- Condition
- Maximum infrastructure cost reduction
- Scope
- Relative value, before the change = 100
What I learned
I learned that cost is easier to judge against revenue than as an amount on its own. Putting infrastructure cost next to revenue metrics made it clear which resources affect profitability and what to cut first. Cost leaks also do not end after one cleanup, so detecting unused resources every day in Python, instead of someone looking now and then, was what kept the savings in place. Detection alone saves nothing until resources are actually removed, which showed me that the next step in cost management is a flow that takes each finding quickly to cleanup approval and action.
Up to -62% — Infrastructure cost