Star Wars Studio Layoffs Follow Launch Furloughs

Game studios that depend on a single launch show how cash timing can drive staffing cuts even after strong sales.

Updated on Nov. 7, 2026 in Job Search

Quiet, unoccupied game-studio workspace with a bare desk, pushed-back chair, and cardboard box under soft window light.
Bit Reactor has laid off an unspecified number of developers on Star Wars Zero Company, after furloughing up to 80% of staff before the game's launch. AI Illustration. Upload story photo >

Bit Reactor, developer of Star Wars Zero Company, has laid off an unspecified number of developers on the game, several of whom announced their departures on LinkedIn. The cuts follow a period in which the studio had furloughed up to 80% of its staff before the game's launch, and the layoffs affect a studio-level workforce that operators in game development and creative production will read as a signal about project-based staffing risk.

Why it matters

CEO Greg Foertsch attributed the furlough to unexpected business developments outside the company's control, and a report says Bit Reactor ran out of most of its money ahead of launch. Even with Zero Company selling one million copies within a month, the studio's cash position appears to have been tight enough to drive both furloughs and layoffs, illustrating how launch-dependent revenue can leave small development teams exposed.

Bit Reactor furloughed up to 80% of its staff in September 2026, ahead of Zero Company's launch, and Zero Company sold one million copies within a month. The number of developers laid off in the current round was not disclosed in the reporting.

The players

Bit Reactor

A video game developer whose Star Wars Zero Company became a commercial launch, and whose staffing actions reflect the financial pressure that can accompany project-based game development.

Lucasfilm

The Walt Disney Company subsidiary that holds the Star Wars franchise and licenses it to game developers, and which the source says is interested in more creative spin-offs in the vein of Zero Company.

The details

Layoffs at a studio are typically announced through individual employees, and in this case several Zero Company designers posted their departures on LinkedIn. Bit Reactor's earlier furlough of up to 80% of staff is a labor-cost pause that holds people in place without paying full wages, and it was used in the weeks before launch. Several furloughed staff were later hired back, which shows the studio using the furlough as a flexible tool rather than a single, final reduction.

Timeline

  1. October 2024: Ryan Mosher joined Bit Reactor as a senior quality assurance analyst.

  2. September 2026: Bit Reactor furloughed up to 80% of its staff in the weeks before Zero Company's launch.

  3. November 7, 2026: Layoffs were reported by Bespin Bulletin and PC Gamer.

Market Landscape

Studios that depend on a single major launch often face cash timing gaps between development and revenue, and furloughs have become a common tool to manage them. Bit Reactor's case fits that pattern, where a commercially strong title did not prevent workforce reductions around launch.

Operators in creative and project-based industries should treat furloughs as a flexible but costly staffing lever that can precede layoffs. Workers in similar roles may face near-term uncertainty, and employers should watch cash runway relative to launch timing.

The takeaway

The practical signal for operators is that a strong launch does not guarantee stable staffing, so cash runway should be modeled against the post-launch revenue curve rather than launch-week sales alone. Track workforce planning disclosures and rehiring patterns in your own project-based hiring to judge how much flexibility furloughs really provide.

Further reading

For broader context on hiring and workforce shifts, see Job Search coverage across United States employers.