You moved to Codeberg because you were tired of GitHub. You wanted open source. You wanted community. You wanted to believe that somewhere, somehow, there was a platform run by people who actually gave a damn about freedom.
Congratulations. They just banned cryptocurrency projects because they decided those projects are morally unacceptable.
Any platform you don’t control is a platform that can be taken from you — and the nicer the host, the harder the betrayal hits.
Let’s be clear about what happened. Codeberg, a volunteer-run, non-profit code forge built on principles of openness and decentralization, looked at a category of software projects and said: “We don’t like what you stand for. You’re out.”
This isn’t Microsoft making a cold corporate calculation. This is a community of volunteers imposing a moral judgment on what code is allowed to exist on their servers.
And that’s what makes it so chilling.
When GitHub does something you hate, you can rage against the corporate machine. You expected it. But when the idealists start drawing ideological lines? That’s when you realize the problem was never about who runs the platform. It’s about the fact that someone else runs it at all.
One commenter on the original Codeberg pull request nailed it: “Let this be a reminder to never trust any service — be it one ran by a billion dollar company, to one ran by volunteers. You will be eventually screwed over.”
The enemy isn’t greed or incompetence. The enemy is dependency itself.
Maybe you don’t care about crypto. Maybe you think those projects are scams and the world is better off without them. That’s fine. But you’re missing the point.
Today it’s cryptocurrency. Tomorrow it could be AI projects that someone deems “socially harmful.” Next year it could be security research tools that are “too dangerous.” The category doesn’t matter. What matters is that the precedent is now set: the platform will evaluate your project against its moral framework, and if you fail the test, you disappear.
No appeal. No due process. No guarantee your code survives.
Another user put it perfectly: “Running a coffee hosting service and putting your moral judgements on projects like this just seems childish and unserious.”
But here’s the twist nobody’s talking about: this ban is actually the best thing that could have happened to the open-source community. Not because the ban is good — it’s not — but because it rips the bandage off a delusion we’ve been nursing for years.
You don’t have a home on someone else’s server. You have a lease. And leases get terminated.
Every developer who has ever felt that warm, fuzzy sense of security because their repo lives on a “community-driven” platform needs to wake up. Codeberg didn’t betray its principles. It revealed them. The principle was never “we host everything.” The principle was “we host what we approve of.” The openness was always conditional, and the condition was always someone else’s judgment.
The answer isn’t to find a better host. There is no better host. The answer is to stop hosting on other people’s machines.
Self-host. Use Forgejo. Use Gitea. Use whatever lets you look at a server rack and say, “This is mine, and no committee of volunteers can vote my project out of existence.”
Yes, it’s more work. Yes, you have to manage backups, security, updates. Yes, it’s inconvenient. But convenience is the bait on every trap ever set. GitHub was convenient. Codeberg was convenient. And now a bunch of developers are scrambling to figure out where their code goes next.
If your project’s survival depends on the goodwill of strangers, your project doesn’t belong to you.
This isn’t just about Codeberg. It’s about every service you rely on without controlling. Your CI/CD pipeline. Your package registry. Your documentation host. Your project management tool. Every single one of them can wake up tomorrow and decide your work doesn’t align with their values.
The crypto ban at Codeberg isn’t a story about cryptocurrency. It’s a story about power — the power that flows invisibly through every platform you use, the power you pretend doesn’t exist because acknowledging it would mean you have to do something about it.
Now you have to do something about it.
Back up your repos. Spin up your own forge. Take the keys back.
Because the next ban might not target a category you don’t care about. It might target you.
FAQ
Q: Doesn't Codeberg have the right to decide what's on their own servers?
A: Absolutely. That's exactly the point. They have the right, which means they have the power, which means your project exists at their discretion. The question was never about their rights — it's about your risk.
Q: If I don't do crypto, why should I care about this ban?
A: Because today's moral objection is cryptocurrency. Tomorrow's could be AI tools, security research, or anything else a platform's maintainers decide is problematic. The ban sets the precedent that your project is subject to someone else's ethical review at any time.
Q: Isn't self-hosting unrealistic for most developers?
A: It's more work, yes. But 'convenient and not yours' versus 'inconvenient and fully yours' is the actual trade-off. Tools like Forgejo and Gitea make self-hosting a Git forge dramatically simpler than it used to be. The question is whether you value sovereignty enough to accept the overhead.