Hey all, I’m Marijn, and I’m building Vault42, an EU-hosted Git service.

I would like to cater to the needs of game developers, and offer them an alternative to GitHub.

Git LFS add-ons are available on the paid plans, but I would like to hear from people who work with large binary assets every day, like textures, audio, models, builds, etc.

A few things I’m trying to understand:

  • How large is your LFS store, and how quickly does it grow?
  • Is storage the problem, or transfer (teammates cloning, CI pulling assets)?
  • Do you rely on file locking for binary files?
  • If you have thought about leaving GitHub, what stopped you?
  • Do you have any specific CI/CD needs I should be aware of?

What would it take for you to move your game projects to another Git host? Replies here or DMs are both welcome.

About 50 people are on the waitlist so far, and I’d like a few game developers on board to help me get LFS right.

Thanks!

(Waitlist, if you want to follow along: vault42.eu)

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 1 day ago

Simply put, I plan on using Scaleway buckets for LFS. Forgejo has no metering for this kind of thing, and I'm not planning to build it, so transfer would mostly be on a fair-use basis, with the tiers priced at what I think are sensible defaults.

I would of course review this after a while, to see how much transfer is actually used, taking into account storage sizes, team sizes and so on.

Current tiers:

Add-on Price Extra LFS storage Fair-use transfer per month
LFS 50 GB €5/month 50 GB 150 GB
LFS 200 GB €15/month (€180/year) 200 GB 500 GB
LFS 1 TB €60/month (€720/year) 1 TB 1 TB

Does this seem right to you?

As for the locks: Forgejo lists active locks and who holds them in the repository’s LFS settings, but not yet while browsing files, and I still need to check how visible that page is for non-admin team members.

  • source
  • parent