Unity (2023): the runtime fee, the developer revolt, and the 22-day CEO removal
On September 12, 2023, Unity Technologies — the game engine used by approximately half of all new mobile games and a significant share of indie and AAA development — announced a new “Runtime Fee” that would charge developers per-install fees once their games crossed revenue and install thresholds. The fee was to apply retroactively to games already shipped. The developer reaction was the worst pricing-revolt response in modern software-tooling history: studios publicly committed to leave Unity, the Slay the Spire developer announced its next game would be built on Godot, and the company’s consultant-relationship social channels were flooded with developer protest. On September 22 Unity walked back the most controversial elements. On October 9 CEO John Riccitiello stepped down. The case is the most-current example in software pricing of how a defensible-on-paper pricing change can produce catastrophic outcomes when it violates the customer-base’s baseline expectations.
- Story: Unity announced 'Runtime Fee' per-install pricing September 12, 2023 retroactive on existing installed bases. Immediate widespread developer backlash. Unity reversed core elements within days but trust damage substantial. CEO John Riccitiello departed October 9, 2023. New CEO Matthew Bromberg May 2024. Significant ongoing developer-migration risk.
- Why it matters: Unity Runtime Fee is the defining recent pricing-decision cautionary tale — demonstrating how pricing decisions can destroy platform-developer trust in days that took years to build.
- Takeaway: Pricing decisions that affect existing customers' historical activity (retroactive fees) produce much stronger negative reaction than prospective pricing changes.
- Takeaway: Platform-developer relationships depend on trust that pricing terms won't change in the developer's disfavor — once broken, ongoing risk perception persists.
- Takeaway: Major pricing changes need stakeholder engagement and communication far in advance of public announcement.
Unity Runtime Fee controversy — the four-step story
Unity Runtime Fee by the numbers
Quick facts
Where Unity was in mid-2023
Unity entered 2023 as a public company under financial pressure. The company had IPO’d in 2020 at $52/share and traded above $200 in late 2021 before declining sharply through 2022. Its merger with ironSource in 2022 had not produced the modeled synergies, costs had grown faster than revenue, and the company had been laying off staff through 2023. The pricing model up to that point was a subscription Unity Pro / Plus structure with revenue thresholds — developers paid recurring license fees rather than per-install fees.
The Runtime Fee was announced as a way to capture more revenue from the most successful Unity-built games. The strategic logic was real — the existing subscription pricing did not scale with developer success, and a small number of games captured the bulk of value Unity helped enable. The execution treated the developer base as if it had no choice but to accept the change.
The announcement and the revolt
On September 12, 2023, Unity published the Runtime Fee policy. The headline mechanics: starting January 1, 2024, Unity would charge developers a per-install fee on games that crossed both revenue and lifetime-install thresholds. The fees ranged from $0.20 per install at the lowest tier down to $0.01 per install for high-volume developers, and the fee would apply retroactively to existing shipped games once the thresholds were crossed. The retroactive element was the breaking point.
Developer reaction was immediate and across the entire developer ecosystem. Mega Crit (developer of Slay the Spire) publicly committed to migrate to Godot for its next game. Massive Monster (Cult of the Lamb) threatened to remove its games from sale. Mobile-game developers calculated potential exposures in the tens of millions of dollars. Industry organizations called for the policy to be withdrawn. Unity’s offices were briefly closed due to a credible threat to employee safety from an upset developer.
The walk-back and the CEO change
On September 22, 2023, Unity published a substantially revised version of the policy. Changes included: fees would only apply to new versions of games built on the next Unity LTS release (not retroactively to existing builds), per-install fees would be capped at 2.5% of revenue, developers could self-report installs rather than relying on Unity’s telemetry, and certain education and charity uses were exempt. The revisions made the policy survivable for most developers but the trust damage was already done.
On October 9, 2023, John Riccitiello stepped down as CEO “effective immediately.” James Whitehurst (former Red Hat CEO and IBM president) was named interim CEO. Through late 2023 and 2024 the company continued restructuring — further layoffs were announced in January 2024 (1,800 employees, about 25% of staff) and the runtime-fee policy was eventually canceled outright in September 2024 in favor of a subscription-pricing increase under permanent CEO Matt Bromberg.
How RGM thinks about pricing changes for high-trust software
When clients ask about pricing-model changes for software with a high-trust customer relationship, the Unity Runtime Fee case is the clearest current example of what not to do. Three structural mistakes compound. First, the change was retroactive to existing shipped games. Software developers had built business plans around the previous pricing model; retroactive changes do not just raise prices, they invalidate prior business decisions and signal that the vendor cannot be trusted with future commitments. Second, the change was per-install rather than per-revenue. Per-install pricing is operationally hostile to most game developers because installs are tracked imperfectly, can be fraudulent, and do not correlate with revenue at the unit level. Per-revenue pricing aligns the vendor’s interests with the customer’s success. Third, the change was announced unilaterally rather than negotiated with the developer base or piloted in subsets. Major customer-facing pricing changes for high-trust software almost always benefit from a graduated, opt-in rollout that lets the customer base internalize the change.
The pattern is broader than gaming. SaaS pricing changes that raise prices on existing committed customers, that introduce metering that customers can’t verify, or that change the economic basis of the relationship (per-install vs per-revenue, per-seat vs per-API-call) all carry the same risk. The Unity outcome — CEO removal, partial walk-back, market-cap damage, multi-year trust rebuild — is the cost of getting it wrong. The lesson for clients is that pricing-model changes for embedded software are not commercial decisions, they are trust decisions, and they need to be communicated and executed accordingly.
Frequently asked questions
How much money would the Runtime Fee have generated?
Unity did not publicly forecast the revenue impact. Estimates by analysts ranged from tens of millions to low hundreds of millions of dollars annualized at scale. The financial upside was material but not transformational for Unity; the trust cost was disproportionate to the financial gain even in the best-case execution scenario.
Did developers actually leave Unity?
Some did. Mega Crit (Slay the Spire) shifted to Godot, several other indie studios publicly committed to or made similar moves, and major mobile developers reduced their reliance on Unity for new projects. The aggregate exodus has been gradual rather than catastrophic — Unity remains a dominant engine — but the brand-equity damage and the increased willingness of developers to consider alternatives (Godot, custom engines, Unreal) is a structural cost the company has not yet fully absorbed.
Why was John Riccitiello let go?
Officially, Riccitiello “retired” from Unity. The timing — less than a month after the Runtime Fee disaster, after 22 days of public crisis — made the connection obvious. Riccitiello had also faced prior developer-community criticism for comments in a 2022 interview characterizing developers who did not consider monetization at design stage as “f***ing idiots.” The cumulative reputational position made his removal a natural part of the company’s recovery.
Has Unity recovered?
Partially. The Runtime Fee was officially canceled in September 2024 under new CEO Matt Bromberg, replaced with a subscription-pricing increase that was communicated transparently and applied prospectively. The developer community has not fully regained trust but has not abandoned the platform. The company’s stock price remained well below pre-controversy levels through 2024 and revenue growth was modest. Full recovery will take years if it happens at all.
What is the single-sentence takeaway?
For software embedded in a customer’s business operations, retroactive pricing changes destroy trust faster than any plausible revenue gain can compensate for — and trust takes years to rebuild.
Sources & references
- John Riccitiello steps down as CEO of Unity effective immediately following Runtime Fee controversy (Game World Observer) — Industry trade press coverage of the CEO transition.
- Unity CEO John Riccitiello resigns amid customer outcry (Fortune) — Fortune coverage of the resignation and the broader controversy.
- Unity Technologies CEO has stepped down after backlash (The Boar) — Post-mortem coverage of the developer reaction and corporate response.
- Unity Software Inc. Form 10-K, fiscal year 2023 (SEC EDGAR) — Unity’s annual filings showing the financial context of the period.
- Unity is canceling its controversial Runtime Fee (The Verge, September 2024) — The Verge coverage of the September 2024 cancellation under new CEO Matt Bromberg.