Hi all,
I am trying to find out if there is interest in a hosted Forgejo service with a strong emphasis on EU sovereignty and independence from big tech. Forgejo is an open-source Git hosting platform that I think is great and deserves wider use. For that reason, we will donate 5% of our plan revenue to the Forgejo project.
The plan is to cover what developers and small teams need:
- Forgejo for Git hosting
- Servers at Scaleway (a European cloud provider)
- CI/CD runners
- Dependency vulnerability alerts on every plan
- Daily backups
- Other essentials, as listed on our features page
Vault42 (that’s us) has no US parent company and uses only EU-based subprocessors, so your code stays outside US jurisdiction. ISO 27001 certification is a goal for later on.
The focus will be on private repositories, since Codeberg already serves open-source projects very well. There will also be a free plan for open source with unlimited public repositories, not to compete with Codeberg but to give people another option.
If this interests you, you can join the waitlist at vault42.eu.
Questions and suggestions are welcome in the comments or by DM.
Cheers,
Marijn from Vault42
Disclosure: I am the founder of Vault42.
How is CI/CD going to look? I currently have many different Github workflows and they are the main thing keeping me from switching to a different platform; the issue is the ecosystem of third party workflows is gigantic, so a competitor ideally needs to be able to run them out of the box, or require only a minor refactor.
Hi! Thanks for your reply :)
This is exactly why I want to offer hosted CI/CD, so that EU GitHub users can actually make the switch. To be honest, I’m still working a lot of this out, and I can’t promise a seamless one-to-one transition from GitHub Actions to Forgejo Actions. They are very similar, but there are differences.
What I can say: Forgejo Actions uses nearly the same workflow syntax, and if a repository has no .forgejo/workflows folder, it reads your existing .github/workflows folder. Most third-party actions work too: common ones resolve by their usual name, and you can reference others by their full GitHub URL.
Hosted runners will offer a lean default image and a GitHub-compatible one, so most workflows should run unchanged or with a small change.
The biggest exception is actions that talk to GitHub itself, such as creating GitHub releases or commenting on pull requests. Those need a Forgejo alternative. There are a few smaller differences as well, such as artifact uploads using Forgejo’s own version of the upload-artifact action.
I want to make this transition as smooth as possible, and for complex setups like yours I’m happy to help directly.