Technical Deep Dive
Lore's technical architecture is a radical departure from Git's content-addressable filesystem. At its core, Lore implements a custom storage engine that separates the storage of binary blobs from the metadata and history graph. This is achieved through a layered design:
1. Object Store Layer: Handles the physical storage of file content. Unlike Git's packfiles, Lore uses a chunked, deduplicated storage format optimized for large binary files. Files are split into variable-size chunks (typically 64KB to 4MB) based on content-defined boundaries using a rolling hash algorithm (similar to Borg backup or restic). This allows efficient delta compression even for binary files where small changes (e.g., a texture edit) only affect a few chunks.
2. Reference Layer: Manages the directed acyclic graph (DAG) of commits, branches, and tags. This layer is lightweight and can be stored separately from the object store, enabling partial clones where a developer only fetches the metadata and the specific chunks they need.
3. Protocol Layer: Lore uses a custom TCP-based protocol (not HTTP or SSH like Git) designed for low-latency, high-throughput transfers. The protocol supports multiplexing, allowing multiple file transfers over a single connection, and includes built-in compression and encryption. It also supports delta-of-delta compression for metadata, significantly reducing the size of history for repositories with millions of commits.
A key innovation is Lore's workspace model. Unlike Git's checkout-based workflow, Lore uses a virtual filesystem (FUSE-based on Linux/macOS, Dokany on Windows) that presents a working directory without actually downloading all files. Developers see the full directory tree, but files are fetched on-demand when accessed. This is similar to Git LFS's smudge/clean filters but is integrated at the VCS level, not as an add-on.
Performance Benchmarks (from Epic's internal testing and early community reports):
| Operation | Git (with LFS) | Git (without LFS) | Lore |
|---|---|---|---|
| Clone a 50GB repo (1000 files, avg 50MB) | 12-15 min | Fails (OOM) | 45 sec |
| Commit a 2GB binary file | 30 sec (LFS upload) | N/A | 2.3 sec |
| Checkout a 10GB subset of files | 4 min | 8 min | 12 sec |
| History log for 100k commits | 8 sec | 8 sec | 0.4 sec |
| Disk usage for 50GB repo (working copy) | 55 GB | 52 GB | 3.2 GB (virtual) |
Data Takeaway: Lore achieves a 10-100x improvement in clone and checkout times for large binary-heavy repositories, with a 15x reduction in disk usage for working copies. This is not incremental—it's a paradigm shift for teams that regularly work with multi-gigabyte assets.
Lore is written in Rust, a choice that provides memory safety without garbage collection overhead, critical for performance-sensitive VCS operations. The project is available on GitHub at `epicgames/lore` and has already attracted contributions from the game development community, though the codebase is still evolving rapidly.
Key Players & Case Studies
Epic Games is the primary developer and sponsor. The team behind Lore includes veterans from the Perforce and Git LFS ecosystems, as well as engineers from Epic's Unreal Engine infrastructure team. Tim Sweeney, Epic's CEO, has publicly stated that "Git was never designed for the scale of modern game development," positioning Lore as a strategic investment in Epic's toolchain.
Competing Solutions:
| Product | Type | Strengths | Weaknesses |
|---|---|---|---|
| Git + Git LFS | Open source | Massive ecosystem, CI/CD integration, GitHub/GitLab support | Binary file handling is bolted on, performance degrades with scale, LFS server required |
| Perforce Helix Core | Proprietary | Industry standard for game dev, excellent binary handling, atomic commits | Expensive licensing, complex administration, closed source |
| Plastic SCM (Unity) | Proprietary | Good Unity integration, branch-per-task workflow, graphical UI | Acquired by Unity, uncertain future, limited outside Unity ecosystem |
| Mercurial + Largefiles | Open source | Similar to Git but better binary support | Declining community, fewer hosting options |
| Fossil | Open source | Built-in bug tracker, wiki, single-file database | Limited adoption, not designed for large binaries |
Case Study: Epic's Internal Use
Epic has been using Lore internally for over two years to manage the Unreal Engine repository, which contains over 300GB of source code, assets, and documentation. Before Lore, the team used Perforce, which required a dedicated team of administrators and cost over $500,000 annually in licensing. With Lore, Epic reports a 40% reduction in CI/CD pipeline times and a 60% reduction in storage costs due to deduplication.
Case Study: Early Adopter - Studio X (Anonymous)
A mid-sized game studio with 200 developers switched from Git LFS to Lore for their upcoming open-world title. They reported that the average time to set up a new developer workstation dropped from 4 hours to 15 minutes, and the number of merge conflicts decreased by 80% because Lore's chunk-level locking allowed multiple artists to work on different parts of the same file simultaneously.
Industry Impact & Market Dynamics
Lore enters a market dominated by Git (over 90% of software projects) and Perforce (estimated 70% of AAA game studios). The VCS market is valued at approximately $1.2 billion annually, with growth driven by the increasing size of digital assets in gaming, film, and engineering.
Adoption Curve Predictions:
| Phase | Timeline | Expected Adoption | Key Drivers |
|---|---|---|---|
| Early Adopters | 2026-2027 | 5-10% of game studios | Unreal Engine integration, Epic's marketing, performance benefits |
| Early Majority | 2028-2029 | 20-30% of game studios | Mature documentation, third-party hosting services, CI/CD plugins |
| Late Majority | 2030+ | 50%+ of game studios | Industry standard for game dev, possible Git replacement in other industries |
Market Disruption Potential:
Lore's open-source nature is a double-edged sword. On one hand, it lowers the barrier to entry and encourages community contributions. On the other hand, it faces the classic open-source challenge: building an ecosystem of tools, hosting services, and integrations that rival Git's. GitHub, GitLab, and Bitbucket have no incentive to support Lore unless it gains significant market share.
Epic's strategy appears to be:
1. Deep integration with Unreal Engine: Lore will be the default VCS in Unreal Editor, making it the path of least resistance for Unreal developers.
2. Open-source community building: By releasing Lore under a permissive license (MIT), Epic hopes to attract contributors from outside gaming.
3. Hosted service: Epic is rumored to be developing a cloud-hosted Lore service, similar to GitHub but optimized for game development, which could generate recurring revenue.
Funding and Investment:
Epic Games has raised over $9 billion in funding (including a $2 billion round from Sony and Kirkbi in 2022) and is valued at $31.5 billion. Lore is a strategic investment, not a revenue generator—it's designed to strengthen Epic's ecosystem and reduce dependency on third-party tools. If Lore becomes the standard VCS for game development, Epic could leverage it to drive adoption of Unreal Engine and the Epic Games Store.
Risks, Limitations & Open Questions
1. Ecosystem Immaturity: Lore has no CI/CD integration, no code review tools, no web-based UI, and no hosted service. Teams must build their own infrastructure or wait for third-party solutions. This is a significant barrier for all but the most technically sophisticated teams.
2. Protocol Lock-In: Lore's custom protocol means it cannot be used with existing Git-based tools (GitHub Actions, GitLab CI, etc.). This creates a vendor lock-in risk, even though the software is open source.
3. Learning Curve: Developers accustomed to Git's workflow will need to learn new commands and concepts. The virtual filesystem model, while powerful, can be confusing for users who expect files to be physically present on disk.
4. Security and Access Control: Lore's current implementation lacks fine-grained access control, audit logging, and encryption at rest. For studios with strict IP protection requirements, this is a deal-breaker.
5. Scalability Questions: While Lore handles 300GB repos well, can it scale to multi-terabyte repositories used by large film studios or game publishers? Early benchmarks are promising, but real-world stress testing is limited.
6. Community Governance: Epic Games controls the project's direction. Will they accept community contributions that conflict with their commercial interests? The open-source community is wary of "open core" projects where the company retains control.
AINews Verdict & Predictions
Lore is the most significant innovation in version control since Git itself. It solves a real, painful problem that has plagued game developers for decades. However, technology alone is not enough—the ecosystem matters more.
Our Predictions:
1. By 2028, Lore will be the default VCS for Unreal Engine projects, but Git will remain dominant for non-Unreal development. Epic will release a hosted Lore service with tight Unreal Editor integration, making it the obvious choice for new projects.
2. Perforce will lose 30-50% of its game development market share within five years. Lore offers comparable performance at zero licensing cost, and Perforce's high prices will become untenable.
3. A community fork will emerge if Epic tries to monetize Lore aggressively. The MIT license allows this, and the open-source community has a history of forking projects when corporate interests diverge.
4. Lore will expand beyond gaming into film VFX, architecture, engineering (CAD), and scientific computing—any field that deals with large binary files. The virtual filesystem model is particularly compelling for remote teams with limited bandwidth.
5. The biggest risk is not technical but social: Git's network effects are enormous. Developers know Git, tools support Git, and hiring pipelines expect Git. Lore must offer a 10x improvement to overcome this inertia—and based on our analysis, it does.
What to Watch:
- The release of Lore's REST API and web UI (expected Q4 2026)
- Integration with Unreal Engine 5.6 (expected 2027)
- The first third-party hosting service (likely from a cloud provider like AWS or Azure)
- Community adoption metrics: GitHub stars, contributors, and number of non-Epic repositories using Lore
Lore is not just a new tool—it's a bet that the future of software development involves larger, more complex assets, and that the tools we use must evolve accordingly. Epic Games is placing that bet with both its engineering resources and its open-source credibility. The next two years will determine whether Lore becomes the next Git or the next BitKeeper.