Compare
USourceControl vs Anchorpoint
Anchorpoint puts a friendlier face on Git + Git LFS. USourceControl skips Git entirely — you get a storage and versioning system designed for game projects, not a polished client over legacy plumbing.
At a glance
Why teams switch
Why teams pick USourceControl over Anchorpoint
One product, one bill
Anchorpoint requires you to pair it with a Git provider's LFS service, manage two tools, and reconcile two billing surfaces. USourceControl is one product with one plan — the client, the server, the storage, and the bandwidth.
No Git LFS at the bottom
Anchorpoint is a UI over Git LFS, so it inherits LFS's quirks — pointer files, hook requirements, hosting-specific quotas. USourceControl's storage is native; there's no Git layer to leak through.
Reliable locking without host gymnastics
Locking on Git LFS varies by host and requires every client to be LFS-aware. USourceControl's lock state is authoritative on the server and enforced for everyone, so two artists can't silently diverge.
Global delivery included
USourceControl ships assets over a global CDN without per-region server setup. On Anchorpoint, throughput depends on your Git host's infrastructure.
When Anchorpoint might fit you better
Anchorpoint is a thoughtful product and a genuinely fine choice when:
- You're already committed to a GitHub / Azure DevOps workflow and want to keep it.
- You want a client-only tool that leaves your storage fully self-managed.
- Your team is small and comfortable living inside the Git LFS model.
FAQ
Common questions
What's the core difference between USourceControl and Anchorpoint?
Anchorpoint is a desktop client over Git LFS. USourceControl is an end-to-end source control service — client, server, storage, and delivery — built from scratch for game projects, without Git underneath.
Does USourceControl work with my existing GitHub repo?
USourceControl isn't a Git frontend, so it doesn't sync with GitHub repos. Many teams keep code in GitHub and use USourceControl only for content — .uasset, textures, audio, builds.
Can I still code-review in GitHub while using USourceControl?
Yes. Keep your engine code (C++, C#, GDScript) in GitHub with PRs, and use USourceControl for content that Git handles poorly.
Is USourceControl more expensive than Anchorpoint + GitHub?
It depends on asset volume. At indie scale with low bandwidth, GitHub + LFS packs can be cheaper. As soon as your team regularly pulls builds or trades multi-gigabyte assets, bundled USourceControl pricing usually comes out ahead.
Do you support engine-native source control plugins?
Not today. The workflow is through the desktop app, which most teams find preferable because non-engineers don't need to use in-editor source control UIs.
See how it feels without Git underneath
Free for solo developers. Try it alongside your existing setup.
Start for free