Fenris Creations, the studio most of us still call CCP Games out of habit, just did something rare for a live-service operator: it handed over the engine. Carbon, the framework that has run EVE Online for more than two decades and now powers EVE Frontier, is fully open source. Trinity (graphics), Destiny (physics and pathfinding), networking, UI, audio, the scheduler, all of it is on GitHub, commit history intact back to 2014, mostly under MIT license.
CCP first floated this back in March 2024, alongside the reveal of Project Awakening, a single-shard, UGC-driven project. That pairing was the real tell. Open-sourcing Carbon was never pitched as a developer-relations gesture. It was positioned as the technical foundation for a co-creation strategy. Hilmar Veigar Pétursson talked about Carbon coming to “belong to the world” and made the Linux comparison directly: open, shared code tends to be more durable over time. That’s a bold claim to make about a live-service MMO engine, a category where almost nobody tests that theory in public.
Two years later, the execution landed, and the framing got sharper. Ben Hunter, now Senior Development Director for Core Technology, described the release as making Carbon’s foundation “visible, understandable, and useful to others,” and tied it back to CCP’s early decision to expose EVE’s API to players. First they opened the API. Now they’ve opened the engine.
Fenris’s own Carbon page frames the engine less like documentation and more like mythology. The header line calls it the platform “igniting EVE’s potential,” and the copy describes Carbon as the tool behind “tens of millions of player journeys” through an “emotion invoking” universe. They’re not selling Carbon as middleware. They’re selling it as the infrastructure behind what they call the world’s largest living work of science fiction.
The Carbon Engine Framework
Under Featured Projects, Scheduler is a Python extension providing Stackless-like deterministic scheduling and channel messaging for Greenlet coroutines, enabling predictable tasklet scheduling on vanilla CPython builds. The spatial audio object clustering tool is a Wwise plugin that dynamically groups and manages spatial audio objects by proximity, cutting down system audio-object load in complex scenes. Core is the C++ foundation library that standardizes how Carbon talks to hardware and operating systems. Resources handles managing, manipulating, and delivering resource files for Carbon titles. IO is an async networking library built on Scheduler and greenlets, exposing a standard Python 3 socket API as a drop-in replacement for Python’s own socket module. Math is a lightweight library of vectors, matrices, quaternions, and geometry utilities for graphics and simulation work.
Under Core Engine Components, Trinity, billed as “the artists’ playground,” is the graphics engine behind Carbon’s large-scale space environments. Destiny, “choreographing the dance of stars,” handles physics and pathfinding and is credited with two Guinness World Records: the largest multiplayer PvP battle at 8,825 players, and the most concurrent participants in a multiplayer PvP battle at 6,557. CarbonUI, “guiding players’ journey,” is the interface framework that helps bring millions of players together across varied universes. CarbonIO, “the pulse of the universe,” handles networking and keeps persistent worlds running reliably at scale. CarbonAudio, “tuning in to immersion,” manages audio logic for massive multi-thousand-player scenes. And Scripting, “creativity unbound,” is Carbon’s Python-based scripting layer, which the site positions as the foundation for building out gameplay experiences.
What’s actually in the release
The release includes more than two dozen modules built and refined over roughly twenty years. Community members have already started submitting security fix pull requests, and there’s early chatter about someone building a web app around EVE content. Hunter has said adoption is currently “leaning toward” people using Carbon to build within the EVE ecosystem itself, though he’s said the door is open to anything.
Worth noting: Fenris isn’t walking away from proprietary engines elsewhere. Eve Vanguard, their upcoming shooter, is built in Unreal because, in their own words, Epic’s engine is simply better suited to that genre. So this isn’t a company converting to open source across the board. It’s a decision specific to Carbon, specific to the kind of persistent, high-population world it was built for.
My take
This is a twenty-year-old engine that has been proprietary the entire time, released in one clean shot rather than in stages, with commit history intact. That’s a meaningful level of transparency for a studio to commit to, especially one whose entire business still runs on the game this engine powers. The near-term impact is probably contained to the EVE community and researchers or educators who want to study a proven MMO architecture. The bigger question is whether other long-running live-service studios facing their own engine decisions look at this and see a repeatable move, or see something that only makes sense because EVE’s twenty-year operating history is unusual to begin with.