Build a Rocket Boy, the studio behind MindsEye, appears to be winding down permanently. The picture comes from public posts by multiple employees, including a senior recruitment staff member who said he would remain in place to help the company close out its work.

The apparent closure follows multiple rounds of layoffs and a difficult period for the Leslie Benzies and Mark Gerhard-owned studio. It also follows a collective grievance led by the Independent Workers’ Union of Great Britain, alongside accusations involving crunch and unlawful employee monitoring. Those matters are serious allegations and should not be treated as findings simply because the studio is now reportedly closing; they nevertheless form an important part of the context around the company’s final months.

For players, the immediate and most important distinction is between a game that has struggled and a developer that may no longer be operating. A studio closure can affect who is available to maintain a released game, address outstanding technical problems, or communicate about its future. However, the available information does not establish what will happen to MindsEye, whether any team will continue supporting it, or whether a formal plan for the game will be announced. Those details remain unconfirmed.

What the employee posts indicate

Several Build a Rocket Boy staff members have recently said on LinkedIn that their employment is ending. The group includes level designer Liam Shannon, QA analyst Elizabet Tyaneva, release manager Michaela Emslie, and production QA analyst Cameron Deaves.

On their own, posts from departing staff could describe another reduction in headcount at a company that intends to continue. The clearest indication that this is something more comes from Dan Hawkins, Build a Rocket Boy’s principal talent acquisition partner. Hawkins wrote that he and his colleagues were reaching the end of their time at the company and that he would help the studio through its final wind-down work in HR.

“I will be seeing BARB through till the very end, helping wrap things up here in the HR department,” Hawkins wrote while saying he was open to new opportunities.

That language matters because “winding down” generally describes the orderly closing process for an organization rather than a normal, ongoing layoff cycle. In practical terms, it can involve concluding employment and HR processes, transferring or documenting company responsibilities, and closing out remaining operations. It does not by itself tell the public which assets, projects, services, or employees may be handled in which way. Nor does it answer whether anyone else could take responsibility for MindsEye later.

People familiar with the situation have also indicated that the closure is permanent. Build a Rocket Boy had not publicly responded at the time these reports emerged, so the studio’s own account of the decision, timing, and implications is still absent.

A troubled final chapter for MindsEye’s developer

The studio’s fate is closely tied to the difficult reception for MindsEye, characterized as a GTA-like game that drew widespread criticism. The company had made multiple attempts to improve the game’s prospects, but the current reports suggest those efforts did not lead to an ongoing path for Build a Rocket Boy.

Calling a game “GTA-like” usually means it is being discussed beside the broad open-world action formula associated with Rockstar’s series: a description that brings an enormous set of player expectations around scale, activity, polish, systems, mission design, and technical performance. It is not a formal genre with a fixed checklist, but it is an especially demanding comparison. As interest in the wider GTA space remains intense, including around the hardware market attention surrounding GTA 6, games placed in that orbit can face unusually close scrutiny.

That broader framing should not obscure the human stakes of this report. The named employees cover roles that touch very different points in game development and release. A level designer is commonly focused on building and refining playable spaces, encounters, routes, and the way a player moves through a game. A QA analyst works in quality assurance, identifying, documenting, and helping teams reproduce defects or inconsistent behavior. A release manager coordinates the steps involved in getting builds and updates ready for release. Production QA connects testing with the wider production process, helping make sure bugs and testing priorities are visible to the teams deciding what can be fixed and when.

In other words, the posts do not point only to one department being affected. They describe staff from development, testing, release coordination, and HR all approaching the end of their work with the company.

Why “closure” requires more care than “layoffs”

Layoffs and a studio shutdown are related but not interchangeable terms. Layoffs reduce a workforce; a studio can survive them, continue a project, or hire again later. A permanent closure means the business itself is reportedly ceasing to operate. That is why Hawkins’ reference to seeing Build a Rocket Boy through to the end is more consequential than a standard notice that a particular team or role has been cut.

Still, public reporting has limits. Employee posts can credibly convey that their jobs are ending and can provide a direct window into a workplace’s final days. They cannot, without a formal company statement or specific agreements becoming public, settle every question that players, customers, and former workers may have. There is no confirmed information here about:

  • the final date of the wind-down;
  • the future of MindsEye support, updates, or communications;
  • whether another organization could assume responsibility for any part of the studio’s work;
  • the number of employees affected by the closure; or
  • how outstanding workplace allegations and the collective grievance may proceed.

Those unknowns are worth stating plainly. It is tempting to turn a reported closure into a full story about a game’s long-term availability or every affected project, but the present evidence does not support those conclusions.

The workplace context cannot be separated from the business story

Build a Rocket Boy’s reported wind-down arrives after a period of controversy beyond the reception to its game. There had already been multiple layoff rounds. The Independent Workers’ Union of Great Britain led a collective grievance, and allegations had been raised regarding crunch and unlawful employee monitoring.

“Crunch” is industry shorthand for sustained periods of unusually intensive work, often near major development milestones or launches. The term can describe a broad range of situations, which is why it is important not to assume the precise conditions of the allegations from the label alone. Likewise, allegations of unlawful monitoring concern conduct that would need to be assessed through the relevant processes and evidence; they should not be presented as settled fact without a determination.

What can be said is that these issues put the studio’s employment practices under public attention before the latest closure reports. With employees now publicly seeking work and a recruitment lead helping to wrap up HR duties, the immediate consequence is a loss of jobs for people whose skills range from design and QA to release operations and talent acquisition.

What to watch for next

The next meaningful development would be a direct statement from Build a Rocket Boy or its owners. Such a statement could clarify whether the studio has formally entered a closure process, establish a timeline, and address the future of MindsEye. Until then, the strongest public evidence is the convergence of posts from affected staff, particularly the wording from a senior HR and recruitment figure describing an end-of-company wind-down.

For the moment, the cautious reading is also the clearest one: Build a Rocket Boy is reportedly closing permanently, while key details about its game and the precise mechanics of the shutdown have not been made public. That leaves a sobering final note for a studio whose release ambitions, personnel decisions, and workplace allegations had already placed it under a harsh spotlight.