Marijn - Vault42 EU

Hi, I’m Marijn from Vault42. A Dutch software engineer living in the Czech Republic, and a firm believer in European tech independence and digital sovereignty. Vault42.eu is my product: Git hosting in the EU, on European infrastructure, outside the reach of foreign jurisdictions.

  • 1 Post
  • 3 Comments
Joined 2 months ago
cake
Cake day: September 24th, 2026

help-circle

  • 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.


  • Woa, thanks for the detailed response, really appreciate it :)

    Interesting to hear about Perforce, I never even heard of that before. I wonder what makes it so suitable for AAA. Wondering also what an equivalent for indie devs could be, because Perforce sounds expensive and maybe overkill for smaller studios and solo devs?

    As to your points:

    Templates for setting up new repos: I think it would be doable to set up Cookiecutter + Cruft in CI, either on hosted runners or your own. For a dedicated instance it could be part of the infra package.

    Renovate I will also offer on the paid plans.

    For storing Terraform/OpenTofu state, Forgejo hasn’t implemented this on purpose; from what I can gather, the maintainers felt it doesn’t fit a code collaboration tool. The solution here would be to bring your own S3 bucket as the state backend, and run plan and apply from CI. For dedicated instances that could be part of the setup as well.

    On the nested org/group structure: Forgejo has a flatter structure than GitLab. Organisations own the repositories, and teams decide who can access which ones.

    As for your other ideas and suggestions, I have noted them down. This has been super valuable insight for me, thanks for letting me take a look under the hood!