Lore is Epic’s newly open sourced version control system for asset-heavy development. It is centralized by design, not a distributed Git clone, and it targets the problems common in game production: terabyte-scale repos, non-mergeable binary assets, file locking, sparse or on-demand workspaces, and finer-grained permissions than a whole-repo boundary. Epic says it grew out of Unreal Revision Control used in Unreal Editor for Fortnite and is moving into broader internal use, which made people take it more seriously than a greenfield side project.
The main conclusion was straightforward: this is a
Perforce challenger, not a general software VCS. People with game experience kept repeating that Git works well for source code but falls apart once most of the repository is textures, models, audio, baked assets, and other binaries that cannot be merged sensibly.
Git LFS got almost no defenders. It was described as brittle, expensive on GitHub, awkward to configure across teams, and fundamentally bolted onto a model that was never built for huge mutable binary assets. Perforce still dominates because it handles locking, permissions, partial syncs, and engine integration, especially in Unreal, even though almost everyone agreed it is archaic and painful to run.
That left Lore landing in a very specific opening. The features people cared about were chunked storage for binary files, on-demand
hydration and sparse workspaces, centralized locks, and the possibility of first-class Unreal support because Epic controls the engine. Several commenters said that alone could matter more than the storage design. Perforce is entrenched partly because Unreal workflows, plugins, and adjacent tools assume it. If Epic gives Lore that same level of support, adoption becomes plausible in studios that already tolerate Perforce only because the alternatives are worse.
The skepticism was also specific. A lot of people disliked the docs, calling them obviously LLM-written and too sloppy for a version control system where edge cases matter. Others pointed out that the desktop client is not open source yet, despite “fully open source” language on the site. Some questioned whether anyone should trust Epic to maintain infrastructure that is not core to its business, or worried this could become another Unreal lock-in lever even with an
MIT license. But even many skeptics still conceded that the problem is real, Perforce is overdue for competition, and a credible open source system aimed squarely at binary-heavy workflows would be a meaningful development if Epic follows through.