Shopping for a Perforce alternative
Perforce Helix Core has run large game projects since the 1990s. Studios with a thousand people on one depot still rely on it, and that track record is earned. The design behind it is also about thirty years old, and a few of those old decisions show up in daily work and in what the licence costs once a team grows past the free tier.
Every operation goes through the server
p4 edit, p4 add, p4 sync and
p4 submit all need a live connection. Making a file writable is a
request the server has to grant before you can start typing. On a train or a
conference network, that round-trip is now part of your edit-save loop. If a file
changes without p4 edit being run first, say from a build script or an
editor that does not shell out to p4, the server stays unaware of it
until p4 reconcile scans the workspace and compares it against the
depot.
Licensing scales with headcount
Above a small free tier, Helix Core is licensed per seat. Four extra artists for a two-month milestone means four more seats, whether they commit every hour or once a week. The bill follows headcount. A mostly-idle contractor costs the same seat as a lead who lives in the depot all day.
The format is closed
The server is closed source, the protocol is proprietary, and the depot format has no public spec or independent implementation. File integrity still runs on MD5, which has had practical collision attacks since 2004. None of that blocks a shipping team, but it does mean your project history is only readable through one vendor's binary, and you have to take that binary's word for what it wrote.
The open-source alternative
lore is Epic's open-source version control for games. Like Perforce, it keeps source code and large binary assets in one repository. The differences are underneath, and most of them remove the need to talk to the server for routine work:
- lore reads the working tree directly, so there is no server-side "opened for edit" state and nothing to reconcile
- staging, committing and branching happen locally; the network only matters on sync or push
- every file fragment is keyed by a BLAKE3 hash, and identical content is stored once per repository instead of re-copied each revision
- the client, server and storage backends are MIT-licensed, and the wire protocol and on-disk format are documented and versioned
folkorama runs the lore server for you. A workspace is a private lore server
on its own subdomain: TLS, backups and version upgrades are handled, and the disk
cap is enforced by the filesystem itself. The client is the stock lore
CLI, with nothing to fork or patch. The entry plan is free, and pricing follows disk
use.
Enforced file locks are still Perforce's edge
Perforce has real exclusive checkout. Once an admin marks a path, a conflicting
p4 submit fails, and the server enforces that. lore's file locking is
advisory for now: it records who intends to edit a file, but nothing in the push
path stops another writer. For a team that depends on a hard lock over unmergeable
art, that is a real gap, and switching means going without it until upstream lore
adds enforcement. The
capabilities page keeps track of
what is and is not enforced today.
A move fixes everything else on that list. The full technical comparison, plus a step-by-step migration that covers mapping a Perforce protections table onto lore repositories, is in Migrating from Perforce.