gitwtfhub

wtf is lore?

epicgames/lore — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2026-06-26

7,636RustAudience · developerComplexity · 4/5ActiveLicenseSetup · moderate

TL;DR

Open-source version control system by Epic Games built for projects mixing code with large binary assets, like game and film production, where Git struggles.

Mindmap

mindmap
  root((lore))
    What it does
      Version control
      Handles large binaries
      Chunked storage
    Tech Stack
      Rust
      JavaScript SDK
      Python SDK
      C sharp SDK
    Use Cases
      Game asset management
      Film production pipelines
      Unreal Editor for Fortnite
    Audience
      Game studios
      Entertainment companies

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Manage gigabytes of textures, 3D models, and audio alongside source code for a game built in Unreal Engine.

REASON 2

Sync only the files a team member actually needs instead of downloading the full asset history.

REASON 3

Create and switch branches cheaply to experiment on large binary assets without duplicating shared files.

REASON 4

Integrate version control into an existing production pipeline using the JavaScript, Python, C#, Go, or C/C++ SDKs.

What's in the stack?

RustJavaScriptPythonC#GoC/C++

How it stacks up

epicgames/loreekzhang/sshxwealthfolio/wealthfolio
Stars7,6367,4667,422
LanguageRustRustRust
Last pushed2026-06-26
MaintenanceActive
Setup difficultymoderateeasyeasy
Complexity4/52/52/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 1h+

Requires running a centralized server, still pre-1.0 so interfaces and file formats may change between releases.

MIT license. Free to use, modify, and redistribute including for commercial purposes, with attribution.

Wtf does this do

Lore is an open source version control system built by Epic Games, designed specifically for projects that mix code with large binary assets, think game development, film production, and similar creative workflows. If you've ever tried managing gigabytes of textures, 3D models, or audio files alongside source code, you know that traditional tools like Git struggle badly. That's the problem this project aims to solve. At a high level, it works as a centralized system where all your project files live on a server that your team syncs to and from. Instead of downloading the entire repository history or every asset up front, it only pulls what you actually need when you need it, so your local workspace stays lightweight. Files are broken into reusable chunks, meaning if two branches share most of the same large files, the system doesn't duplicate them. Branches are cheap to create and switch between, which encourages experimentation. It also keeps a tamper-evident history, so you can trust that revisions haven't been silently altered. The primary audience is game studios and entertainment companies where artists and developers need to collaborate on massive projects. For example, a team building a game in Unreal Engine or a studio producing animated content would use this to manage everything from source code to high-resolution character models. It's already the built-in version control for Unreal Editor for Fortnite, though the open source version and that internal build aren't fully interoperable yet due to a compression format mismatch Epic is actively resolving. The project is written in Rust and provides SDKs for several languages, JavaScript, Python, C#, Go, and C/C++, so teams can integrate it into existing pipelines. It's still pre-1.0, so interfaces and file formats may change between releases. That said, it's fully open source under MIT license, and Epic is actively developing it with a public roadmap.

Yoink these prompts

Prompt 1
Explain how lore's chunked storage avoids duplicating large binary assets shared across branches.
Prompt 2
Show me how to set up a centralized lore server that my team can sync large game assets to and from.
Prompt 3
Help me integrate lore into my existing pipeline using the Python SDK.
Prompt 4
Walk me through why lore handles gigabyte-sized textures and 3D models better than Git for a game project.
Prompt 5
Explain the current compatibility gap between the open-source lore project and Epic's internal Unreal Editor for Fortnite build.

Frequently asked questions

wtf is lore?

Open-source version control system by Epic Games built for projects mixing code with large binary assets, like game and film production, where Git struggles.

What language is lore written in?

Mainly Rust. The stack also includes Rust, JavaScript, Python.

Is lore actively maintained?

Active — commit in last 30 days (last push 2026-06-26).

What license does lore use?

MIT license. Free to use, modify, and redistribute including for commercial purposes, with attribution.

How hard is lore to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is lore for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.