Epic Games has released Lore, an open-source, centralized version control system (VCS) designed to handle large binary files alongside source code. Built to support the development of Fortnite and Unreal Engine, Lore treats all data as opaque byte streams, aiming to solve performance bottlenecks common in systems like Git or Perforce when managing massive game assets.
Why Epic Games Developed Lore
Epic Games created Lore to address specific limitations the studio encountered while scaling its development pipelines. According to the official Lore documentation, existing version control systems often force a trade-off between managing code and managing large-scale binary assets.
While tools like Git are industry standards for source code, they struggle with large binary files, often causing repository bloat and slow clone times. Conversely, Perforce—a common choice in the gaming industry—often requires frequent server round-trips that can introduce latency in large-scale environments. Epic designed Lore to be "sparse-by-construction," meaning it only downloads the specific fragments of data required by the client, significantly reducing network overhead.
How Lore Differs from Git and Perforce
The primary technical differentiator for Lore is its "binary-first" architecture. Most version control systems are designed around text-based diffing, which treats code as the primary data type and binary files as secondary attachments.
| Feature | Git | Perforce | Lore |
|---|---|---|---|
| Binary Handling | Secondary | First-class | First-class |
| Architecture | Distributed | Centralized | Centralized |
| Storage Strategy | Full history | Server-side | Content-addressed |
As noted in the system design, Lore treats all content as opaque byte streams on the "hot path." Text-aware features are layered on top rather than being baked into the storage or transport logic. This ensures that a 10GB 3D asset receives the same performance priority as a small script file. Furthermore, Lore utilizes an MIT License, a move that contrasts with the copyleft requirements of systems using the GNU General Public License, providing more flexibility for proprietary integrations.
Performance and Scalability Goals
Lore aims to solve the "multi-tenancy" problem that often plagues large development studios. In many centralized systems, infrastructure bottlenecks can allow one user’s heavy traffic to degrade performance for others. Lore’s architecture is intended to ensure that users on the same infrastructure remain isolated, preventing a single developer’s large pull request from impacting the entire team’s workflow.
The system also eliminates "partially-applied revisions," a state where a repository might contain a mix of old and new files during an update. By ensuring that in-between states remain invisible to readers, Lore aims to keep development environments stable, even during massive asset synchronization.
Who Should Use Lore?
While purpose-built for game development, the design of Lore makes it relevant for any sector dealing with large-scale machine-readable data. Industries such as AI model training, where developers must version-control massive datasets alongside model architecture code, may find Lore’s binary-first approach more efficient than traditional Git-based workflows.
Epic Games has made Lore available for Windows, macOS, and Linux. Detailed documentation and quick-start guides are hosted on the official Lore website, while the source code is currently maintained via a public repository on GitHub.