Codeberg has long stood apart in the crowded field of code hosting. Run by a registered nonprofit in Berlin, the platform offers Git repositories, issue tracking and continuous integration without ads or venture capital strings. Yet its latest move has sparked sharp debate. On July 22, 2026, Codeberg merged a proposal that explicitly bars cryptocurrency-related projects from its service. The change adds a new clause to the Terms of Use: “Content that harms the reputation of Codeberg, such as – but not limited to – cryptocurrency related projects.”
The decision did not appear from nowhere. It follows years of internal discussion captured in Codeberg/org pull request 1254 and earlier community forum threads. Supporters pointed to fraud risks, energy waste and repeated abuse that strains limited volunteer resources. One commenter noted the platform’s nonprofit status demands careful stewardship. Anything that invites regulatory scrutiny or damages public perception could threaten the tax-advantaged structure that keeps hosting free for thousands of open-source teams.
But not everyone agrees. Critics called the ban overly broad. “Please explain how cryptocurrency projects harm Codeberg’s reputation,” wrote nekogirl on July 23. Others worried about precedent. “This sets concerning precedent,” said johnoestmannmusic. “Nervous to recommend Codeberg.” The vote passed with eight hearts and six thumbs down. The pull request itself was merged the same day by contributor Gusted. Short. Decisive. And now official policy.
This isn’t Codeberg’s first stand. A companion proposal merged simultaneously restricts projects consisting mostly of code generated by large language models. Commenters there highlighted copyright uncertainty. One wrote, “The copyright issues alone are sufficient to be problematic for a non-profit.” Both changes reflect the same underlying tension. A small organization funded by donations and 1,691 paying members cannot absorb every controversy that draws legal heat or server abuse. Growth brings pressure. The platform now hosts far more than it did in 2019, when annual spending totaled roughly 300 euros.
Transparency has become a priority. In May 2026 the organization published its first public budget overview. Codeberg News detailed how the group has scaled without taking large sponsors or venture money. “We know that other projects have other approaches to working with money,” the post states. “For us, there are a few things to be proud of: funding diversity, funding humans, frugal spending and control.” No single owner pockets profits. Members vote on the budget. Cash auditors review every expense against the bylaws. That structure now faces real tests as membership exceeds 1,200 and project volume climbs.
The cryptocurrency ban echoes earlier moves by other independent forges. In 2022, sourcehut updated its terms to remove blockchain projects, citing similar concerns about resource consumption and platform reputation. Drew DeVault wrote at the time that such projects often led to abuse. Codeberg appears to have reached a parallel conclusion. Yet the wording chosen here is deliberately flexible. The phrase “such as – but not limited to” leaves room for case-by-case judgment. That flexibility may prove useful. Or it may invite accusations of arbitrary enforcement.
Meanwhile, major projects continue to trust the platform. The GNU Guix project completed its migration from Savannah in May 2025. After more than a decade on the older system, Guix adopted Codeberg’s Forgejo-based infrastructure for code, issues and pull requests. Ludovic Courtès described the move in a June 2026 blog post. “One thing in the proposal that didn’t trigger much debate though is the preference both for a free-software-based forge and for one hosted by a non-profit, Codeberg e.V. This choice is very much in line with the Guix ethos.”
Success has not been effortless. Guix now sees more than 500 pull requests per month. Roughly 10 percent of its 6,400-plus issues remain open. The shift from email-driven patches to web pull requests required adjustment. Commit signing became mandatory for security reasons. New contributors arrived, but the backlog grew. Still, Courtès reported comparable growth in commit authors and overall activity. The nonprofit model aligned with Guix values even as practical friction appeared.
Codeberg’s approach rests on three stated pillars. Diverse funding from members and small donations avoids outside influence. Compensation for key contributors addresses the “human scaling problem” that plagues volunteer projects. Frugal operations and member oversight keep spending aligned with mission. The 2026 budget plan, now housed in a public repository, marks the first time these numbers have been shared beyond the membership. The organization expects questions and criticism. It also expects continued growth.
Yet growth itself creates the very constraints that led to the crypto ban. Servers cost money. Moderation takes time. Legal risks cannot be ignored when the entity enjoys nonprofit privileges under German law. Cryptocurrency projects have historically generated both legitimate technical work and waves of spam, scams and proof-of-work miners that hammer infrastructure. Codeberg chose exclusion over constant triage. The decision prioritizes stability for the thousands of non-controversial free-software projects that rely on the service.
Reactions on X reflected the divide. Some users defended the nonprofit’s right to set boundaries. Others saw ideological overreach. One developer who had recently migrated expressed frustration at discovering the new rule. Another suggested the ban might push serious blockchain research elsewhere. The conversation continues in Codeberg’s own forum, where the original stance against cryptocurrency was first debated.
For industry observers the episode highlights a broader truth. Nonprofit code hosts operate under tighter margins than commercial platforms. They answer to members rather than shareholders. That accountability can produce principled stands that feel abrupt to outsiders. It can also foster genuine independence. Codeberg does not sell user data. It runs no tracking. Its roadmap bends toward community needs, not quarterly revenue targets.
The cryptocurrency prohibition will likely face challenges. Enforcement details remain vague. Definitions of “cryptocurrency related” were questioned during review. Projects already hosted may receive grace periods or appeals. And the platform must balance its new restrictions against its goal of welcoming free and open source code. The Terms of Use change is not exhaustive. It functions as a signal more than a detailed statute.
Still, the move fits a pattern. Codeberg has steadily professionalized its governance while preserving its volunteer spirit. It publishes budgets. It compensates contributors where possible. It engages its 1,691 paying members in votes that shape policy. The crypto ban represents one outcome of that maturing process. Whether it strengthens the platform or narrows its appeal will become clearer in the months ahead. For now, the organization has drawn its line. Projects that cross it must find another home.
And the rest of the open source world watches. Large platforms face their own pressures around resource abuse and controversial content. Smaller independent forges like Codeberg test alternative models in public. Their successes and missteps inform everyone else. In this case the lesson seems straightforward. When resources are finite and accountability is direct, hard choices follow. Codeberg made one. The community will live with the result.
WebProNews is an iEntry Publication