Code on EU soil: why nine repositories moved to a Berlin non-profit

Code on EU soil - a luminous arch backlit by light rays deflecting a storm of cold streaks, crowned by twelve golden stars

Written by

in

Why nine repositories moved to a Berlin non-profit

We put the company’s nine repositories on Codeberg – a git forge run by a registered non-profit association in Berlin. Not as a statement about anyone else’s platform. As a decision about which jurisdiction our source history lives under, and why that belongs in the same compliance conversation as the inference stack.

What is on Codeberg now

Nine repositories at codeberg.org/PrivateLocalAI: our own tools – Strata, PolyStrata, Xolotl, Avalon, FreeToken, mcp-search-fetch – in C++, Python and Rust, plus maintained forks of the upstream projects we work against (vLLM, Pulsar, ds4). Same commits, same branches, open to any fork.

A repository is not only code

A repository carries contributor names and email addresses, commit history, issue discussions, access metadata. Under the GDPR, much of that is personal data, and the whole of it is company context – branches, internal notes, release timing. Where the forge sits decides which courts can reach it.

The mechanism, in three lines

GitHub is a US company: a subsidiary of Microsoft. The CLOUD Act (Clarifying Lawful Overseas Use of Data Act, 2018) obliges US providers to disclose data in their "possession, custody, or control" wherever it is stored – an EU data centre included. In their 2019 joint response to the law, the European Data Protection Board and the European Data Protection Supervisor warned that organisations complying with the GDPR can be caught in an unresolved conflict of laws by exactly that reach.

Enforcement is not theoretical

In May 2025 the Irish Data Protection Commission fined Meta Ireland 1.2 billion euros for transferring EU personal data to the US without an Article 46 safeguard strong enough – the largest GDPR fine to date, levied for the transfer itself, alongside an order to suspend it. Microsoft’s own transparency reports, published every six months, list thousands of law-enforcement requests per country per period – for EU citizens’ data, to US authorities, through US legal process. The mechanism is not hypothetical; it runs on a schedule.

The 2023 adequacy framework made transfers possible again. It did not repeal the CLOUD Act.

So we moved

Codeberg is operated by Codeberg e.V., a registered association (eingetragener Verein) headquartered in Berlin and funded by membership fees and donations – no shareholders, no US parent. It runs Forgejo on association-controlled bare-metal in German data centres, with German providers for backups and DDoS protection. What Codeberg offers is not a stronger privacy promise – it is the absence of exposure: a subject the CLOUD Act cannot reach because it has no US parent to compel.

The day-to-day is the same git. Codeberg runs Forgejo, a fork of Gitea: clones, pushes, pull requests, mirrors – the keyboard memory barely changes. We keep GitHub forks as mirrors for reach and stars; the authoritative branch sits under EU jurisdiction.

The same topology, one layer up

It is the same logic as running a model on your own GPU: compliance by architecture, not by paperwork. Inference inside your building means no Chapter V transfer to arrange; source history on EU-controlled hardware means no US subpoena to answer. Neither requires a legal team to interpret. Both are facts of the topology.

What we are not claiming: that GitHub combs through your repositories, or that a non-profit is immune to outages. The claim is narrower – the company holding the data cannot be compelled by a court your regulator considers unsafe. GitHub remains a fine place for open reach: keep the mirrors there if reach is what you need. The question we answered was only where the copy that matters must live.

Benchmark figures we publish – engines as columns, machines as rows, one identical model file – stay at localai.hex7.com/benchmark.html. The code behind them now builds somewhere whose jurisdiction matches its customers’.

Ask about an on-site assessment: privatelocalai@proton.me – in the Perpinyà – Girona – Barcelona corridor, and anywhere the wiring diagram needs to fit on one page.

Comments

One response to “Code on EU soil: why nine repositories moved to a Berlin non-profit”

  1. […] reading: Code on EU soil: why nine repositories moved to a Berlin non-profit and Your data, your […]

Leave a Reply

Your email address will not be published. Required fields are marked *