Endurain leaves Codeberg: outages, an AI rule and what it means for self-hosters

The self-hosted fitness tracker Endurain has moved its project from Codeberg back to GitHub. In a project update dated 9 October 2026, maintainer João Vitória Silva gives three reasons: outages at Codeberg, an unreliable self-run Forgejo runner, and a new AI rule from the association. We read the sources ourselves. Not everything circulating in newsletters matches them word for word.

Codeberg is the Git platform of the non-profit Codeberg e.V. Since a members' vote in July 2026, its terms of use (section 2 (1) no. 7) prohibit projects that mostly consist of code written by generative AI tools. The association cites unclear copyright, missing safeguards against harmful code and resource use. Whether a given project falls under it is decided, in unclear cases, by the association's board.

What the maintainer writes

Update 4 in the "feature freeze" series has a section called "Going back to GitHub". It lists:

repeated availability problems, mostly with SSH, Codeberg being down, and commits failing as a result
a Forgejo runner the team set up for ARM64 images and for jobs that hit time limits; it needed reboots, images did not build, and the Android APK build worked only some of the time
the members' vote on rules against projects "written and maintained with heavy use of LLMs" or that accept LLM contributions without oversight. Endurain uses AI tooling and accepts AI-assisted pull requests, and the team is not sure it complies

He adds two things. His GitHub account was blocked for three weeks without explanation. And the team ruled out hosting its own Forgejo or Gitea, because a single runner had already been enough work. The migration is done and v0.19.3 was released from GitHub. He is a Codeberg member himself and praises its goals.

What we checked

Statement	Source	Evidence bucket
Outages, SSH and commit failures at Codeberg	Endurain update 4, 9 Oct 2026	maintainer's claim, not measured by us
Forgejo runner unstable, APK build inconsistent	Endurain update 4	maintainer's claim
Endurain uses AI tooling and accepts AI-assisted pull requests	Endurain update 4	maintainer's claim
GitHub account blocked for three weeks	Endurain update 4	maintainer's claim
Vote 358 to 144, 14 abstentions, about 50 % of active members	Codeberg blog, 23 Jul 2026	verified (the association's primary source)
Terms of use: projects that "mostly consist of code written by generative AI-tools" are prohibited	TermsOfUse.md, section 2 (1) no. 7	verified (read by us, 9 Nov 2026)
Codeberg repository archived, GitHub repository active (push 8 Nov 2026, AGPL-3.0, 38 commits since 10 Oct)	Codeberg and GitHub API, 9 Nov 2026	verified (measured by us)
Endurain would in fact be affected by the rules	none	inference, open

The figure 358 to 144 is not in the Endurain text. It comes from the Codeberg blog, which also says the vote ran for 14 days and ended on 22 July 2026.

Where Endurain's quote and the wording differ

The phrase "written and maintained with heavy use of LLMs" appears in the Codeberg blog, in a list of cases that may no longer be welcome there. It is informal guidance. The binding sentence in the terms of use speaks of projects that mostly consist of AI-written code. We found no wording in either text that forbids accepting AI contributions without oversight. The blog puts maintainers who accepted other people's AI contributions among the cases where being affected is unlikely, provided the project does not otherwise lean heavily on LLMs.

That does not refute Endurain's concern. The association says it will apply the rules case by case, and the maintainer finds them open to interpretation. It only shows that the move is the project's own risk assessment, not an eviction. None of the sources reports an order against Endurain.

What it means for us

We run Gitea ourselves at git.senn-gruppe.com, on a dedicated host with a runner. Our operations note of 11 October 2026 lists Gitea 28.1.0 and gitea-runner v5.0.0 there. A platform in your own house does not take away maintenance or outages. That same evening Gitea was unreachable for about 100 seconds because the nightly update job recreated the containers; anyone pushing in that window got a 502. That is the kind of effort Endurain did not want to carry.

In return, no third party's terms of use can change by members' vote. Which rules apply to AI contributions in our repositories is our own decision. What share of our code is AI-written we have not measured, and we say nothing about it here.

Anyone choosing a forge should answer three questions first. What do the terms say about AI code, and who decides in a dispute? How much operations work are you willing to carry if you host yourself, runners included? And what happens if the service blocks your account, as the maintainer says GitHub did to him? A mirror on a second platform answers the last one. By his own account, Endurain already had GitHub as a backup.

An introduction to running it is in Git in-house with Gitea and Forgejo. More posts on running your own infrastructure are collected in the hub Servers, Proxmox and network. If you want to review where your code lives and which rules apply there, our offer is under Services.

The open question stays the same for every team: do your platform's terms and your own contribution rules say how AI-written code is handled? If not, settle it before the next move.