The editorial argues the surprising move isn't that Epic built a VCS, but that they open-sourced one they're actively using on the world's most demanding game. This distinguishes Lore from Microsoft's GVFS/Scalar (Git extensions) as a clean break with a credible production pedigree.
Argues that Git won source-code versioning so decisively that the industry forgot it lost the binary-asset war. Multi-GB FBX files and 50GB texture packs break Git's 'every clone is a full repo' mental model, and LFS papers over the gap without fixing the underlying architecture.
Contends Perforce kept its grip on AAA games despite famously bad UX because it correctly modeled centralized locking and lazy fetches from day one. Lore's bet is that if you replicate that workflow with modern ergonomics and open licensing, the moat collapses.
Submitted the Lore announcement which rocketed to 1,089 points within hours — unusual velocity for a tooling launch. The editorial reads this signal as evidence that ML model repos, design files, video production, and other binary-heavy workflows feel the same Git pain that games do.
Epic Games announced Lore, a new open-source version control system at lore.org, targeting the workflows that have made Perforce the default for AAA game development for the last three decades. The Hacker News thread hit 1,089 points within hours — unusual velocity for a tooling launch, and a signal that the friction Lore addresses is broadly felt outside of games too.
The pitch is specific: handle repositories in the multi-terabyte range, with millions of files, where a large share of the bytes are binary assets (textures, meshes, audio, video) that Git's content-addressable model handles badly. Lore advertises sparse checkouts, partial clones, locking semantics for un-mergeable binaries, and a server-authoritative model that looks more like Perforce or Plastic SCM than Git. Epic is positioning it as the system they're using internally on Fortnite and Unreal Engine — the same repos that have historically been the showcase Perforce uses in its own sales decks.
The interesting move isn't that Epic built a VCS — it's that they open-sourced one while still running the world's most demanding game on it. Microsoft did something similar with GVFS/Scalar for the Windows monorepo, but those tools were Git extensions. Lore is a clean break.
Git won the source-code war so completely that we forgot it lost the asset war. Anyone who has tried to put a 4GB FBX file or a 50GB texture pack into a Git repo has discovered the same thing: Git LFS is a workaround, not a solution. Pulls are slow, partial checkouts are awkward, and the entire mental model of "every clone is a full repo" breaks down past a few hundred GB. Perforce kept its grip on games not because of UX (the UX is famously bad), but because it correctly modeled centralized locking and lazy fetches from day one.
Lore's bet is that Perforce's moat is the workflow model, not the closed-source licensing — and if you replicate the workflow with modern ergonomics and zero per-seat cost, the moat evaporates. Perforce Helix Core licenses run roughly $1,500–$2,500 per seat per year at studio scale; for a 300-engineer studio, that's a $500K-$750K annual line item that has been impossible to justify ripping out because there's no real alternative. Plastic SCM (now Unity Version Control) made a run at this and got partial adoption, but it was never open and never had Epic's gravitational pull.
The community reaction in the HN thread split predictably. Game devs cheered the workflow specifics (locking, sparse checkouts, large-file streaming) — the things Git users routinely call "unnecessary" because they've never shipped a 200GB game. Web/backend devs asked why anyone would build a non-Git VCS in 2026. Both reactions are correct in their own context, which is exactly the point: Lore isn't trying to displace Git for the JS monorepo crowd. It's trying to displace Perforce for the people who never moved to Git in the first place.
There's also the Epic-vs-the-incumbents subtext. Epic has spent the last five years building an alternative stack to every major piece of game infrastructure it doesn't control: Epic Online Services vs. Steamworks, the Epic Games Store vs. Steam, Unreal vs. Unity. Lore vs. Perforce slots into that same playbook. The strategic logic is simple: if you control the engine, the store, the backend services, and the version control, you control the cost structure of every studio that ships on your platform.
If you're not in games, the immediate impact is zero — keep using Git. But there are second-order effects worth watching even from a web/backend seat.
First, monorepo tooling has been quietly converging toward Lore's model for years. Sparse checkouts, partial clones, virtual filesystems — Meta's EdenFS, Google's Piper, Microsoft's GVFS all exist because Git's full-clone assumption breaks at scale. If Lore's primitives are good enough and the project gets real momentum, expect parts of its design to leak back into general-purpose tooling, the same way Bazel and Buck leaked out of internal monorepos.
Second, CI/CD assumptions are about to get poked. Most CI systems are Git-shaped: they assume cheap clones, branch-per-PR, and merge-based history. A Perforce-style server-authoritative model with file locks doesn't fit those primitives well. If Lore takes off, expect GitHub Actions / GitLab CI / Buildkite to either build first-class support or watch a new generation of CI tooling spring up around it. CI vendors with a story for non-Git VCS will have a quiet competitive advantage.
Third, if you ship games or work with binary-heavy creative pipelines (ML model weights, video pipelines, design assets), this is worth a serious trial in 2026. The cost of staying on Perforce is measurable; the cost of trying Lore is a weekend. Run a pilot on a non-critical project, see how the team reacts, and benchmark workspace sync times against your existing P4 setup.
The open question isn't whether Lore is technically capable — Epic doesn't ship vaporware at this level. The question is governance. Is Lore actually open source in the sense that a competing studio can adopt it without giving Epic strategic visibility, or is it open-source-as-marketing in the Unreal-Engine-license sense? The license terms and the contribution model over the next six months will determine whether this becomes the new default for games or just another captive Epic tool with the source thrown over the wall. Either way, Perforce just had its worst Monday in thirty years.
Just today as I pushed some changes to Github, I was thinking how user-unfriendly Git's UI is: Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 10 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 290 bytes
This is a very promising announcement for Unreal game development specifically. For any other purpose I wouldn't care as much.Perforce definitely needs a challenger. It is not the incumbent because it is particularily simple to use or administer. Git is actually way simpler when it comes to bra
We had to use Perforce (Helix Core Cloud) at my last game studio, and it is the de facto industry standard that most of your creative staff is already familiar with. The programmers don't love it, but they don't rule the roost in games. It's also the safe, verified default for working
Turns out it is not really new but only open sourced it now. From the FQA.>Lore, formerly called Unreal Revision Control, is the built-in version control system for UEFN (Unreal Editor for Fortnite), where creators have been using it to version their islands. It is also seeing progressive adoptio
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
For context, since a lot of people on HN haven't worked on games - this is not intended to compete with Git for general software development. This is a competitor with Perforce for game development.Git is fine for text based files like code, but it's really bad at stuff like textures, 3D m