When a small game studio's financial runway evaporates, the invisible machinery of source code custody, middleware licenses. And cloud billing often determines whether a game survives-or vanishes forever.
In June 2025, Kotaku broke the news that MidBoss, the indie studio behind the acclaimed cyberpunk point-and-click adventure 2064: Read Only Memories, had filed for Chapter 7 bankruptcy. The filing was signed by Matt Conn, the company's current CEO-who had been brought back into the role just months earlier after a previous departure. To many players, the headline felt like a kickstarter‑era miracle gone sour. To senior engineers and technical operators, however, the bankruptcy is a case study in the software supply chains, platform dependencies. And governance failures that can quietly dismantle even a beloved digital product.
I've spent over a decade working on mobile game backends, cloud infrastructure for digital media. And cross‑platform porting pipelines. When I read the court documents, I didn't see just a studio running out of cash. I saw a cascade of engineering decisions made under duress, technical debt accrued across two different game engines. And an ownership structure that left the source code and digital assets dangling in a legal grey zone. This article dissects the machinery behind the news-from Adventure Game Studio's legacy constraints to the cold reality of Unity licensing survival-so that anyone building or sustaining software can learn from the wreckage.
The Cyberpunk Narrative That Foreshadowed Its Own Studio's Breakdown
2064: Read Only Memories launched in 2015 as a retro‑styled adventure set in a neon‑drenched San Francisco where human‑AI relationships are legally contested. The game itself was a love letter to 1980s cyberpunk, built initially on the open‑source Adventure Game Studio (AGS) engine. Two years later, the studio released 2064: Read Only Memories, a full remake in Unity, to reach consoles and a broader market. The thematic irony is hard to miss: a story about digital consciousness and corporate control ended up being produced by a company that couldn't outrun its own technical and legal constraints.
MidBoss's bankruptcy filing lists assets between $50,001 and $100,000 and liabilities totaling over $700,000. Those numbers. While modest by AAA standards, reflect years of attempting to fund an entire development cycle through crowdfunding, modest game sales. And recurring maintenance overhead. From a software engineering standpoint, the plateau between the 2015 AGS original and the 2017 Unity remake represents the exact point where many indie studios inadvertently mortgage their future stability for short‑term platform expansion.
Indie Game Engines as Both Enablers and Long‑Term Liabilities
The original 2064: Read Only Memories was created in AGS, a scripting‑based engine originally designed for classic point‑and‑click adventures. AGS works beautifully for 2D narrative experiences but lacks native support for modern console SDKs, 64‑bit builds. Or robust memory management. In production environments, I've seen teams fall in love with a framework because it accelerates the prototype, only to discover that the tooling for automated testing, localisation, and CI/CD is almost nonexistent. AGS projects typically bundle assets and scripts in a proprietary format that resists version control granularity; merging AGS game data in git is notoriously fragile.
For a small studio shipping on PC, those limitations are manageable. But as soon as a console port is on the roadmap, the engine becomes a technical debt time bomb. MidBoss's decision to remake the entire game in Unity wasn't a vanity project-it was an engineering necessity driven by platform requirements for Xbox, PlayStation. And Nintendo Switch certification. However, migrating a completed narrative title that already has a paying audience introduces a massive regression risk: every dialogue tree, puzzle logic. And UI interaction must be re‑implemented and re‑tested, often without the benefit of a formal specification.
Middleware Licensing and Platform Survival
When a studio files for Chapter 7 bankruptcy, the immediate technical concern is whether it can continue to honour middleware licences. Unity, for example, ties its Editor and runtime to the legal entity that signed the subscription. If that entity dissolves, the licence can lapse, making it difficult-or occasionally illegal-for a trustee to keep building or even hot‑fixing the game. This isn't merely a contract quirk; it can block critical security patches from reaching live players if a dependency tree relies on a commercial SDK that checks an entitlement server.
The Unity Runtime Fee and Per‑Install Counting
MidBoss was primarily a Unity shop by 2017. Even after migrating away from AGS, the studio remained dependent on Unity's ecosystem for console export modules and performance optimisation. Under Unity's post‑2023 pricing changes, per‑install runtime fees could have squeezed a thin‑margin catalogue further. While those fees are paused or restructured for many indies, the uncertainty alone can make a studio's financial model unviable to a bankruptcy trustee who must decide whether to keep digital storefronts running.
Third‑Party Plugins and the Technical Estate
Beyond the engine, point‑and‑click adventures often rely on dialogue‑system plugins, audio middleware (such as FMOD or Wwise). And platform‑specific save‑game SDKs. Each of these carries its own licence terms, and many are non‑transferable. In a Chapter 7 liquidation, the trustee can't simply sell the "game" as an asset; they must inventory every licence and determine which are assignable. The more sprawling the plugin stack, the less valuable the technical estate becomes to a potential acquirer.
Cloud Infrastructure: The Indie Cost Trap
Even a single‑player narrative game can accrue significant cloud costs if it offers any online features-cloud saves, leaderboards, analytics. Or DRM checks. MidBoss's games, including the subsequent Read Only Memories: NEURODIVER, used cloud‑based services for cross‑platform save synchronisation and achievement tracking. In bankruptcy, those service accounts risk suspension for non‑payment, causing features to silently fail inside the product. From an SRE perspective, no one may be on call to detect the outage until players flood Discord with complaints.
Data Residency and Player Privacy
Some of MidBoss's cloud services may have stored player email addresses, save‑game metadata. Or analytics. A Chapter 7 trustee has a legal obligation to secure or dispose of personally identifiable information in accordance with privacy regulations. For a tiny studio without a dedicated compliance officer, the process becomes a scramble that can attract regulatory attention-especially if EU players are affected and GDPR obligations surface years after the initial data collection.
Source Code Custody and Version Control Gaps
When I examined public traces of the 2064: Read Only Memories codebase, one pattern stood out: the repository history was fragmented across private GitLab instances, per‑developer forks, and possibly older Perforce depots from the AGS era. This lack of a single source of truth is common in indie teams where continuous integration was never fully automated. In a bankruptcy, the trustee may need to locate the canonical source repositories to sell them-and if no one can confidently identify the official build branch, the asset's value diminishes sharply.
Build Pipelines Lost to Time
The Unity remake required a specific combination of Editor version, platform SDKs. And plugin versions. Without a reproducible Docker‑based build environment or a documented setup guide, even a well‑intentioned acquirer would face weeks of archaeology to produce a shippable binary. I've personally seen legacy iOS games become un‑buildable within 18 months because Apple's certificates expired and no one kept a clean CI pipeline. For MidBoss's catalogue, iOS and tvOS builds-if they existed-are likely already in this limbo.
Console Certification: A Hidden Tax on Porting
Porting a narrative adventure to Xbox, PlayStation. And Switch demands certification testing for each platform. Every patch must pass lot check, which costs time and money. When a studio files bankruptcy, platform holders may suspend the developer account, preventing further updates. Or even delist the game if they see insolvency as a risk to the player experience. According to the original Kotaku report, MidBoss's CEO struggled with "crushing platform fees" that ate into already thin margins.
The 2064: Read Only Memories Console Catalogue
At the time of bankruptcy, 2064: Read Only Memories was available on Switch, PS4, and Xbox One. Each storefront represents a separate SKU with its own bug backlog. The trustee may not have the expertise to triage these. So the most likely outcome is a passive delist as platform agreements lapse. From a digital preservation perspective, this is a quiet catastrophe: a well‑reviewed cyberpunk narrative could vanish from console storefronts because the legal entity that held the publishing rights no longer exists.
Governance, Ownership. And the Legal Grey Zone
MidBoss's CEO returned to the role months before the filing, suggesting internal governance turbulence. In startup land, frequent C‑suite turnover often leaves engineering documentation, domain registrations, and payment‑processor accounts tied to personal emails of departed founders. A Chapter 7 trustee must untangle this web. I've seen situations where the source code for a beloved indie game was locked inside a former developer's Bitbucket account because the company never opened an organisational repo. That sort of personal entanglement can turn a salvageable asset into a legal black hole.
Continuity of the Read Only Memories Brand
The read only memories franchise also includes NEURODIVER, released in 2024. Its fate is equally uncertain. If the trustee sells the intellectual property, a new studio might maintain the catalogue. However, without access to the original 2064: Read Only Memories source and the institutional knowledge of why certain systems were built the way they were, any port or remaster becomes a reverse‑engineering project rather than a simple re‑release.
The Kickstarter Afterlife: Financial Runway and Code Rot
MidBoss initially funded Read Only Memories through Kickstarter, raising over $180,000 from backers who expected long‑term support. Crowdfunding creates a moral-and often contractual-obligation to deliver promised features and updates. When the studio files bankruptcy, those promises can't be fulfilled. But the digital goods already in players' libraries remain. Backers become involuntary long‑term testers of an unmaintained product, discovering bugs that will never be patched. The code rot accelerates as operating systems and hardware move forward, breaking the game's compatibility layer step by step.
Court records show MidBoss's debts included unpaid royalties, contractor fees, and state tax obligations-liabilities that can start a cascade of platform account freezes. For a small studio living hand‑to‑mouth on Steam revenue, a single frozen account can halt development entirely, turning a going concern into a non‑operational entity in weeks.
Lessons for Studios Building on Open‑Source Foundations
The MidBoss bankruptcy isn't a unique story; it's the logical endgame of a set of engineering and business decisions that many indie teams make. Here are the architectural lessons I draw from the Kotaku revelation and the years of technical reporting that preceded it.
1. Treat the build pipeline as a first‑class product
If your game builds only on a specific developer's machine, it's already dead in an insolvency scenario. Document the exact toolchain, lock dependency versions in a manifest. And automate a clean build from scratch. That way, a trustee or acquirer can reproduce the binary without reverse engineering.
2. Audit licence transfers early
Before signing a middleware deal, ask the vendor what happens if the
.
Need a Custom App Built?
Let's discuss your project and bring your ideas to life.
Contact Me Today →