Comparison
Branchive as a Perforce alternative
If you're looking for a Perforce alternative that adds pull requests, required review, and a modern collaboration layer — while keeping the binary-asset file locking that game teams depend on — Branchive is built for that intersection.
Windows only today — macOS and Linux are in development.
Back to BranchiveReviewed PRs vs. none
Perforce has no native review step. We built one in.
Pull requests with required review aren't a native Perforce concept. Branchive Cloud brings the full PR workflow to Lore — propose changes, require review before merge, discuss inline — enforced server-side before a merge lands.
QUIC-native big binaries, still
Binary-first, without the admin overhead.
The lore:// protocol is QUIC-based and built for large files — a real 6.05 GiB Unreal project, 3,637 files, cloned in 78 seconds from Branchive Cloud (measured, one command, not a benchmark rig). No server administration required to get started.
Transparent, free right now
No per-seat licensing to negotiate.
Perforce requires commercial per-seat licensing and server administration. Branchive Desktop is free, full stop, and Branchive Cloud collaboration features are free during early access.
Enforced permissions vs. a locking-only VCS
Protected branches, enforced by Branchive Cloud.
Core Lore already blocks a direct push to a protected branch, even the owner's. Branchive Cloud forks the server to enforce role by level and gate unprotect to admins only, so protection actually holds — the same seriousness as Perforce's protections table, with a pull-request workflow layered on top.
Honesty
When Perforce is still the better choice.
If you need locks that go read-only on your local disk
Branchive Cloud's file locking is enforced server-side: locking a file stops anyone else from locking the same file, and the server rejects anyone else's direct commit, push, force-push, or rename over the locked file. Perforce's write-blocking locks go one step further and make the file read-only on your local disk the moment someone else locks it — Branchive doesn't do that yet. If your workflow depends on that client-side guarantee, Perforce does that and Branchive does not.
Deep existing P4 pipeline integrations
If your studio has years of investment in Perforce-triggered CI pipelines, custom P4 triggers, Swarm-based review workflows, or build tools that integrate directly with the Perforce client API, switching version control systems carries real migration cost. Branchive does not offer a drop-in P4 API compatibility layer.
Large studios with dedicated Perforce administration
Perforce is the long-standing standard at large game studios for a reason: it handles enormous binary depots, has decades of production hardening, and its administration model is well understood by veteran game-infrastructure teams. If your studio already has dedicated P4 administration and the licensing cost is acceptable, Perforce remains a proven choice.
Full feature comparison
Full feature comparison.
Competitor wins are shown honestly — green leads the row, red loses it, gold marks a caveat in between. Where we couldn't verify a competitor's number, like Unity Version Control's pricing, we say so instead of guessing.
| Feature | Branchive | loregui | GitHub | Perforce Helix Core | Diversion | Unity Version Control |
|---|---|---|---|---|---|---|
| Native large-binary handling | Yes — native QUIC lore:// | Yes — binds Lore's native API in-process | No — bolt-on Git LFS | Yes — native | Yes — native | Yes — native |
| File locking | Yes — enforced on Branchive Cloud; self-hosted Lore doesn't block the write | Exclusive claim only — no server, so it can't block the write | Git LFS locking — best-effort, not hard-enforced | Exclusive, write-blocking | Exclusive — "Hard Locks" | Exclusive — "Smart Locks" |
| Code review / merge-request workflow | Yes — native pull requests | No — local GUI, no server | Yes — native pull requests | Yes — needs the Helix Swarm add-on | Yes — Reviews | Yes — Code Reviews |
| Required review enforced before merge | Yes | No — nothing to enforce it | Yes | Yes — Swarm enforce | ⚠️ Not enforced — on Diversion's roadmap, per their docs | Yes |
| Protected branches (server-enforced) | Yes — core Lore blocks natively; our fork adds level-enforcement and admin-gated unprotect | No — no hosted server | Yes | Yes — protections table | Yes | Yes |
| Permission levels (read/write/admin) enforced | Yes | No — no access-control layer | Yes | Yes | Yes | Yes |
| Web UI (browse / diff / review) | Yes | No web UI — full native desktop GUI instead | Yes | Needs the Helix Swarm add-on | Yes | Yes |
| Self-host option | Core is self-hostable; the enforcement layer is Branchive Cloud-only | Yes — 100% local, any backend (local/S3/MinIO/Garage) | Yes — Enterprise Server | Yes | Enterprise tier only | Yes |
| Desktop platforms | Windows only today — macOS/Linux in development | Windows, macOS (Apple Silicon), Linux | Windows, macOS (GitHub Desktop) | Windows, macOS, Linux | Windows, macOS (Linux via CLI) | Windows, macOS, Linux |
| CI / automation | Via webhooks → your CI | No — local GUI only | Yes — Actions | Yes — via Jenkins | Yes — CI integrations | Unity DevOps |
| Pricing / free tier | Free during early access | Free — open source (MIT) | Free tier + paid; Git LFS metered ~$0.07/GB storage + ~$0.0875/GB egress | Free ≤5 users; Cloud $39/user/mo | Free ≤5 users (Indie); Pro $25/user/mo, Studio $35/user/mo | — see Unity's site |
| Target audience | Unreal Engine / game teams, Windows-first | Lore users who want a free local GUI, any platform | General development | AAA game / VFX, enterprise | Unreal Engine / game teams, cloud-native | Game development, real-time 3D |
The GitHub column reflects Git + Git LFS — the same metered-storage and best-effort-locking model applies to self-hosted Git + LFS on GitLab, Gitea, or Bitbucket. The loregui column is Biloxi Studios' free, open-source local GUI for Lore — genuinely free and cross-platform today, with no hosted server, review pipeline, or access-control layer. Unity Version Control's pricing isn't published anywhere we could verify, so we don't quote a number here — check Unity's site directly.
Questions
Frequently asked questions.
Are file locks enforced in Branchive?
Yes, on Branchive Cloud. File locking stops a second lock on the same file, and now also stops anyone else's direct commit, push, force-push, or rename over the locked file — the server rejects it. Perforce's write-blocking locks go one step further and make the file read-only on your local disk, which Branchive doesn't do. Approved PR merges aren't lock-gated, and repo owners/admins can force-release a lock.
Can Branchive handle large binary files like Perforce?
Yes. The lore:// protocol is QUIC-based
and built for large files. A real 6.05 GiB Unreal project with
3,637 files was fully cloned in 78 seconds from Branchive Cloud
(measured, not a benchmark). Like Perforce, binary files are a
first-class concern — not handled through a separate storage layer.
Does Branchive require running my own server?
No — Branchive Cloud is a managed service. Core VCS operations
(clone/commit/push/branch/lock) also work against any
loreserver, self-hosted included.
Branchive Cloud adds collaboration features: pull requests with
required review, invite-only team sharing, and per-repo
read/write/admin roles (collaborators land changes via reviewed
pull requests; only the owner pushes directly today).
Does Branchive enforce branch protection and permissions the way Perforce does?
Yes, but precisely: core Lore already blocks a direct push to a protected branch, even the owner's — that's native. What stock Lore lacks is protection that holds — anyone with a grant can unprotect, push, and reprotect — and level-based roles, so read-only can still push to an unprotected branch. Branchive Cloud forks the server to close both gaps: role enforced by level, and unprotect admin-gated, matching the seriousness of Perforce's protections table with a pull-request workflow layered on top. A self-hosted, stock loreserver gives you the Lore core, not this enforcement layer.
Try it
See if Branchive fits your team's workflow.
Windows only today — macOS and Linux are in development.
Branchive home · Why Branchive · Branchive as a GitHub alternative