Bit Reactor, the studio behind the highly anticipated title Star Wars Zero Company, made the difficult decision to furlough a substantial segment of its workforce in the weeks leading up to the game’s debut. According to a spokesperson for the company, the move was taken "before it was clear how the launch would go" and was not the result of any pressure from the game's publisher, Electronic Arts, nor from Disney, the holder of the Star Wars intellectual property. The representative described the action as a "difficult decision" forced by financial realities rather than external influence.
The timing of the furloughs has drawn considerable attention because Zero Company has been met with strong enthusiasm from both players and critics. Within days of release, the title climbed to the second spot on Steam’s top‑seller chart, a testament to its polished gameplay, immersive narrative, and faithful use of the Star Wars universe.
Despite the commercial success, insiders say the studio was operating on a shoestring budget. Sources close to Bit Reactor told Game File that as many as 80 percent of the employees were placed on furlough, leaving only a skeletal team to monitor the live service, patch critical bugs, and provide essential support after launch. The rationale behind the mass furlough appears to stem from a cash‑flow crunch that hit the studio just before the game went live. One former senior technical artist, Zachariah Scott, posted on LinkedIn that Bit Reactor was "concealing the fact that the team was furloughed weeks ago," suggesting a deliberate effort to keep the information under wraps until the launch window passed.
Scott further explained to Game File that budgeting constraints were a constant concern during development. He recounted that the studio’s founder, Greg Foertsch, frequently spoke about the need to secure a new publishing deal or additional funding in order to keep the operation afloat.
Scott also highlighted specific creative compromises that resulted from the tight financial situation. For example, developers had proposed adding more lightsaber animation variations to enrich combat, but the request was denied because the allocated budget could not accommodate the extra work. He described the overall development environment as one of "shocking austerity," where even essential polish items were trimmed to stay within the limited financial parameters. In an effort to reassure the furloughed employees, the Bit Reactor spokesperson indicated that the company hoped to bring many of them back once the launch proved successful.
The logic was that a strong commercial performance could generate the revenue needed to re‑hire staff and possibly fund future projects. However, Scott noted that the sentiment among the remaining crew was far less optimistic.
He quoted several colleagues who expressed doubt that a profitable launch would automatically translate into reinstatement for everyone who had been furloughed. The uncertainty surrounding job security added a layer of tension to an already stressful post‑launch period. The furloughs have also surfaced in a legal dispute filed in 2024 by former chief operating officer Alison Kelly. In her lawsuit, Kelly alleges that Bit Reactor not only furloughed employees but also terminated a number of contractors.
The case revolves around the ownership structure of the studio. Kelly claims she is a co‑owner of Bit Reactor, referencing a draft operating agreement from April 2021 that outlined an equity split among herself, founder Greg Foertsch, and early co‑founder Tom Whittaker. Both Whittaker and another co‑founder, Steve Meyer, have since departed the company.
Foertsch’s legal team counters that the draft agreement was never executed, arguing that Kelly never acquired ownership and was instead dismissed for alleged poor performance. Kelly disputes these assertions and is seeking more than $20 million in damages. The broader industry context underscores how indie and mid‑size studios often operate on precarious financial footing, especially when developing a high‑profile licensed game. While a partnership with a heavyweight publisher like EA can provide distribution muscle, it does not always guarantee financial stability for the developer.
In Bit Reactor’s case, the studio appears to have shouldered most of the development costs, leaving it vulnerable when cash reserves ran low. Looking ahead, the future of Bit Reactor remains uncertain.
If Zero Company continues to sell strongly and generates sufficient post‑launch revenue, the studio may be able to rehire many of the furloughed staff and possibly expand its team for future updates or new projects. Conversely, prolonged legal battles and ongoing financial strain could force the company to make further cuts or even consider restructuring. For now, the remaining developers are tasked with maintaining the game’s performance, addressing player feedback, and ensuring that the title’s early success does not fade due to insufficient support. In summary, Bit Reactor’s pre‑launch furloughs reflect a confluence of financial pressure, strategic decision‑making, and the high stakes associated with releasing a flagship title in a beloved franchise.
The situation highlights the delicate balance studios must strike between creative ambition and fiscal responsibility, and it serves as a cautionary tale for other developers navigating the complex landscape of modern game publishing.