Bit Reactor, the studio behind the newly released Star Wars Zero Company, made the difficult decision 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 move was taken "before it was clear how the launch would go" and was driven by internal financial pressures rather than any external influence from the publisher Electronic Arts or the Star Wars IP holder Disney. The representative emphasized that the decision was made independently by Bit Reactor’s leadership and was not dictated by the larger corporate partners. The timing of the furloughs has drawn considerable attention because Zero Company entered the market to widespread acclaim.
Players and critics alike have praised the title for its immersive storytelling, polished combat mechanics, and faithful recreation of the Star Wars universe. Within days of release, the game climbed to the second spot on Steam’s top sellers chart, underscoring its commercial success and strong community reception. Despite the positive market response, insiders reveal that about 80 percent of Bit Reactor’s workforce was placed on unpaid leave just before the launch.
This left only a skeletal crew—comprising a handful of programmers, QA testers, and support staff—to monitor the live service, patch bugs, and address any technical issues that might arise after the game went live. Sources close to the studio told Game File that the remaining team was tasked with maintaining server stability, rolling out hot‑fixes, and providing basic customer support while the majority of developers were absent.
The primary catalyst for the furloughs appears to have been a cash‑flow crunch. According to the same sources, Bit Reactor “ran out of most of its money just ahead of the launch of its first game.” The studio had invested heavily in development, marketing, and licensing fees, and the anticipated revenue from the launch was not sufficient to cover ongoing payroll and operational costs. As a result, the leadership opted to reduce expenses dramatically by putting most employees on temporary leave. Zachariah Scott, a former senior technical artist at Bit Reactor, took to LinkedIn to criticize the company’s handling of the situation.
Scott claimed the studio was actively trying to conceal the fact that the furloughs had taken place weeks before the public announcement. He also described the financial environment at Bit Reactor as "tight" throughout his tenure, noting that founder Greg Foertsch frequently spoke about the need to secure a new publishing deal or additional funding in order to keep the studio afloat.
Scott recounted a specific incident in which the development team requested additional lightsaber animation resources to enhance the combat experience. The request was denied on the grounds that the budget simply could not accommodate the extra work. He characterized the overall development process as being conducted under "shocking austerity," with the team forced to make compromises on features and polish due to limited financial resources. In response to the criticism, Bit Reactor’s spokesperson reiterated that the company hoped to re‑hire the furloughed workers once the launch proved financially successful.
The statement suggested that a strong sales performance could generate the cash flow needed to bring staff back on board, but also acknowledged the uncertainty surrounding such a scenario. Scott, however, reported hearing from several former colleagues who expressed skepticism about the likelihood of being reinstated, even if the game generated significant profit.
He noted that many felt the company’s promises were vague and that the reality of rehiring a large, dispersed workforce would be logistically challenging. The furlough controversy also surfaced in a 2024 lawsuit filed by former chief operating officer Alison Kelly.
In her filing, Kelly highlighted that Bit Reactor not only furloughed employees but also terminated a number of contractors during the same period. The lawsuit centers on a dispute over ownership stakes in the company. Kelly argues that she should be recognized as a co‑owner based on a draft operating agreement from April 2021, which proposed splitting equity among founder Greg 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 counters that the draft agreement was never executed, meaning Kelly never obtained an ownership interest. They also contend that Kelly’s termination was justified due to alleged poor performance. Kelly denies these allegations and is seeking more than $20 million in damages, claiming that the termination and the mass furloughs were part of a broader pattern of mismanagement and exclusion from the company’s leadership.
The situation at Bit Reactor illustrates the precarious nature of independent game development, especially when a studio’s fortunes are tied to the success of a single high‑profile title. While Star Wars Zero Company has achieved impressive sales figures and critical praise, the underlying financial instability has had tangible human costs. Employees who contributed to the game’s development now face uncertainty about their livelihoods, and the studio’s future hinges on whether the post‑launch revenue can sustain a full re‑staffing effort. Industry observers note that such scenarios are not uncommon in the gaming sector, where development cycles can span several years and studios often operate on thin margins.
The balance between delivering a polished product and maintaining a sustainable payroll is delicate, and missteps can lead to drastic measures like furloughs or layoffs. For Bit Reactor, the coming months will be crucial: continued strong performance of Zero Company could provide the capital needed to rehire staff and stabilize operations, while a decline in sales or persistent technical issues could exacerbate financial strain and potentially lead to further downsizing. Regardless of the outcome, the Bit Reactor case serves as a reminder of the broader challenges faced by smaller developers navigating the high‑stakes environment of blockbuster game releases.
It underscores the importance of transparent communication with employees, realistic budgeting, and contingency planning to mitigate the risk of sudden workforce reductions that can impact morale, public perception, and ultimately, the long‑term health of the studio.