Epic Games Lore: Open-Source Version Control for Game Development

Epic Games just dropped Lore, an open-source version control system purpose-built for game development. It's not trying to kill Git; it's taking on Perforce, the industry standard for managing massive binary assets like textures, 3D models, and audio files. The HN thread lit up with 233 points and 126 comments, and for good reason—this could reshape how teams collaborate on non-text content.

Lore: Epic Games' Take on Game Development Version Control

Lore is a version control system designed from the ground up for game development workflows. It handles large binary files efficiently, supports exclusive file locking (so artists don't step on each other's toes), and exposes a "full-surface API" that lets you integrate it programmatically—something Git deliberately avoids. The project is open-source under a permissive license, and its repository already includes Architectural Decision Records (ADRs) that document key design choices, like the decision to implement JavaScript bindings.

Lore website

Epic Games, the company behind Unreal Engine and Fortnite, has dogfooded Lore internally before releasing it. The competition is clear: Perforce, which has been the go-to for game studios despite its complexity and cost. Lore aims to be simpler, more modern, and free.

Why Lore Is Trending on Hacker News

The HN crowd immediately grasped the niche. One commenter wrote:

"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."

This sentiment dominated the thread. Developers who have suffered with Git's handling of binary files—bloating repositories, no easy locking—saw Lore as a breath of fresh air. Another commenter echoed the pain:

"Just today as I pushed some changes to Github, I was thinking how user-unfriendly Git's UI is..."

The frustration is real. Git's chatty output and opaque internals are a barrier, especially for non-developers like artists. There was skepticism about the name—"I'd trust this project more if it was named Data"—but the overall tone was cautiously optimistic. The presence of ADRs earned points for transparency.

My Take on Lore's Full-Surface API and Exclusive Locking

I've worked with Git and Perforce, and I've seen how much friction binary assets cause. Git simply wasn't made for this. Its delta compression and diff algorithms assume text, and its locking model is nonexistent. Perforce solves those problems but at a cost—both monetary and in complexity. Lore looks like a deliberate attempt to offer a Perforce-like experience without the baggage.

The full-surface API is a smart move. Git's porcelain/plumbing distinction is powerful but intentionally not a stable library. By providing a proper API, Lore enables tooling and integrations that could make it a platform, not just a tool. That's a big deal for build pipelines and custom workflows.

Adoption will be tough. Perforce is entrenched in game studios, and migrating isn't trivial. But Epic's weight behind Lore—and its open-source nature—could tip the scales. The game development community is tight-knit; if a few high-profile studios switch, others will follow.

What Lore's API Means for Builders

If you work with large binary files—game assets, CAD models, video files—you should evaluate Lore. Its exclusive locking model is a game-changer for collaborative editing. Here's a quick contrast:

Git with a large binary file:

git add texture.psd
git commit -m "add texture"
git push
# Repository size balloons, merge conflicts are unreadable

Lore with same file:

lore lock texture.psd  # Prevent others from editing
lore commit -m "update texture"
# Efficient storage, no merge nightmare

For game developers, this reduces the friction between code and content. You can keep code in Git and assets in Lore, or unify everything in Lore. The ADRs provide insight into the design decisions—worth reading if you're building similar systems.

Architectural Decision Records

For DevOps, the full-surface API means you can script complex operations without parsing messy stdout. That's a huge win for automation.

Should You Switch to Lore for Binary Files?

If you're a game developer or work with large binary assets, Lore is worth a serious look. It addresses real pain points that Git and Perforce leave unaddressed. If you're a general software developer, you can probably stick with Git—but watch Lore for ideas that might trickle into other tools. Either way, Epic's move to open-source this signals a shift: version control is no longer one-size-fits-all.

---

HN discussion: https://news.ycombinator.com/item?id=48571081

Original announcement: https://lore.org/

Perforce: https://www.perforce.com/

Related HN thread on Git UI complexity: https://news.ycombinator.com/item?id=48470604