Kwalee, the UK-based mobile games publisher that acquired the original development team in 2022, quietly confirmed the layoffs through official channels. Though no detailed reasoning has been provided. Industry insiders speculate that sales figures for Luna Abyss fell short of targets or that a corporate restructuring prioritized mobile titles over the slower-burn success of a mid-tier PC/console game. Whatever the cause, the consequences are stark: a game now orphaned from its codebase, its community untended. And a portfolio of talent scattered across an already precarious job market.
This isn't just another "game studio shut down" story. It's a case study in mismatched expectations, the fragility of acquired studios. And the technical debt that accrues when institutional knowledge vanishes overnight. Let's break down the wreckage and pull out the hard lessons for developers, publishers. And anyone building a product on borrowed time,
The Anatomy of a Post-Launch Studio Collapse
Launching Luna Abyss was supposed to be the crowning achievement for the Kwalee Labs team - a cosmic horror shooter with a distinctive art style and lore depth. But from a business perspective, launch day is just the moment the risk graph changes shape. Pre-launch, all costs are fixed and expectations are internal. Post-launch, the market delivers its verdict. And revenue must justify every remaining salary.
If Luna Abyss sold 50,000 units in its first month (a plausible number for a niche AA title), that might generate around $2. 5 million gross, but after platform fees, publisher cuts. And marketing recoup, the net could be under $1 million. With a team of, say, 30 people averaging $80k/year salary plus benefits, the burn rate for a single month is roughly $250,000. That means the entire game's revenue barely covers four months of operations. Without a long tail or DLC plan, the decision to cut headcount becomes "rational" in spreadsheet terms - but devastating in human and product terms.
Key metrics that often trigger post-launch layoffs:
- Steam concurrent player counts below 500 after the first week
- Low Metacritic user scores (if below 7. 0, recovery is hard)
- Day-one patch download rates lower than pre-orders
- Negative word-of-mouth velocity on social platforms
In the case of Luna Abyss, early reviews were mixed - some praised its atmosphere, others criticized pacing - which may have contributed to a sales curve that flattened faster than the publisher's internal projections.
--- ##Why Being Acquired by a Larger Publisher Can Be a Double-Edged Sword
Kwalee originally made its name as a hyper-casual mobile game powerhouse, launching titles like Draw it and Bake it. Acquiring a team Making a PC/console cosmic horror shooter was a strategic play to diversify into the "AA" space - but the cultural and operational friction was immense. Mobile publishers operate on short feedback loops, rapid A/B testing. And user acquisition cost math. A narrative-driven shooter demands months of polish, community nurturing, and patience.
This mismatch creates a classic principal-agent problem: the acquiring company measures success in ROI per quarter, while the acquired team measures success in creative freedom and genre recognition. When Luna Abyss didn't immediately generate the revenue velocity of a hit mobile game, the corporate parent likely pulled the plug.
We've seen this pattern before: similar layoffs after acquisition at other studios. The lesson is that creative teams should negotiate retention bonuses and multi-year runways during acquisition, not just stock or earn-outs tied to blind revenue targets.
--- ##The Unfinished Business of Live Ops and Post-Launch Support
A game launch today is never a finished product. Luna Abyss needed at least three post-launch patches to address performance issues reported on PC (stuttering on mid-range GPUs, some UI scaling bugs). Without the team, those fixes may never ship. The community forum on Steam already shows players asking "Is this game abandoned? " and that perception alone can tank future sales.
Consider the contrast with Deep Rock Galactic, which launched in early access and spent years on live ops, growing from 2,000 concurrent players to over 40,000 through continuous updates. Luna Abyss had the foundation - interesting cosmic horror lore, a satisfying gunplay rhythm - but needed a roadmap to keep players engaged. The layoff kills that roadmap before it's even written.
From a technical standpoint, orphaned software accumulates what engineers call "bit rot": unpatched bugs, unmaintained dependencies, and eventually compatibility failures with newer OS versions. Within six months, Luna Abyss may become unplayable on certain hardware. And no one will be there to fix it.
--- ##How Layoffs Undermine the Long-Term Value of a Game Product
When a publisher fires the entire development team, they aren't just cutting costs - they're destroying the product's long-term equity. Luna Abyss had potential as a franchise: expansions, merchandise, maybe even a sequel. Without the original creators, any future work would require rebuilding institutional knowledge from scratch. Which is prohibitively expensive.
Publishers often treat layoffs as a "reset button," but in practice, the hidden costs are massive:
- Loss of brand trust (players hesitate to buy from "dead" studios)
- Refund requests may spike (though they rarely succeed)
- Negative PR makes future hiring harder for the publisher
- Game-as-a-service model becomes impossible
A far better approach would have been to transition the team to a reduced "maintenance mode" of 3-5 people, funding that with the game's existing revenue or a small bridge loan. That would preserve the asset's value and keep the community happy, while giving the publisher time to decide on a sequel or IP sale.
--- ##The Human Cost and Technical Debt of Unplanned Departures
Behind the headlines are real people - engineers, artists, designers - who poured years of their careers into Luna Abyss. In modern game development, a single developer might own critical subsystems (networking, animation state machine, lighting pipeline). When they leave without a proper handoff, that knowledge disappears. The remaining skeleton crew (if any) faces impossible choices: do they refactor the whole system or leave a half-broken feature in place?
I've seen this firsthand in production environments where a key engineer left mid-sprint: the team spent weeks reverse-engineering undocumented code. Kwalee Labs is now facing that exact scenario across an entire codebase. Any future attempt to patch Luna Abyss will require paying external contractors to learn the code from scratch - a cost that likely exceeds the original team's salary.
Technical debt from layoffs includes:
- Undocumented build pipelines and CI/CD configurations
- Missing asset optimization profiles
- Stale crash logs no one can triage
What the Industry Should Learn from Kwalee Labs Luna Abyss
First, never hire to peak and then fire at trough. Studios should growth plan for post-launch scaling, not just pre-launch production. Hire generalists who can move between tasks. And build financial buffers covering at least six months of post-launch operations.
Second, acquisitions should include a "survival clause" that guarantees the acquired team 12 months of funding after launch regardless of sales performance. Otherwise, the acquiring company is essentially buying a lottery ticket and burning it if it doesn't win.
Third, the industry needs better transparency around sales expectations. Read more about studio revenue transparency in this GDC talk. If the team knew the publisher needed 200k units to break even, they could have adjusted scope or marketing strategy earlier.
--- ##The Unseen Metrics: Developer Retention as a KPI
Product managers track conversion rates, churn. And LTV. Studio heads should add developer retention to that dashboard. A studio that loses 100% of its staff within a month of launch has a systemic failure - not just in finances, but in leadership, communication, or culture.
Retaining a core team post-launch doesn't have to be expensive. Respawn Entertainment kept a skeleton crew on Titanfall 2 for months after its underperforming launch. And that team eventually prototyped Apex Legends. Luna Abyss's team could have done the same - brainstorming the next project while supporting the live game.
Technical recommendation: Use project management tools like Jira or Linear to track knowledge transfer sessions as tickets with assigned reviewers. If a key developer leaves, that ticket becomes critical path.
--- ##Replicating the Indie Spirit Under a Corporate Umbrella
The irony of Kwalee Labs is that Luna Abyss aimed to capture the indie cosmic horror vibe of Amnesia or SOMA - games made by small, passionate teams without corporate overlords. Once the corporate structure takes over, the decision cycle slows, risk aversion increases. And the very passion that fueled development is treated as a liability.
For indie teams considering acquisition, the advice is clear: negotiate autonomy over post-launch roadmap, demand a minimum team size guarantee for a set period. And ensure the acquiring company has experience in the same genre. Kwalee's mobile-first background was a red flag from the start,
FAQ: Common Questions About the Kwalee Labs Layoff
- What exactly happened at Kwalee Labs?
The entire development team for Luna Abyss was laid off less than a month after the game's launch. Kwalee confirmed the move but provided limited details. - Is Luna Abyss still playable
Yes, as of now the game remains available on Steam and Epic Games Store. But future updates and bug fixes are unlikely without a development team, - Could another team revive the game
Technically yes. But the cost of onboarding new developers to understand the custom engine and codebase would likely be prohibitive for a mid-tier title. - How does this compare to other game industry layoffs in 2025?
It follows the same pattern as recent cuts at Team Bondi, Volition. And Telltale - where entire studios are dissolved post-launch, leaving games abandoned. Internal link: compare with layoff trends in gaming 2024-2025 - What should affected developers do now?
Update portfolios with their work on Luna Abyss, connect with other laid-off devs via LinkedIn and Discord groups. And consider contract work while applying to more stable studios. The Game Developers Conference job board is a good start.
What do you think
Should publishers be required to fund a minimum of six months of post-launch development as part of any acquisition deal?
Is there a case where laying off an entire team immediately after launch is actually the right business decision,? Or is it always short-sighted?
What structural changes in the industry - unionization, better profit-sharing,? Or legal contracts - would prevent this scenario from repeating?
.Need a Custom App Built?
Let's discuss your project and bring your ideas to life.
Contact Me Today →