Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Lore (Epic Games)
Epic Games' centralized, content-addressed VCS for code plus large binary assets (chunked storage, on-demand hydration, sparse workspaces); originally Unreal Revision Control, built into UEFN.
Open-sourced 2026-06 (repo created 2026-05-21, Phoronix 2026-06-17); v0.11.0 released 2026-10-22 (GitHub API). Pre-1.0. (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How is it mainly sustained? big company side project (13% of 16 others)
- Who is it for? both (5% of 20 others)
- How does it relate to git repositories? own storage format, one-time import or no git interop (21% of 19 others)
- What size of project is it designed for? very large monorepos or large binary assets (21% of 19 others)
What it shares with most of the community
- Is it actively maintained? active (90% of 20 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (53% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (67% of 18 others)
- Can you commit, branch, and read history with no network connection? yes (94% of 17 others)
- Is it designed with AI coding agents in mind? no (65% of 20 others)
- What is the basic unit of history? (pick the most specific that applies) snapshots (commits) with no identity that survives a rewrite (74% of 19 others)
- How are merge conflicts mainly handled? must be resolved before the merge or commit completes (65% of 17 others)
Not documented
The public sources we read don't say:
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow?
Nearest neighbors
- Mercurial 69% of 16 shared answers match
- Fossil 67% of 15 shared answers match
- Sapling 63% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) MIT; the desktop client is not open source yet (depends on proprietary components). | source 2026-10-25 |
| How is it mainly sustained? | stands apart big company side project | source 2026-10-25 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes Local mode is a single executable; team server is self-hostable. | source 2026-10-25 |
| Do you need an account to use it? | no account Open-source CLI and self-hostable server; everyday ops need no network. | source 2026-10-26 |
| Who is it for? | stands apart both 'Developers and artists alike'. | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Own content-addressed store; no git interop. | source 2026-10-26 |
| How does it relate to git repositories? | stands apart own storage format, one-time import or no git interop No git interop documented. | source 2026-10-25 |
| Where does the authoritative copy of a project live? | one central server per project (hosted or self-hosted) Central 'server-of-record for durability, access control, and conflict resolution'. | source 2026-10-25 |
| Can you commit, branch, and read history with no network connection? | yes 'Staging, committing, branching, diffing never require a network round trip'. | source 2026-10-25 |
| Is it designed with AI coding agents in mind? | no | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | the version control system itself | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | snapshots (commits) with no identity that survives a rewrite | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | Not documented | source 2026-10-25 |
| How are merge conflicts mainly handled? | must be resolved before the merge or commit completes Three-way merge for text; binary conflicts surfaced for a choice; advisory locks. | source 2026-10-25 |
| What size of project is it designed for? | stands apart very large monorepos or large binary assets | source 2026-10-25 |
| Is code review part of the product? | no review workflow No review feature documented. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/EpicGames/lore · read 2026-10-25
- Web page · epicgames.github.io/lore/ · read 2026-10-25
- Web page · epicgames.github.io/lore/faq/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.