Interviews with former Amazon Game Studios employees suggest Amazon's efforts to develop games have been unsuccessful due to hubris, fueled by success elsewhere
After brute-forcing its way to dominance in so many industries, the tech leviathan may finally have met its match. Tweets: @cecianasta , @gadgetlab , @matpiscatella , and @paultassi Tweets: Cecilia D'Anastasio / @cecianasta : Amazon spent biiig $ trying to “win at games.” Sources explain why they've failed so far: hubris. “We'll have our own engine. It will feed into AWS. We'll use it to build our games, and we'll feed those games into Twitch. We'll make all this money.” Nope. https://www.wired.com/... @gadgetlab : The company that brute-forced its way into so many industries may now have met its match. https://www.wired.com/... Mat Piscatella / @matpiscatella : “No matter how big your pockets are, unless you're building games because you want to build games, you're not going to have success.” https://twitter.com/... Paul Tassi / @paultassi : A very good article about Amazon's troubles in the gaming industry mostly stemming from them not getting how to manage projects and forcing everything to use the Lumberyard engine https://twitter.com/...
Context & Ripple Effects
The Wired interviews give named voices to a story that had been building in pieces: Protocol reported two months earlier that Amazon's structure and culture aren't optimized for creative work, and this piece traces the failure to a specific strategic bet — Mike Frazzini's 2017 flywheel pitch in which an in-house engine would feed AWS, AWS would feed first-party games, and Twitch would monetize them. Former employees now describe that logic as hubris imported from Amazon's retail and cloud wins.
What makes the account credible rather than anecdotal is how well it predicts what came next: reporting on leadership as the core of the gaming division's struggles despite a reported $500M/year budget, the quiet retreat from Lumberyard via open-sourcing it as the Open 3D Engine, and Google's own Stadia collapse showing the same playbook failing elsewhere.
First-order effects
- Amazon Game Studios' internal teams bear the direct cost: reports say they were required to build on Lumberyard, tying project timelines to an unproven engine while the division burned a reported $500M a year without a hit.
- Frazzini's flywheel thesis — engine-to-AWS-to-Twitch — is now publicly discredited by the people who worked inside it, putting his leadership of the division under direct scrutiny.
Second-order effects
- Google's Stadia failure, missing controller-sales and MAU targets after tens of millions spent on games, shows rivals ran the same infrastructure-first play and failed the same way — forcing both companies to rethink whether cloud and distribution advantages translate into game-making ability.
- Amazon's eventual exit from a proprietary engine hands ground to established engine makers and shifts its gaming bets toward titles like New World, which later delivered hundreds of thousands of concurrent Steam players and validated a narrower, craft-first approach.
Third-order effects
- If the pattern holds, Big Tech's entry into games stops being a platform land-grab and becomes a talent business it cannot shortcut with capital — engine ownership, studio culture, and creative leadership matter more than AWS or Twitch reach.
- The Lumberyard-to-Linux-Foundation handoff points toward commoditized open engines as the industry default, weakening any strategic rationale for tech giants to build their own.
The trend: Big Tech's attempt to brute-force gaming through platform flywheels is collapsing into a grudging acknowledgment that game development is a craft-and-talent business that scale economics don't buy.