Star Wars Zero Company Is a Hit. Most of Its Developers Are Unpaid.

The Paradox at the Heart of Zero Company

Star Wars Zero Company is a success. It topped the Steam charts on launch, earned strong reviews, and arrived at a moment when few games in the sprawling Star Wars portfolio could claim genuine critical approval. From the Gamescom stage in Cologne, co-founder Greg Foertsch was already fielding questions about what comes next.

Most of the people who built this game are not being paid.

That contradiction—between commercial and critical triumph on one hand, and financial precarity for the majority of a studio’s workforce on the other—is the story this industry keeps refusing to tell clearly. Bit Reactor’s situation is not unique in its basic shape. It is, instead, a clean, unvarnished example of a pattern that repeats across licensed-game development: the brand carries the risk, the publisher carries the upside, and the developers carry everything else.

What We Know

A Bit Reactor representative confirmed to Game File that the studio furloughed many workers before the game shipped. The rep called it a “difficult decision” made before launch results were known, and stressed explicitly that the call was Bit Reactor’s alone—not EA’s, not Disney’s. That distinction matters, because it draws a line of accountability that lets both publishers retreat behind it.

A lawsuit filed by co-founder Alison Kelly in 2024, with a filing from August 12 this year, stated that Bit Reactor “has furloughed most of its employees and terminated contractors.” A source told Game File that furloughs impacted roughly 80 percent of the team. Another source described a skeleton crew still on payroll, presumably to handle post-launch patching.

Zachariah Scott, a senior technical artist who worked at Bit Reactor from early 2023 until a分手 exit in May, said on LinkedIn over the weekend that the studio was concealing the furloughs from its team for weeks. He told Game File he had spoken with nearly a dozen current and former Bit Reactor workers, and their stories converged: furloughed three weeks before launch, told little, given even less clarity about when—or whether—they would return.

The rep said Bit Reactor hopes to bring furloughed workers back with restored pay if the game performs well. Scott said the workers he talked to were skeptical that even if returns happen, every furloughed person would get their job back.

The Legal Tangle That Explains Everything—and Nothing

To understand how Bit Reactor arrived here, you have to look at the lawsuit between its two co-founders. Kelly, who served as chief operating officer until 2024, sued Foertsch alleging she was pushed out, that she held co-ownership of the studio, and that Foertsch had unjustly enriched himself. She cited damages exceeding $20 million, based on an assessment that Bit Reactor was worth more than double that figure. Foertsch’s side has denied she was ever a co-owner and has countersued, questioning her performance.

The trial, originally scheduled for June, has been postponed until early 2027. Both sides are deposing witnesses and trading filings. But the court documents reviewed by Game File contain something rarer than legal arguments: they contain a corporate origin story.

They describe a studio formed in 2021 with ambitions around tactical combat games, a breakthrough pitch that caught EA’s attention (originally tied to one of EA’s non-Star Wars franchises before pivoting), and early fractures between the co-founders that ran deep enough to end up in federal court and then in Baltimore County’s state courts. The filings paint a picture of a studio that was ambitious, undercapitalized relative to its goals, and navigating the treacherous politics of securing a Star Wars license while simultaneously fighting over who owned what inside it.

None of this excuses the furloughs. But it does explain how a studio can ship a well-reviewed game on time and still have most of its workforce unpaid. When co-founders are litigating ownership, when money is tight, and when a publisher holds the purse strings, the people at the bottom of the capital stack—the developers, the artists, the technical staff—are the first leverage point.

Who Pays, Who Profits

The structure of licensed-game development insulates the publisher remarkably well. EA published Zero Company. Disney (through Lucasfilm Games) controls the Star Wars license. Bit Reactor built the game. When launch succeeds commercially, EA collects revenue share. Lucasfilm gets another approved Star Wars product that reinforces its broader media ecosystem. Bit Reactor—if it survives—gets a credit on the box and perhaps a chance to prove itself for the next contract.

But when things go wrong, or when cash flow tightens ahead of launch, the risk lands on the studio’s payroll. That is the arrangement. It is not secret. It is simply rarely examined this closely.

The Bit Reactor rep’s insistence that the furlough decision was the studio’s alone, and not EA’s or Disney’s, is the kind of statement that reads as corporate prudence and lands as institutional self-protection. Whether or not EA or Lucasfilm pressured the decision is impossible to confirm from outside. What is visible is that both entities benefit from the outcome regardless of who made the call.

What This Means for Licensed Games

Zero Company’s success should not be read as evidence that the licensed-game model is working. It is evidence that the model is extracting more from people than it is returning to them. A hit game with 80 percent of its workforce furloughed is not a healthy sign for the industry’s creative class. It is a sign that the economics reward brands, not builders.

The broader implication is sobering. As Lucasfilm and other IP holders expand their gaming strategies—with new studios, new partnerships, and increasing ambition—the question of who bears development risk will not disappear. It will multiply. Every new licensed title follows the same architecture: IP owner, publisher, developer, each with different exposure and different protections. The developers almost always hold the thin end of the wedge.

Kelly’s lawsuit, with its claims of over $20 million in damages and its revelations about early studio fractures, suggests that Bit Reactor’s troubles predate the furloughs. They predate the launch. They were baked into the studio’s structure from an early point. That is worth noting because it complicates the easy narrative that this is simply a case of a small studio mismanaging its finances before a big release. The fractures were internal, legal, and ongoing. The furloughs were the visible symptom, not the disease.

What Happens Next

The immediate future for Bit Reactor’s furloughed workers is uncertain. The rep has signaled a possibility of recall if launch numbers justify it. Scott’s conversations with workers suggest widespread doubt. The studio’s legal limbo—two co-founders in court, ownership disputed, trial set for 2027—makes any clean resolution unlikely in the near term.

For the industry, the lesson should be clear and uncomfortable. Licensed games are not inherently bad. Zero Company is a good game, made by people who clearly care about their craft. But the system that produced it extracts disproportionate risk from the people who actually do the work, while shielding the brands and publishers that profit from it. Until that dynamic changes—or until someone chooses to name it publicly rather than treat it as routine—games like Zero Company will keep arriving to acclaim, and the people who made them will keep paying the price in silence.