In a landmark shift for the gaming industry, Fenris Creations—the developer formerly known as CCP Games—has officially released its proprietary "Carbon" game engine as an open-source project on GitHub. This move marks the culmination of a two-year transition, transforming the tech stack that has powered the sci-fi juggernaut Eve Online for over two decades into a publicly accessible resource. By embracing a largely MIT-licensed model, Fenris is inviting developers, modders, and technophiles to inspect, fork, and contribute to the very foundation of one of the most resilient virtual worlds in history. Chronology of a Transformation The journey to open-source Carbon began in 2024, when the studio, then operating as CCP Games, first signaled its intent to democratize its development platform. For a studio historically known for maintaining a "walled garden" around its complex codebase, the announcement was met with skepticism and curiosity in equal measure. The Announcement (2024): The studio publicly committed to the open-source path, citing a need for greater transparency and community trust. The Quiet Phase (2024–2025): For nearly two years, the core technology team at Fenris engaged in a "slow burn" preparation. This involved untangling two decades of proprietary middleware, licensing agreements, and legacy code. The Final Push (2026): The last 12 weeks of the project saw an intensive sprint to finalize the codebase for public consumption, ensuring that the engine was not only readable but usable for external developers. The Launch (Current): Carbon is now live on GitHub, with the studio actively integrating community-submitted pull requests (PRs) into its workflow. The Philosophy of "Rising Tides" At the heart of this decision is Ben Hunter, Fenris Creations’ senior development director for core technology. According to Hunter, the move is less about relinquishing control and more about fostering a collaborative ecosystem. "We arrived at this point two and a half to three years ago, where we decided there’s nothing really special about our sauce in terms of the actual code," Hunter explains. "We, and the community, would be better served by actually getting it out there, having more eyes on it, so that we can actually learn and grow from that." This "rising tides" philosophy suggests a shift in how mid-to-large-sized studios perceive proprietary tech. By allowing the community to stress-test and improve the engine, Fenris aims to benefit from collective intelligence. The studio isn’t looking for a direct revenue stream from the engine itself; rather, they are betting on a future where the Eve ecosystem grows through external innovation, much like the early days of Eve Online when the company first exposed its Application Programming Interface (API) to third-party developers. Technical Architecture and Licensing Fenris has been meticulous in how it handled the legal and technical "carving out" of the engine. The majority of Carbon is distributed under the MIT License, which is among the most permissive in the open-source world, allowing users to modify, distribute, and even commercialize their creations without paying royalties to Fenris. However, the architecture is modular. Two specific components required a different approach: Spatial Audio Clustering: Covered by the Apache License 2.0. IO Modules: Governed by the Python Software Foundation License. The separation of these modules was a significant engineering hurdle. The team had to distinguish between what constituted "core engine code" versus the two decades of peripheral middleware that had accreted around Eve Online. Sensitive elements—most notably the proprietary code governing the game’s complex, multi-million-dollar in-game economy—were strictly excluded from the open-source release to protect the integrity of the Eve market. Security in an Open Environment One of the most pressing concerns for any studio releasing its source code is the risk of bad actors identifying and exploiting security vulnerabilities. For an engine that has been "battle-hardened" over 23 years of continuous operation, this is not a trivial risk. Hunter acknowledges the challenge but views it as a net positive. "The holes that were there would have been there anyway," he notes. "Actually having the ability to have third parties contribute to and help us close any potential security gaps is very good." Remarkably, the team reports that since the code has been available, the number of security-related PRs has been minimal. This is a testament to the decades of infrastructural work done to secure the networking layers of Eve Online, which have historically been targeted by those seeking to disrupt large-scale fleet battles. Moving forward, the studio has built security reviews directly into their "sprint process," treating every external contribution with the same, if not higher, level of scrutiny as internal code. Governance and the Godot Influence When Fenris sought to build a framework for managing an open-source project at this scale, they turned to the developers of the Godot engine. The rise of Godot as a community-governed alternative to Unity and Unreal provided a blueprint for how to structure a project that values longevity over short-term monetization. "The main conversations were around governance models," Hunter says. The most vital lesson learned from Godot was the importance of a "plug-in architecture." By decoupling the engine’s core from its tooling, Fenris is creating a surface area that is easier for contributors to manage. This transition to a plug-in-based system is currently underway and will be a centerpiece of future updates to the Carbon codebase. Furthermore, Fenris has established clear guidelines for contributions, including a requirement that developers disclose if they have used Large Language Models (LLMs) in the creation of their code. While the studio is open to AI-assisted development, they mandate transparency so that code can be subjected to appropriate levels of scrutiny. The Industry Shift: AI and the Future of Engines The timing of Carbon’s release aligns with a broader, industry-wide re-architecting. With Epic Games pushing toward the "LLM era" with Unreal Engine 6 and the introduction of new languages like Verse, the landscape is becoming increasingly complex. Fenris is positioning itself not as a competitor to these monolithic engines, but as a specialized, community-driven alternative. "There’s a lot of re-architecting going on at the moment," says Hunter. "The biggest part of this is figuring out the most useful way to integrate or utilize LLMs for workflows." Fenris is already developing an internal "tools gateway" for LLM integration, which they plan to open-source once it has passed the testing phase. Implications: The Next Five Years What does the future hold for Carbon? In the short term, Fenris is focused on creating a "test project"—an example game that serves as a sandbox for developers to understand the engine’s architecture without needing to navigate the immense complexity of the full Eve Online client. In the long term, the ambition is grander. Fenris envisions a vibrant ecosystem of "Eve-centric" applications. Just as the release of the Eve API in the early 2000s led to the creation of essential tools for character management and ship fitting, the release of the Carbon engine provides the infrastructure for a new generation of builders. "I would like to see it contributing to the Eve universe as a whole," Hunter concludes. By betting on the community, Fenris Creations is attempting to secure the legacy of its engine, ensuring that even if the studio’s focus shifts, the technological foundation of its virtual universe remains open, improvable, and eternal. Whether this will lead to a new wave of space-faring MMOs or simply a more robust Eve Online remains to be seen, but one thing is clear: the era of the closed-source engine is under pressure, and Fenris has chosen to lead the charge into the open. Post navigation MobyGames Pivots to Professional Networking: Can Atari’s Database Become the "IMDbPro" of the Gaming World?
