What tech stack does Epic Games use?

Epic runs Fortnite on tens of thousands of AWS EC2 instances powered by Graviton processors, scaling dynamically to support 110 million monthly active users and spikes of up to 44.7 million concurrent players during major live events. The entire worldwide game-server fleet, backend APIs, matchmaking, and player data services live on AWS — a commitment Epic made in 2018 and has deepened continuously since. In a recent expansion, Epic committed to using AWS Local Zones specifically for Fortnite's North American competitive and tournament server infrastructure, reducing latency for high-stakes competitive play.

Epic uses AWS Kubernetes (EKS) for containerized workload management, having kicked off a cloud-efficiency initiative in 2022 to digitally transform Fortnite's backend. The company stores petabytes of player telemetry, game-state data, and behavioral analytics in an AWS-native data lake, using AWS analytics services to inform live-service decisions — when to deploy limited-time modes, adjust Battle Pass content pacing, or time IP crossover events. AWS CloudFront serves as the CDN layer for both game asset delivery and the Epic Games Store web properties globally.

For game engine compilation and large-scale render pipelines, Epic uses AWS Thinkbox Deadline alongside its own Unreal Build Accelerator (UBA), which distributes compilation workloads across large EC2 fleets. This infrastructure handles both internal Fortnite development and Unreal Engine licensee build pipelines through the Horde build server. Epic has open-sourced portions of the Horde system via the AWS Cloud Game Development Toolkit, making it available to the broader developer community.

The epicgames.com web properties and the Epic Games Store launcher are built with React and JavaScript, with jQuery still present in parts of the stack per StackShare signals — likely in older store-page and item-shop components that predate Epic's React migration. The frontend serves hundreds of millions of sessions annually across the EGS web, Fortnite launcher flows, and the Fab asset marketplace. For internal productivity, Gmail and Google Workspace are the confirmed email, calendar, and collaboration platforms.

On the data side, Epic runs large-scale player analytics through its AWS data lake — tracking player behavior, spending patterns, churn signals, and engagement metrics across 110M monthly Fortnite players and 317M EGS PC users. This data infrastructure directly informs Fortnite's live-service cadence and the Epic Games Store's free-game giveaway program (Epic offered 100 free titles in 2025, with 77% of those games setting their all-time peak player records during the free week). Epic Online Services (EOS) is used internally across all Epic titles for cross-platform multiplayer, anti-cheat (Easy Anti-Cheat), achievements, and entitlements — and is also licensed to third-party studios, making it simultaneously a first-party infrastructure component and a commercial product offering.

On the creator-economy side, Epic has built Verse — a new scripting language created specifically for UEFN (Unreal Editor for Fortnite) — as a purpose-built tool for the millions of creators building experiences in Fortnite Creative. This represents a meaningful investment in custom language tooling rather than adopting an existing scripting ecosystem, consistent with Epic's broader build-over-buy engineering philosophy.

Epic's near-total commitment to AWS means cloud-agnostic or multi-cloud pitches will land flat. Any infrastructure or data product that lacks a strong AWS-native story — Graviton optimization, EKS-native deployment, S3-backed storage, CloudFront CDN integration — is effectively competing against Epic's existing architecture rather than complementing it. AWS Marketplace listings, native integrations with EKS and EC2 Graviton, and published reference architectures are table stakes for any infrastructure vendor approaching Epic.

Epic's strong build-over-buy posture at the platform layer is the most important cultural signal for sellers to internalize. Horde replaces Jenkins or GitHub Actions; UBA replaces Incredibuild; EOS replaces PlayFab; Verse replaces Lua or JavaScript for creator scripting. This means the most successful vendor pitches historically address areas where Epic has explicitly chosen not to build: specialized rendering and CDN optimization, BI visualization and business intelligence dashboards over the AWS data lake, payments and anti-fraud processing for the Epic Games Store, identity and authentication tooling, and third-party security and compliance tooling that operates above the AWS layer.

The March 2026 restructuring creates a specific vendor consolidation window. If Epic is reducing its overall vendor count and contracting spend by $500M, a product that credibly replaces two or three existing point-solution vendors has a strong ROI narrative right now. Frame pitches around cost consolidation and measurable reduction in tooling overhead — not feature richness — to align with the current procurement mindset.