Bit Reactor, the studio behind the much‑anticipated title 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 release. 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 emphasized that the choice was internal and driven by financial realities rather than external mandates.

The game itself has been welcomed enthusiastically by both players and critics. Within days of its debut, Zero Company climbed to the second spot on Steam's top sellers chart, a testament to the strong brand recognition of the Star Wars franchise and the solid gameplay experience the developers delivered. Despite the positive reception, the behind‑the‑scenes situation at Bit Reactor was far from ideal. Multiple sources close to the studio told Game File that roughly 80 percent of Bit Reactor's workforce was placed on furlough, reducing the company to a skeletal crew tasked with monitoring the live service, fixing bugs, and providing essential support after launch.

This drastic reduction in manpower was reportedly caused by the studio exhausting the majority of its cash reserves just before the game hit the market. In other words, the company found itself financially strained at a critical juncture, forcing it to cut costs in a way that directly impacted its employees. Zachariah Scott, a former senior technical artist at Bit Reactor, took to LinkedIn to allege that the studio had been attempting to hide the furloughs from the public and the broader gaming community. He claimed that the company was "concealing the fact that the team was furloughed weeks ago," suggesting a lack of transparency that may have affected morale and trust among the remaining staff.

Scott also described the budget environment during his tenure as "tight," noting that studio founder Greg Foertsch frequently spoke about the need to secure a new game deal in order to keep the operation afloat. According to Scott, the development team had aspirations to enhance the game with additional lightsaber animations—a feature that would have enriched combat dynamics and visual fidelity. However, these ideas were repeatedly rejected on the grounds that the budget simply could not accommodate them.

Scott summed up the development atmosphere as one of "shocking austerity," implying that the team was forced to make significant compromises in order to bring the product to market. When asked about the possibility of rehiring the furloughed workers, the Bit Reactor spokesperson expressed optimism, stating that the studio hoped a successful launch could generate enough revenue to bring those employees back. The implication was that a strong commercial performance might provide the financial breathing room needed to restore the workforce to its pre‑launch size.

Nonetheless, Scott relayed that many of his former colleagues were skeptical. He quoted them as saying they were "less confident that even if there were returns, that all who were furloughed would get their old jobs again," reflecting a lingering sense of uncertainty about job security.

The furloughs also became a point of contention in a lawsuit filed in 2024 by former chief operating officer Alison Kelly. In her legal filing, Kelly highlighted that the studio had not only furloughed staff but also terminated several contractors.

The lawsuit revolves around the ownership structure of Bit Reactor, specifically whether Kelly holds a co‑ownership stake alongside founder Greg Foertsch or whether Foertsch is the sole proprietor. Kelly cited a draft operating agreement from April 2021 that proposed dividing the company's equity among herself, Foertsch, and early co‑founder Tom Whittaker. Both Whittaker and another co‑founder, Steve Meyer, have since departed from the company.

Foertsch's legal team countered Kelly's claims by asserting that the draft agreement was never executed, meaning Kelly never became an official owner. They further alleged that Kelly's termination was justified due to poor performance. Kelly, however, denied these accusations and is seeking more than $20 million in damages, arguing that her removal was unjust and that she was unfairly excluded from any equity share. The broader context of this situation underscores the volatility that can accompany indie and mid‑size game development, especially when working with high‑profile licenses that come with elevated expectations and costs.

While Star Wars Zero Company has achieved impressive sales figures and critical praise, the internal financial strain experienced by Bit Reactor serves as a cautionary tale about the importance of sustainable budgeting, transparent communication with staff, and the risks associated with relying heavily on a single product launch to secure a studio's future. In summary, Bit Reactor's pre‑launch furloughs impacted the majority of its workforce, leaving a minimal team to manage post‑release support. The studio attributes the decision to depleted cash reserves rather than external influence, and while there is hope that the game's success could enable rehiring, skepticism remains among former employees. The situation has further escalated into legal disputes over ownership and compensation, highlighting the complex interplay between creative ambition, financial management, and corporate governance in the modern gaming industry.