Bit Reactor, the studio behind the newly released Star Wars Zero Company, made the difficult choice to furlough a substantial segment of its staff in the weeks leading up to the game’s debut. According to a spokesperson for the company, the decision was taken before any clear picture of how the launch would perform, and it was not dictated by the game’s publisher, Electronic Arts, nor by Disney, the holder of the Star Wars intellectual property. The representative described the move as a "difficult decision" that had to be made in a period of financial uncertainty.
The timing of the furloughs has raised eyebrows because Zero Company has been met with enthusiastic reception from both players and critics. Within days of its release, the title climbed to the No. 2 spot on Steam’s best‑selling games chart, indicating strong market demand. Nevertheless, insiders say that as much as 80 percent of Bit Reactor’s workforce was placed on unpaid leave, leaving only a skeleton crew to monitor the live service and patch any bugs that surface after launch.
Sources close to the studio explain that the furloughs were driven by a cash‑flow crunch. The company reportedly exhausted most of its available capital just before the launch of its first major title. This financial strain forced management to reduce payroll costs dramatically, even though the product itself was performing well commercially. Former senior technical artist Zachariah Scott added further context in a LinkedIn post, alleging that the studio had been trying to conceal the scale of the furloughs from the public.
Scott told Game File that budgets during his time at Bit Reactor were "tight," and that founder Greg Foertsch frequently spoke about the need to secure a new development deal in order to keep the studio afloat. He recounted that developers had requested additional lightsaber animation work, only to be told that there was simply no money left for such enhancements. Scott summed up the development environment as one of "shocking austerity," suggesting that the team was forced to make significant compromises in order to ship the game.
In response, Bit Reactor’s spokesperson expressed optimism that the furloughed employees could be rehired once the launch proved successful. The company hinted that a strong commercial performance might generate enough revenue to bring staff back on board.
However, Scott noted that many of the workers he spoke with were skeptical about the likelihood of regaining their former positions, even if the game generated a profit. Their concerns stemmed from the uncertainty surrounding the studio’s financial health and the lack of a concrete plan for rehiring. The furlough issue resurfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly. In her filing, Kelly referenced the mass furloughs and also claimed that the studio had terminated several contractors during the same period.
The lawsuit centers on a dispute over ownership of Bit Reactor. Kelly argues that she should be recognized as a co‑owner of the company, citing a draft operating agreement from April 2021 that proposed splitting equity among Foertsch, herself, and early co‑founder Tom Whittaker.
Both Whittaker and another co‑founder, Steve Meyer, have since departed the studio. Foertsch’s legal team countered that the draft agreement was never executed, meaning Kelly never obtained any ownership stake. They further alleged that Kelly was dismissed for poor performance, a claim she denies.
In her complaint, Kelly seeks more than $20 million in damages, asserting that the termination and the handling of the furloughs caused significant personal and professional harm. The situation at Bit Reactor highlights the precarious balance that independent game developers must maintain between creative ambition and financial viability.
While Zero Company has garnered critical acclaim and strong sales, the behind‑the‑scenes financial pressures have led to drastic workforce reductions. The case also underscores the importance of clear ownership structures and transparent communication within start‑up studios, especially when large sums of money and high‑profile licenses are involved. Looking ahead, the future of Bit Reactor remains uncertain. If the game continues to sell well and the studio can secure additional funding or a new publishing partnership, there may be an opportunity to rehire the furloughed staff and stabilize operations.
Conversely, if revenue falls short of expectations or if legal battles drain resources, the remaining team may struggle to maintain the game’s live services and support its community. For now, the developers who stayed on are tasked with addressing post‑launch bugs and ensuring that the player experience remains smooth, all while navigating the lingering effects of a major financial upheaval. The broader industry will likely watch Bit Reactor’s outcome closely, as it serves as a cautionary tale about the risks of launching a high‑budget title without sufficient financial backing.
The story also raises questions about how publishers and IP holders can support smaller studios during critical launch windows, especially when the success of a franchise‑based game can have far‑reaching implications for both the developer and the brand. In summary, Bit Reactor’s decision to furlough the majority of its workforce just before the release of Star Wars Zero Company was driven by an acute cash shortage, not by external pressure from EA or Disney.
While the game has achieved impressive sales and critical praise, the studio now operates with a lean team tasked with post‑launch support, and it faces ongoing legal disputes over ownership and compensation. The ultimate resolution will depend on the game’s continued commercial performance, the outcome of the lawsuit, and the studio’s ability to secure new funding or partnerships that could allow it to bring back its displaced employees.