Comparison
Branchive as a GitHub alternative
If you're looking for a GitHub alternative for large-repo, binary-heavy, or game-development workflows, Branchive is built on a different VCS foundation — one that treats large files as a first-class concern, not an add-on.
Windows only today — macOS and Linux are in development.
Back to BranchiveNative big binaries vs. an LFS bolt-on
Large files, built in — no LFS layer to run.
Git was built for text. Git LFS bolts on a separate storage layer and metered bandwidth. The lore:// protocol is QUIC-native and treats large files as first-class data — a real 6.05 GiB Unreal project, 3,637 files, cloned in 78 seconds from Branchive Cloud (measured, not a benchmark).
Locking exists here — GitHub has none built in
Enforcement GitHub doesn't give you at all.
GitHub has no native file-locking mechanism — Git LFS's lock command is the closest bolt-on, and it's best-effort, not hard-enforced. Branchive Cloud's locking is enforced: it 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. Approved PR merges aren't lock-gated, and repo owners/admins can force-release a lock.
Transparent, free right now
No LFS metering to track.
Branchive Desktop is free, full stop. Branchive Cloud collaboration features — pull requests with required review, protected branches enforced by Branchive Cloud — are free during early access, with no per-GB LFS storage or egress charges.
Honesty
When GitHub is still the better choice.
Code-only projects with small repos
If your repository is a few hundred megabytes of source code with no large binary assets, Git is purpose-built for that workflow. GitHub's PR/review flow is the industry standard, and you won't feel the pain points that LFS and large-repo clone times create for binary-heavy teams.
Open-source community, ecosystem, and integrations
GitHub's open-source community is unmatched. The ecosystem of integrations, the CI marketplace (GitHub Actions), and the network effects of millions of developers collaborating in public are things Branchive does not replicate. If your project lives or dies by its open-source community, GitHub is the right home.
CI marketplace and Actions
GitHub Actions provides a vast marketplace of pre-built CI workflows. Branchive Cloud does not offer a comparable CI marketplace today. If your team relies on deep CI integration with third-party services, GitHub's ecosystem is more mature.
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 Branchive work with Git?
No. Branchive is built on Lore, Epic's version control system — not
Git. Lore uses its own QUIC-based protocol
(lore://) and a different data model.
Branchive does not interoperate with Git repositories or the Git
CLI.
Can I import my existing GitHub repositories?
There is no automated import from Git to Lore. Branchive works with
Lore repositories — you can create new repos on Branchive Cloud and
push to them from a Lore workspace. The core operations
(clone/commit/push/branch/lock) work against any
loreserver, self-hosted included.
Is Branchive free?
Branchive Desktop is a free Windows client. Branchive Cloud 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) — are available when you sign in with Google.
Does Branchive enforce protected branches and roles, or is that just a UI setting?
Core Lore already blocks a direct push to a protected branch, even the owner's — that's native. What stock Lore lacks: protection isn't gated (anyone holding a grant can unprotect, push, and reprotect) and roles are checked by presence, not level, so a read-only grant can still push to an unprotected branch. Branchive Cloud forks the server to close both gaps — role enforced by level, and unprotect admin-gated — so protection actually holds, on the lore CLI and Branchive Desktop too, not just the web UI. A self-hosted, stock loreserver gives you the Lore core, not this enforcement layer.
Try it
See if Branchive fits your workflow.
Windows only today — macOS and Linux are in development.
Branchive home · Why Branchive · Branchive as a Perforce alternative