What would your infrastructure cost on Gameye?

Model your load profile and compare Gameye against Edgegap, Hathora, and AWS — egress included on Gameye.

Infrastructure profile
Peak concurrent players (CCU)
Players per container 10
2200
Container vCPU
Container RAM
Reserved capacity 0%
All on-demandAll reserved
Average CCU as % of peak 30%
10% (events only)80% (always on)
Assumptions
Egress per player 20 KB/s
5 KB/s30 KB/s
Your Gameye cost
—
per month
— containers
— vCPU-hours
— GB egress
— per player
$0
saved vs. Edgegap every month
0% less
Monthly cost comparison
Gameye BM/Cloud/Edge
Edgegap Cloud/Edge
Hathora BM/Cloud
AWS c8a.xlarge Single provider Cloud
★ c8a.xlarge is the closest AWS instance to Gameye's Ryzen 7950X bare metal by clock speed — 4.1 GHz boost, still virtualised
Cost breakdown
ProviderComputeEgressTotal
Gameye5GHz bare metal · egress incl. — Included —
Edgegap$0.069/vCPU-hr · $0.0051/GB-hr RAM · $0.10/GB egress — — —
HathoraSame vCPU rate as Gameye · +$10K/mo fixed · egress charged — — —
AWS c8a.xlargeAMD EPYC 9R14 @ 4.1 GHz ★ closest match — — —
Gameye includes all egress. AWS, Edgegap, and Hathora charge separately — typically $0.09–$0.10/GB. At scale, egress accounts for 30–50% of the total bill. Modelled at 20 KB/s per player against average CCU.

Hathora uses the same per-vCPU rate as Gameye but adds a $10,000/month platform fee and charges egress separately. The Compute column above includes the fixed fee.

AWS c8a.xlarge figures reflect two adjustments. First, a 1.3× performance factor: AWS virtualised instances typically need ~30% more vCPUs to deliver equivalent real-time throughput. Second, instance packing density: the c8a.xlarge has fixed specs (4 vCPU / 8 GB) — when your container's RAM demand constrains how many fit per instance, idle vCPUs are wasted and the effective cost per container rises accordingly.
Get a custom quote
No commitment · typical integration in days