“"Wow, someone finally got sick enough of Perforce's multi-decade monopoly to do something about it." — icefox (31 upvotes), Lobsters (https://lobste.rs/s/r9fmgk/epic_games_announces_lore_version)”
You know that feeling when your game studio's Perforce bill arrives and you are paying hundreds of dollars per seat per year for artists and programmers who just need to check in textures? Or when a senior tools engineer spends an afternoon reconciling Perforce's file metadata because the server state drifted out of sync after a crash? Git does not solve this either — it stores every version of every 2 GB texture file permanently with no delete path, and it has no real file locking, so artists regularly overwrite each other's binary assets with no merge path. Every existing open-source VCS treats binary files as an afterthought; Lore is the first open-source centralized VCS built with binaries as the primary case.
Think of Lore's storage layer like a fingerprint-based filing system that never duplicates pages. Every file gets broken into chunks, and each chunk gets a BLAKE3 cryptographic fingerprint — if two texture versions share 80% of the same pixels, those shared chunks are stored once and referenced from both. On top of this sits a tiny mutable index of branch names and latest revision pointers, which you keep locally and sync conditionally. You run stage, commit, branch, and diff entirely against your local store — no server round trip required for everyday work. Access control works per partition: each linked sub-repository is an isolated partition with its own JWT auth scope, so your art team's 50 GB asset partition can carry different permissions than your code partition without splitting into separate repos.
You are a tools engineer, pipeline TD, or technical director at a game studio paying Perforce per-seat licensing for a mixed team of artists and programmers managing terabyte-scale repos. You are also relevant if you work in VFX pipelines, simulation infrastructure, or any system that versions multi-gigabyte binary artifacts alongside code. This is not the right tool today for general software teams versioning only text — Git handles that well, and Lore's file locking enforcement is still incomplete, making a live production migration risky.
Worth evaluating on a new or side project now — the MIT license, Epic's proven internal usage at Fortnite scale, and the BLAKE3 deduplication design give it more credibility than a typical day-one open-source launch. Do not migrate a live production to it yet: the FAQ explicitly warns APIs and on-disk formats may change before v1.0, and file locking enforcement — the make-or-break feature for artist workflows — is still being redesigned for scale. Watch for v1.0 as the signal to run a serious production trial.
Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.