Lore is Epic Games’ open-source version control system, written in Rust and released under MIT in May 2026. The reason it shot onto trending is the name on it: Epic builds Unreal Engine and Fortnite, so a version control system from them is aimed squarely at a problem most VCS tools handle badly, which is repositories where the code is small and the binary assets are enormous.

Before you evaluate it, get one fact straight that the README states plainly but a Git user might skim past: Lore is centralized and content-addressed, closer in shape to Perforce than to Git. There is a server. Workspaces hydrate file data on demand rather than cloning everything. If your mental model is “distributed, everyone has the full history,” that does not apply here, and that is deliberate.

What it is built for

Game and film projects routinely carry hundreds of gigabytes of textures, meshes, audio, and capture data alongside their source. Git chokes on that, git-lfs is a bolt-on, and the established answer in studios has been Perforce. Lore is Epic’s open take on that same job:

  • Content-addressed storage stores and references data by content hash in a Merkle tree, so comparisons, integrity checks, and reuse across branches and history are cheap.
  • Chunked storage for large files keeps files as reusable, indexed chunks, so a small edit to a huge asset transfers and dedupes efficiently.
  • On-demand hydration and sparse workspaces let a workspace stay small by fetching file data only when needed, which is the feature that makes a multi-terabyte repo usable on a laptop.
  • Immutable revision chain derives each revision’s hash from its state plus its parents, giving a tamper-evident history.
  • Centralized service with caching sits in front of durable storage to scale throughput for large teams.

There are official SDKs for JavaScript, Python, C#, and Go, plus the core library, server, and CLI in this repo, so it is designed to be integrated into tooling rather than only driven by hand.

Install and try it

The quickest look is demo mode, which spins up a local server:

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.sh | bash -s -- --demo
# Windows
$env:LORE_DEMO=1; irm https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.ps1 | iex

From there the quickstart walks you through your first commit. The CLI is described as a one-to-one surface for the full functionality, so there is no required GUI yet (a desktop client is on the roadmap).

The caveats that decide whether you should wait

This is where you need more than the README’s bullet list.

It is pre-1.0 and says so. The on-disk formats, interfaces, and APIs may change between releases. For a version control system, the on-disk format changing is not a small footnote, so treat early adoption as experimentation, not as a place to park a studio’s only copy of a shipping project.

There is no supported way to migrate an existing Git repository in yet. This is the single most-requested item in the issue tracker at the time of writing, and its absence matters: you cannot simply bring your history over, so evaluation today means starting fresh or scripting your own import.

The headline use case is not fully wired even inside Epic. Lore is the built-in VCS for UEFN (Unreal Editor for Fortnite), but the README is candid that the open-source tooling cannot talk to the UEFN build yet, because UEFN uses a proprietary compression format that cannot ship with the open project. Epic says it is moving UEFN onto the same open format this project uses to close that gap. Until then, the most concrete real-world workflow people will search for is still in progress.

Smaller operational gaps show up in issues too: there is no official Docker Compose example for standing up the server yet, and musl libc prebuilt Linux binaries have been requested. Both are the kind of thing that makes self-hosting smoother once they land.

Lore vs the alternatives

SystemModelBest atNote
LoreCentralized, content-addressedCode plus huge binary assets, open sourcePre-1.0, Rust, MIT
Git + git-lfsDistributed + pointer filesSource code; binaries via add-onUbiquitous, but large assets are awkward
Perforce (Helix Core)CentralizedThe incumbent for game and film studiosProprietary, the thing Lore is implicitly answering
Diversion / Plastic SCMCentralized/cloudLarge-asset teams wanting Perforce alternativesCommercial

The honest one-liner: if you came here hoping to replace Git for your source-only project, Lore is not aimed at you. If you maintain a project where multi-gigabyte binaries are the actual problem, this is Epic putting a serious, open contender into a space that has been proprietary for a long time.

FAQ

Is Lore free and open source? Yes. It is MIT licensed, with the core library, server, and CLI in this repository and language SDKs alongside it.

Is Lore like Git? Not really. Lore is centralized and content-addressed with a server and on-demand workspace hydration, which is closer to Perforce than to Git’s distributed model. It targets repositories dominated by large binary assets.

Can I migrate my Git repository to Lore? Not through a supported tool yet. A migration path is the top community request as of 2026-06, so for now evaluation means starting a fresh repo or writing your own import.

Is Lore production-ready? It is pre-1.0 and the on-disk formats and APIs can change between releases, so it is best treated as early and experimental rather than a system of record for a shipping project today.

Does Lore work with UEFN / Unreal? Lore is the built-in VCS for UEFN, but the open-source build cannot talk to UEFN yet because of a proprietary compression format. Epic says it is moving UEFN onto the open format to close that gap.