EU Git hosting
under European law.
Git hosting in Europe, for teams whose code must stay in Europe.
gitbuild.dev keeps your repositories, issues, and metadata on EU infrastructure under EU jurisdiction — with a DPA included, no US cloud in the chain, and no AI training on your code. Powered by Forgejo, the fully open-source Git platform governed by the non-profit Codeberg e.V.
Where your code lives
Data residency is an architecture decision, not a region picker in someone else's cloud.
EU infrastructure, end to end
Repositories, metadata, and backups all reside on infrastructure within the European Union. Nothing is replicated to, or routed through, US-based cloud providers.
EU law applies directly
Because the provider, the infrastructure, and the data are all European, GDPR and member-state law govern your data by default — no Data Privacy Framework, no standard contractual clauses to re-paper every few years.
No AI training
Your source code is never used for LLM training, model ingestion, or third-party analysis. The prohibition is contractual and technical — we have no data-sharing relationships with AI companies.
GDPR and the paperwork that proves it
Compliance teams need documents, not marketing. Both are public.
Data processing agreement
The DPA that governs how we process your data — subprocessors, retention, deletion, and breach notification. Included with the Business plan, public for everyone to read first.
Read the DPA →Infrastructure
Where the servers are, who operates them, and how backups work. The concrete answers your security review asks for, in writing.
See the infrastructure →The compliance checklist, answered
The questions a DPO or security reviewer asks before approving a Git host.
- Data residency: all data stored and processed within the European Union
- Legal basis: GDPR applies directly; no third-country transfers
- DPA: data processing agreement included on team plans, public before signup
- Subprocessors: EU-based, documented on the infrastructure page
- AI training: prohibited contractually and technically
- Exit: standard Git export at any time — no lock-in, no egress project
Frequently asked questions
Common questions about hosting Git in the EU on gitbuild.dev.
What does EU Git hosting actually mean?
Your repositories, issues, pull requests, and metadata are stored and processed on infrastructure inside the European Union, operated by a European company. EU data protection law applies directly — there is no transatlantic transfer to justify and no foreign cloud provider in the chain.
Is gitbuild.dev GDPR compliant?
Yes. GDPR applies natively, not through an add-on: data stays in the EU, a data processing agreement is included on team plans, and the infrastructure page documents exactly where and how your data is hosted.
Which providers do you rely on?
Hosting runs on EU-based infrastructure with EU-based backups. No US hyperscaler holds your repositories, and no third party processes your code for analytics or AI training. The full breakdown is on the infrastructure page.
Can we get a DPA for our compliance file?
Yes — a data processing agreement is included with the Business plan and is available for review before you sign up. Enterprise customers can additionally contract dedicated infrastructure.
Host your code where your legal team already is.
Create your account in seconds. A Forgejo workspace is provisioned automatically when you verify your email.
Start Building