Comparison
LoreOwl vs Perforce
File locking and large files, without running your own server.
- 5 users
- Free on Perforce P4
- $39
- Per user a month on P4 Cloud
- $20
- Per seat a month on LoreOwl Studio
And fewer than 20 workspaces. Larger teams buy licences.
Hosted by Perforce, up to 100 users, 64 GiB of storage included.
Hosted, with 500 GB of history and the rest of the app included.
| Aspect | Perforce P4 | LoreOwl |
|---|---|---|
| Server | Run your own, or P4 Cloud | Hosted by us |
| File locking | Exclusive checkout | Locks shown in the file tree |
| Large binary files | Yes | Yes |
| Which files are binary | A typemap, set by an admin | Nothing to configure |
| Partial checkout | Workspace views and streams | A view file when you clone |
| Permissions | Down to a path | Owner or member, per organization |
| Audit trail | Yes | No |
| Game builds and store uploads | Separate tools | Built in |
| Asset vault with versions | No | Yes |
| Issue tracking | Separate tools | Board and timeline |
Moving a depot across
- Sync a workspace with P4V or p4, then import that folder
- Your current files arrive as one commit, with recent changelist descriptions saved on it
- Changelist history does not come across
Where Perforce is the better fit
- Very large depots and teams in the hundreds
- Permissions down to a path, and a full audit trail
- Streams, and studio tools already built on P4
- Exclusive checkout that the server enforces
What LoreOwl does not do
- Locks are advisory. They show who holds a file and do not block a push.
- No per-path permissions. Access is per organization.
- No audit log.
- No proxy or edge servers.
- The desktop app is Windows only.
Perforce facts on this page come from its own site, checked in October 2026: P4 cloud options, deployment guide. They change, so check them before you decide.
The other comparisons
Replace GitHubLarge binary files versioned without Git LFS, with builds, a vault and issues in the same app.Replace AnchorpointHosted Lore with storage included, plus builds, a vault and issues, instead of a client for a host you run.Replace JenkinsGame builds, checks and store uploads built in, with no server or Jenkinsfile to maintain.Replace TrelloA board and a timeline on the same tickets, next to the commits and builds they belong to.