Ubisoft’s Red Storm Entertainment Was Reportedly Supporting at Least 10 Games Before Mass Layoffs Ended Its Development Era

Ubisoft’s restructuring has reportedly claimed far more than a single support team. According to a new report from Insider Gaming, Red Storm Entertainment was involved in at least 10 different projects before Ubisoft’s recent layoffs effectively ended the studio’s game development operations. That is a striking number for a team that many players had long stopped thinking of as a lead studio, but it also shows just how deeply embedded Red Storm remained across Ubisoft’s wider portfolio.

Red Storm’s reported workload paints a picture of a studio that had become one of Ubisoft’s most widely used internal support partners. Insider Gaming says the team was contributing to Rainbow Six Siege seasonal content, the next mainline Ghost Recon under the alleged codename Project OVR, Brawlhalla, Beyond Good & Evil 2, an unannounced XCOM style Rainbow Six game reportedly called Slice & Dice, Splinter Cell, audio work for The Division 2, concept work for The Division 3, support for an unannounced Watch Dogs Director’s Cut, and another project still in the concept phase. None of those unannounced projects have been publicly confirmed by Ubisoft, so they should be treated as reported internal assignments rather than official slate announcements.

That breadth also helps explain why the closure of Red Storm’s development function feels so jarring. This was not a dormant studio sitting idle between projects. By Insider Gaming’s account, it was touching major Ubisoft brands across shooters, action games, and legacy franchises at the same time. In that light, the layoffs do not just remove one development label from Ubisoft’s structure. They appear to disrupt a studio that had become connective tissue between multiple parts of the publisher’s pipeline.

At the same time, the move lines up with Ubisoft’s larger corporate reset. Reuters reported in January that Ubisoft was reorganizing into 5 “Creative Houses” built around distinct game categories and IP structures, while also pursuing another 200 million euros in savings over 2 years as part of a broader cost cutting plan. In that model, a cross portfolio studio like Red Storm becomes harder to justify, especially if the new structure favors teams operating inside more tightly defined franchise silos rather than floating across many different productions.

That does not make the outcome any less bleak. Red Storm was founded in 1996 and played a foundational role in the early history of both Rainbow Six and Ghost Recon before Ubisoft acquired it in 2000. Even though it had not led a major shipped release in years, its legacy inside tactical shooter development and Tom Clancy gaming was substantial. Seeing that development identity end through layoffs and internal restructuring rather than through a deliberate sunset or creative transition is the kind of industry loss that resonates beyond one studio headcount number. This historical background is well established, while the current closure context comes from the recent reporting and Ubisoft’s wider restructuring.

The practical implication now is that Ubisoft seems to be keeping Red Storm’s technical knowledge while stripping away its role as a game making studio. Insider Gaming reports that the team is being retained primarily as a global IT and Snowdrop support unit. If that holds, Red Storm’s future will be centered on infrastructure rather than authorship, which is a very different endpoint for a studio once associated with some of Ubisoft’s most important tactical franchises.

For Ubisoft, this is another reminder that the company’s “major reset” is not just about budgets and org charts. It is changing who builds its games, how support is distributed internally, and which long running studio identities still get to exist as creative entities. For Red Storm, the reported list of 10 projects only makes that ending feel even more abrupt.

Do you think Ubisoft made a strategic call here, or is shutting down Red Storm’s development role another sign that the company’s restructuring is cutting too deeply into its own history?