Pegaxy Blaze PvP Horse Racing

Written in collaboration with
Mirai Labs
Key Highlights
Pegaxy Blaze races are short, session-based, and unpredictable in volume. With Edgegap's on-demand deployment model, servers spin up in seconds when a race begins and shut down immediately after. No idle capacity sitting between sessions. No paying for compute that isn't earning its keep.
Mobile games live and die by cost per daily active user. Edgegap's ability to allocate fractional vCPU aligns server resources precisely with the lightweight demands of a mobile racing session, ensuring Mirai Labs isn't over-provisioning compute for an eight-player race that doesn't need it.
The Studio
Mirai Labs is a Web3 gaming company behind one of the earliest breakout blockchain gaming franchises. Pegaxy, originally a play-to-earn horse racing game built on the Polygon blockchain, amassed a massive global player base at its peak and established Mirai Labs as a credible force in Web3 gaming.
Pegaxy Blaze is the studio's evolution of that IP for mobile. A fast-paced, eight-player horse racing game, Blaze brings elemental skills, prestige systems, and competitive leaderboards to a new audience while staying true to the franchise's racing roots.
The Challenge
Mobile F2P is an unforgiving business. Players expect a polished, low-latency experience regardless of whether they're racing from Singapore, São Paulo, or Stockholm. Infrastructure that can't reach them doesn't just hurt the experience, it loses the player.
At the same time, cost per DAU is a metric that determines whether a mobile title is viable. Traditional server fleets charge whether players are racing or not. For a session-based game with variable daily traffic, that model erodes margins fast.
Mirai Labs needed infrastructure that could serve a globally dispersed player base instantly, scale without waste, and price itself around actual usage, not reserved capacity.
The Solution
Edgegap's orchestration is built for exactly this trade-off. Servers deploy on-demand across 615+ locations worldwide at a single universal price to all locations, on demand, without pre-warmed fleets sitting idle. For Pegaxy Blaze, that means a server exists only for the duration of a race.
Three capabilities made the difference:
On-Demand Global Deployment: The moment a match is confirmed, Edgegap's patented decision-making system identifies the optimal server location for the players in that race and deploys within seconds. No regional trade-offs. No selective market launches. Players in cost-prohibitive regions like Asia-Pacific or the Middle East get the same experience as players in North America or Europe.
Fractional vCPU Allocation: Not every game server needs the same compute. Edgegap's platform allows Mirai Labs to right-size resources to the actual demands of a mobile racing session, directly reducing cost per DAU without sacrificing performance. For a free-to-play title, that headroom is the difference between a financially viable game and one with a cloud spend that hurts it profitability.
Usage-Based Pricing: Edgegap charges for real compute usage, not reserved capacity. Pegaxy Blaze pays for races that happen, not for infrastructure waiting around for them.
Conclusion
Multiplayer mobile games face a double constraint that desktop and console titles don't: players expect desktop-quality online performance on hardware tethered to mobile networks, and the F2P model means every server dollar spent is measured against a player base that pays nothing upfront.
Edgegap's on-demand orchestration, fractional vCPU support, and regionless global network give Pegaxy Blaze the infrastructure to compete globally without the cost structure of a game that can afford to waste it.








