Branchive: Helix Core Alternative with Built-In Pull Requests

Reviewed PRs, built in — no Swarm required

One system, not two.

Helix Core itself has no native review workflow — Helix Swarm is a separate component you install and administer. Branchive Cloud's pull-request review is built in from the start, with no add-on to install.

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).

Transparent, free right now

No per-seat licensing to negotiate.

Helix Core requires server administration and commercial per-seat licensing — free for up to 5 users, then Perforce's Cloud tier runs $39/user/month. Branchive Desktop is free, full stop, and Branchive Cloud is free during early access.

Enforced permissions, layered on top

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 — the same seriousness as Helix Core's protections table, with a pull-request workflow layered on top.

Honesty

When Helix Core is still the better choice.

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. Helix Core'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, Helix Core does that and Branchive does not.

Deep existing Helix/P4 pipeline integrations

If your studio has years of investment in Perforce-triggered CI pipelines via Jenkins, custom P4 triggers, or Swarm-based review workflows, switching version control systems carries real migration cost. Branchive does not offer a drop-in Helix Core API compatibility layer.

Large studios with dedicated Helix Core administration

Helix Core is the long-standing standard at large game and VFX 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 Helix Core administration and the licensing cost is acceptable, it 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.

Does Helix Core include code review out of the box?

No — that's Helix Swarm, a separate component you install and administer alongside Helix Core. Branchive Cloud's pull-request review is built in from the start, with no add-on to install.

Are file locks enforced in Branchive the way Helix Core enforces them?

Mostly. Branchive Cloud's forked server now enforces the same write-blocking Helix Core does: it stops anyone else from locking the same file, and it rejects a direct commit, push, force-push, or rename from someone else over the locked file. Helix Core goes one step further and makes 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.

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 Helix Core 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 Helix Core'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.

Sign in with Google Download Branchive Desktop 0.1.11

Windows only today — macOS and Linux are in development.

Branchive home · Why Branchive · Branchive as a Perforce alternative · Version control for game development

Branchive as a Helix Core alternative