Compare

USourceControl vs Anchorpoint

USourceControl is cloud version control for game teams. It saves every change to your game, keeps the whole team in sync, and never loses a file. Anchorpoint is an artist-friendly client, but it runs on Git and Git LFS, and you bring and secure your own storage. USourceControl includes private storage and skips Git entirely. Nothing to assemble.

At a glance

Underlying tech
USourceControlPurpose-built versioning protocol
AnchorpointGit + Git LFS under the hood
Hosting
USourceControlCloud, we run it for you
AnchorpointBring your own Git host (GitHub, Azure DevOps, self-hosted)
Large-file quotas
USourceControlPer-plan storage, no LFS bandwidth caps
AnchorpointInherits your Git host's LFS quotas and bandwidth packs
Locking reliability
USourceControlServer-enforced, first-class in desktop app
AnchorpointGit LFS locking, depends on host and client support
History model
USourceControlPer-file version timelines
AnchorpointGit commit graph
Pricing includes storage
USourceControlYes, storage and bandwidth bundled
AnchorpointNo, host LFS costs are separate
Source-available client
USourceControlYes (Enterprise)
AnchorpointClosed source

Why teams switch

Why teams pick USourceControl over Anchorpoint

Storage included, nothing to assemble

Anchorpoint is a client. You still bring your own storage (a Git host, NAS, Dropbox, or AWS), wire it up, and secure it yourself. USourceControl is one product with one plan: the client, the server, the storage, and the bandwidth, all included. Once you're set up, your team starts committing.

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 and Git LFS, and you supply and secure your own storage. USourceControl is an end-to-end cloud source control service: client, server, private storage, and delivery, all included and 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

From $12/mo for solo developers. Try it alongside your existing setup.

Book a call