On Tuesday, Unity Technologies announced a new “Unity Runtime Fee” — a charge that kicks in when games built with Unity exceed certain install thresholds. Starting January 1, 2024, developers using Unity Personal and Unity Pro would owe Unity between $0.01 and $0.20 per install after crossing revenue and install count thresholds. The backlash has been immediate, severe, and entirely predictable. As someone who has watched platform dynamics play out across many domains over three decades, this is a masterclass in how to destroy developer trust.
The Policy and Why It’s Problematic#
The details matter here, and they’re worse than the headline suggests. Unity plans to track installs using their own proprietary data model — not sales, not revenue, but installs. That means reinstalls count. Installing on a new device counts. If your game goes free-to-play and gets millions of installs but monetizes poorly, you could owe Unity more than you earn.
The thresholds vary by tier: Unity Personal users would start paying after $200K in trailing twelve-month revenue and 200K lifetime installs. Unity Pro and Enterprise have higher thresholds but the per-install fees still apply. For successful indie games, the math gets alarming quickly. A game with 10 million installs could owe Unity hundreds of thousands of dollars — retroactively, for games already built and shipped under the previous licensing terms.
That retroactive application is perhaps the most egregious aspect. Developers made business decisions — chose an engine, built their game, signed publishing deals — based on Unity’s existing pricing model. Changing the terms after the fact, for software already in the market, violates a fundamental principle of platform trust.
The Broader Platform Lesson#
This isn’t just a game development story. It’s a cautionary tale for every developer who builds on a proprietary platform. The pattern is familiar: a platform grows by being developer-friendly, achieves market dominance, then changes the terms to extract more value from its captive user base.
We’ve seen variants of this across the tech industry. Oracle’s aggressive licensing changes after acquiring Sun. Docker’s pricing adjustments that caught many organizations off guard. Twitter’s API pricing that killed an ecosystem of third-party apps. The common thread is that platforms eventually optimize for revenue extraction over ecosystem health.
What makes Unity’s move particularly striking is the timing and severity. The company has been struggling financially — their stock is down significantly from its highs, they’ve had layoffs, and the merger with ironSource has been controversial. This fee structure looks like a desperate attempt to find new revenue, implemented by people who don’t understand (or don’t care about) the downstream effects on their developer community.
What Developers Are Doing#
The response from the Unity developer community has been extraordinary. Multiple game studios have publicly stated they’re evaluating alternatives. Cult of the Lamb’s developer Massive Monster, Innersloth (Among Us), and Aggro Crab (Going Under) have all spoken out. Some developers are threatening to pull their games from storefronts rather than pay the fee. Others are already beginning the painful process of evaluating engine switches.
Godot Engine, the open-source game engine, has seen an enormous surge in interest. Their Twitter account gained tens of thousands of followers in days. Unreal Engine, Epic’s proprietary but more predictably priced alternative, is also getting renewed attention.
But switching engines isn’t like switching text editors. Game engines are deeply embedded in a development team’s workflow, tools, expertise, and existing codebases. A mid-project engine switch is essentially starting over. Even for new projects, the switching cost includes retraining your team, rebuilding your tool pipeline, and accepting a productivity dip that could last months or years.
This is exactly the kind of lock-in that makes platform changes so insidious. The cost of leaving is so high that many developers will stay and absorb the fee, even if they resent it. Unity is counting on that calculus.
The Open Source Alternative#
The surge of interest in Godot Engine deserves special attention. Godot has been steadily improving for years, and its 4.0 release earlier this year brought significant graphics and performance improvements. It’s MIT-licensed, meaning it’s free to use, free to modify, and free from the kind of licensing ambush Unity just pulled.
Could Godot replace Unity for all use cases today? Honestly, no. Unity’s ecosystem of assets, its mobile deployment pipeline, and its tooling maturity still have advantages for many projects. But the gap has been narrowing, and Unity just gave Godot the biggest marketing boost it could have asked for.
I’ve always been an advocate for open-source infrastructure in development workflows. Not because proprietary tools are inherently bad — they often provide excellent experiences — but because open-source tools can’t pull the rug out from under you. When your business depends on a tool, the license under which you use that tool is a strategic concern, not just a legal technicality.
My Take#
I think Unity will walk this back. The backlash is too severe, the developer exodus too visible, and the PR damage too deep for them to push through the current proposal unchanged. We’ll likely see revised thresholds, exemptions for existing games, and softer language within weeks.
But even a full reversal won’t fully repair the trust. The message has been sent: Unity’s leadership is willing to retroactively change terms to extract revenue from their developer base. Even if this particular policy is softened, developers will — and should — factor that willingness into their platform decisions going forward.
The lesson for all of us, whether we build games or web apps or cloud services, is clear: be thoughtful about your dependencies. Evaluate not just the technical capabilities of your platforms, but the business incentives of the companies behind them. And when viable open-source alternatives exist, give them serious consideration. The price you’re not paying today might be the leverage you’ll wish you had tomorrow.
I don’t build games, but I recognize the dynamic. Every time I choose a framework, a cloud provider, or a development tool, I’m making a bet on the future behavior of the organization behind it. Unity just reminded all of us why that bet matters.