Where we stand

Every tool on the table. Verified facts only.

Green leads the row, red loses it, gold is a caveat. Where we couldn't verify a competitor's number — like Unity Version Control's pricing — we say so instead of guessing. That goes for our own cells too.

Feature matrix

Feature	Branchive	loregui	GitHub + LFS	Perforce Helix Core	Diversion	Unity VC
Native large-binary handling	Yes — native QUIC lore://	Yes — binds Lore's native API	No — bolt-on Git LFS	Yes — native	Yes — native	Yes — native
File locking	Enforced at the push, review-friendly — a lock never freezes a teammate out; they keep working and land through review	Exclusive claim only — no server to block the write	LFS locking — best-effort	Exclusive hold — one held lock stalls everyone else	Exclusive — "Hard Locks"	Exclusive — "Smart Locks"
Pull requests / code review	Yes — native pull requests	No — local GUI, no server	Yes — native	Needs Helix Swarm add-on	Yes — Reviews	Yes — Code Reviews
Required review before merge	Yes — enforced	No — nothing to enforce it	Yes	Yes — Swarm enforce	Not enforced — on their roadmap	Yes
Protected branches (server-enforced)	Yes — level-enforced, admin-gated unprotect	No — no hosted server	Yes	Yes — protections table	Yes	Yes
Permission levels enforced (read/write/admin)	Yes — server-side	No — no access-control layer	Yes	Yes	Yes	Yes
Web UI (browse / diff / review)	Yes	No web UI — native desktop GUI instead	Yes	Needs Helix Swarm add-on	Yes	Yes
Self-host option	Core is self-hostable; the team layer is Branchive Cloud	Yes — 100% local, any backend	Yes — Enterprise Server	Yes	Enterprise tier only	Yes
Desktop platforms	Windows today — macOS/Linux in development	Windows, macOS, Linux	Windows, macOS (GitHub Desktop)	Windows, macOS, Linux	Windows, macOS (Linux via CLI)	Windows, macOS, Linux
CI / automation	Signed webhooks → your CI	No — local GUI only	Yes — Actions	Yes — via Jenkins	Yes — CI integrations	Unity DevOps
AI agent access (MCP)	Yes — hosted server, OAuth, per-repo scoped	Yes — local desktop only	Yes — official (remote in preview)	Community server — not officially supported	No — as of Jan 2026	No — VCS ops (Editor MCP only)
Pricing	$20/user/mo, 1 TB each, 2 free-forever collaborators per repo, bandwidth free — $0 in beta	Free — open source (MIT)	Free tier + $4/user; LFS metered ~$0.07/GB + ~$0.0875/GB egress	Free ≤5 users; Cloud $39/user/mo	Free ≤5 users; $25–35/user/mo	Not published — see Unity's site
Built for	Unreal Engine / game teams	Lore users wanting a free local GUI	General development	AAA game / VFX, enterprise	Game teams, cloud-native	Game dev, real-time 3D

The GitHub column reflects Git + Git LFS — the same metered-storage model applies to self-hosted Git + LFS on GitLab, Gitea, or Bitbucket. loregui is Biloxi Studios' free, open-source local GUI for Lore — a different lane: no hosted server, review pipeline, or access control, which is exactly what Branchive Cloud adds. On MCP: loregui's server is local-only, GitHub's remote server is in public preview, Perforce's is community-supported (not officially supported), and Unity's official MCP targets the Editor — not version control; Branchive's is a hosted, OAuth-secured server scoped to your repo permissions. Facts per each vendor's published documentation.

Deep dives: GitHub alternative · Perforce alternative · Helix Core alternative · Diversion alternative · Unity Version Control alternative · Git LFS alternative

Three ways to use Epic's Lore

Pick your lane.

Lore CLI — bare metal

Epic's native command line. Fast, free, no GUI, no team layer. You bring your own server and your own discipline.

loregui — free local GUI

Biloxi Studios' open-source desktop GUI. Great solo tool, cross-platform today. No server, no reviews, no access control.

Branchive — the team layer

Free desktop GUI plus a hosted fork of Lore with reviewed pull requests, enforced locks and grants, issues, wiki, and webhooks. The only lane built for teams.