USourceControl vs Lore (Unreal Version Control)
Epic open-sourced Lore, also known as Unreal Version Control or URC, as a free alternative to Perforce for Unreal Engine teams. It is a genuinely significant release and it is free, which makes the honest comparison a question about who runs it rather than what it costs. Here is where each one fits, from $25/user/mo.
At a glance
When a managed service is the better call
Nobody on your team wants to be an admin
Free software running on a server you maintain is not free. It costs whoever is answering pager duty instead of building your game. If that person is your only backend engineer, or worse, your technical director, the arithmetic changes.
Restores you don't have to rehearse
Every studio believes it has backups. Far fewer have restored from one. Here, restore is not a recovery procedure — it is a button in the app, used daily, on a version history that keeps every commit and verifies every byte with SHA-256 on the way in and out.
A distributed team from day one
Self-hosting is straightforward when everyone shares an office and a LAN. It becomes a networking project the moment your artists are in three countries on home connections.
You want to start today
Sign up, link your project folder, commit. Five minutes, no server to provision, no storage to size, no firewall rules to argue about.
Predictable cost, unlimited scale
One flat per-seat price with unlimited storage and bandwidth. No storage sizing exercise as your Nanite meshes grow, and no surprise bill when the team pulls a nightly build.
Someone to call
When source control breaks mid-milestone, community support is the wrong dependency. Support is included on every plan, with priority and dedicated support on Studio.
When Lore is the right choice
We would rather you pick the right tool than pick ours. Lore is a serious release from the people who make the engine, and for a lot of teams it is the correct answer:
- You have infrastructure people and want full control of your stack. Lore gives you that in a way no service can.
- Your studio has a hard requirement that project data never leaves hardware you own, whether from a publisher agreement or internal policy.
- You are already running your own infrastructure competently, so the marginal cost of one more service is genuinely low.
- Budget is the binding constraint and engineering time is not. Free plus your own server beats any subscription when you have the people to spare.
- You want to read, modify, or extend the source of your version control system. It is open source, and that is a real advantage.
If any of those describe you, Lore is likely the better fit, and it is worth taking seriously. The comparison is not really free versus paid. It is whether the hours your team spends running it are worth less than a subscription.
Coming from a self-hosted setup?
Migration is the same shape from any system: point the desktop app at your current working copy and commit. No history rewriting, no export format to wrangle, no downtime for the team beyond one sync.
Common questions
What is Lore?
Lore, also referred to as Unreal Version Control or URC, is a version control system Epic Games open-sourced as a free alternative to Perforce for game development. It is designed around the same problems: very large binary assets, file locking, and the workflows Unreal teams actually use.
Is Lore really free?
The software is free and open source, yes. Running it is not: you need a server, storage that grows with your project, backups you have tested, monitoring, upgrades, and someone whose job it is to care when it stops. For a studio with infrastructure staff that cost is marginal. For a five-person team where the technical director would be the admin, it is the whole cost.
Should I use Lore instead of Perforce?
If you were going to self-host anyway, Lore deserves serious evaluation. It targets the same problems as Perforce without per-seat licensing, and it comes from the people who build the engine. The honest caveat is that Perforce has decades of production hardening at enormous scale behind it, and Lore is new. Weigh how much that maturity is worth on your project.
How does USourceControl compare to Lore on features?
The feature sets overlap substantially, because both target the same problems: large binaries, per-file locking, and Unreal-shaped workflows. The real difference is operational. Lore is software you run; USourceControl is a service we run. Choose based on whether you want to own that responsibility, not on a feature matrix.
Can I migrate from Lore to USourceControl later?
Yes. Migration works from any system: sync your current working copy as the initial commit, and your team carries on from there. History stays in your old system for reference if you want to keep it. The same applies in reverse, since you can export your files from us at any time.
Does Lore work with Unreal Engine 5 World Partition and OFPA?
It is built by Epic for Unreal, so UE5 workflows including World Partition and One File Per Actor are squarely its target. The many-small-files pattern OFPA produces is exactly the case a purpose-built game version control system should handle, which is true of Lore and of us, and notably less true of Git LFS.
Skip the server
Cloud source control for Unreal Engine 5 teams, from $25/user/mo. Unlimited storage and bandwidth, free for solo devs, first commit in five minutes.
Create your first project