DayZ Creator's BRUTAL C# Framework Goes Open Source — a Bet Against Engine Lock-In
RocketWerkz open-sourced BRUTAL, its C# game framework: free commercial use, no royalties, low-level graphics access — a post-Unity-Runtime-Fee bet on developer trust.
Dean Hall's BRUTAL C# framework is now open source
RocketWerkz — the studio founded by DayZ creator Dean Hall — has open-sourced BRUTAL, the C# game-development framework it built for its own projects. The release, announced October 20, gives developers a free, royalty-free alternative to Unity, Unreal, and Godot, with low-level graphics access and no revenue share. It's already trending on GitHub with nearly 1,900 stars since its October 14 debut.
BRUTAL combines C# and .NET with C++ libraries and low-level graphics access. Think of it as a foundation layer: instead of handing you a full editor and asset pipeline like Unity, it gives you the building blocks to construct your own development tools. RocketWerkz has been dogfooding it in Kitten Space Agency, and there's already an external case study — Ludeon Studios ported RimWorld off Unity onto a new engine called Waylith, citing better performance and faster startup times.
Why the timing is perfect
Nobody open-sources a game framework in a vacuum. Two industry traumas made this release land the way it did. First, the Unity Runtime Fee saga, which shattered developer trust in Unity's business model and sent studios hunting for exits. Second, Epic's announcement that it would deprecate Unreal's Blueprints visual scripting, which rattled the many teams that built their workflows around it.
Developers are now pricing engine risk the way they price any other dependency: what happens to my project if the vendor changes the deal? An open-source framework you can fork answers that question permanently. That's the bet BRUTAL is making.
The license: free, but not quite MIT
The terms are generous with one catch. BRUTAL is free to use in commercial games with no royalties — ship a hit, keep all of it. But the open-source license requires attribution and displaying a logo before gameplay when players load your game. That's a splash-screen tax, essentially: free engine, mandatory credit roll.
For indie studios, that's a trivial price. For larger studios, the logo requirement is a marketing conversation, not a blocker. Compare it with Unreal's 5% royalty after $1M in revenue or Unity's per-install fee structures, and BRUTAL's deal looks very good indeed — assuming the framework itself holds up in production, which only time and shipped games will prove.
What developers should actually evaluate
A framework is not an engine, and the distinction matters. BRUTAL gives you low-level access and building blocks; it does not give you Unity's editor, asset store, or hiring pool. Adopting it means building more of your own tooling — which is exactly what experienced teams want and exactly what small teams dread.
The smart evaluation looks like this: if your team already maintains custom tooling and chafed under Unity's or Unreal's constraints, BRUTAL is worth a serious prototype. If you're a small team that depends on an engine's editor and ecosystem, the open-source Rust clones of Adobe's apps show the same pattern — open source gives you freedom, but freedom is work. And if you're choosing version control and CI for the experiment, Git 2.56's new cleanup tools pair nicely with the "stop your agents breaking things" ethos.
The bigger signal is cultural. When the creator of one of the most successful survival games ever decides the industry needs another open framework — and when a studio like Ludeon actually ships a port away from Unity — the engine wars aren't over. They're just moving to a new battlefield: trust. NVIDIA open-sourcing its $800M Run:ai scheduler made the same point in AI infrastructure. The vendors who win the next decade will be the ones developers believe won't change the deal mid-project.


