Edgegap

—

Disclaimers

Each game’s resource usage is unique. The following calculator provides a ballpark estimate based on weekly historical data from our platform. It is not expected to be perfectly accurate to your game’s exact traffic.

Games vary in player base over time. Make sure to avoid estimating monthly costs based on your initial peak CCU.

For “month 1” estimates, we suggest investigating comparable games to estimate realistic retention decay in the first month after release.

Games with multiple game modes may require a combination of estimates.

How the Estimate Works

This model is built on Edgegap’s real traffic data across hundreds of games and millions of matches, used to establish what an “average week” of player activity looks like for every minute of that model week. Starting from your expected peak concurrent users, the model applies a usage curve to every minute of a full 7-day week, scaling based on historical time-of-day and day-of-week patterns.

It uses your game’s metrics (vCPU per server and players per session) to calculate how many game servers need to be running at each minute to meet demand, including both ongoing sessions and new ones spinning up. Assumptions include a fill rate of 100%, alongside dynamic active session ratio, peak users, and session duration usage variables based on historical data. It applies pricing (compute and egress) across both Cloud and Private Fleet capacity at each minute, producing the cost estimate above using a Cloud rate of $0.00115/vCPU-min, egress rate of $0.10/GB, and Private Fleet hosts at $250/month (13.6 vCPU available) with 5 TB egress included per host.

The full spreadsheet model (over 210,000 formulas across 10,080 data points) has been simplified into a JavaScript implementation for this calculator. Due to rounding in the simplification, estimates here may run ±3% than the full model. Contact us for an estimate outside these assumptions, or if you have further enquiries about how the model functions.