Codeberg’s decision this week to ban “vibe-coded” projects, meaning repositories dominated by AI-generated code, drew a bright line in the open-source community. The policy fits the platform’s non-profit charter, but it also nudges a real subset of developers to look for a plan B. Codeberg was itself the alternative many people picked when they left GitHub for a smaller, community-run home. If it’s no longer the right host for your work, these are the seven Codeberg alternatives worth setting up on a Windows, macOS, or Linux desktop in 2026.
Quick comparison
| Host | Best for | Free plan | Starting price/mo | Standout feature |
|---|---|---|---|---|
| GitHub | Widest ecosystem | Unlimited public and private | $4/user | Copilot and Actions |
| GitLab | End-to-end DevOps | Unlimited public, generous private | $29/user | Built-in CI/CD |
| Gitea | Self-hosted lightweight | Free (open source) | Free | 5-minute install |
| Forgejo | Community fork of Gitea | Free (open source) | Free | Federation preview |
| Sourcehut | Minimalist, no JavaScript UI | Trial | $2 (Alpha) | Email-based workflow |
| Bitbucket | Atlassian-integrated teams | Unlimited private for small teams | $3/user | Jira link |
| Radicle | Peer-to-peer, no server | Free (open source) | Free | No central host |
Why people are leaving Codeberg
Codeberg’s charter has always been more values-driven than most Git hosts. This week’s policy update makes the values explicit:
- The AI code policy. Codeberg banned repositories where AI generates the majority of the code and where humans aren’t the primary authors. Legitimate use is fine; overuse is not. Developers who build with AI-assisted flows have to draw the line themselves.
- Volunteer moderation. The community’s ability to enforce the policy is finite. Some contributors would rather be somewhere that treats the question with a written policy and appeals process, not case-by-case judgement.
- CI limits. Codeberg’s Woodpecker CI is generous for a non-profit but limited compared to GitHub Actions or GitLab CI. Larger projects hit the ceiling.
- Discoverability. Community-run hosts don’t feed the same discovery machines as the big commercial platforms. Some developers value that; others miss the stars, the trending page, and the reach.
- Federation is a promise, not a feature yet. ActivityPub-style federation between Forgejo instances is on the roadmap, but until it lands, moving between community hosts is still an export-import job.
The alternatives
GitHub, best for the widest ecosystem
GitHub is the alternative most Codeberg refugees try first, and the honest one for most projects. Public repos are free with unlimited collaborators, private repos are free for small teams, and Actions minutes on free tiers now cover most personal work. AI features (Copilot, Copilot Chat, Copilot Workspace) are opt-in, not enforced.
Where it falls short: Microsoft-owned. GitHub trained models on public repos with a permissive interpretation of license, which is precisely what pushed many people to Codeberg in the first place.
Pricing:
- Free: unlimited public and private repos, 2,000 Actions minutes/month for private repos
- Paid: Team from $4/user/month, Enterprise from $21/user/month
- vs Codeberg: bigger, faster, richer feature set, and the AI policy tradeoff runs the other way
Migrating from Codeberg: gh repo import or git remote set-url covers the code. Issues and PRs transfer via the GitHub Importer. Time for a mid-size project: 30 minutes.
Download: GitHub, GitHub Desktop for Windows and macOS
Bottom line: Pick GitHub if you want scale, ecosystem, and integrations, and are OK with Microsoft’s AI stance.
GitLab, best for end-to-end DevOps
GitLab ships a Git host, CI/CD pipelines, container registry, package registry, security scanning, and issue tracking as a single product. Free tier is generous, and the self-managed Community Edition is a real alternative to Gitea for people who want built-in CI.
Where it falls short: UI is dense. Free tier CI minutes have tightened over the years. Enterprise features hide behind paywalls.
Pricing:
- Free: unlimited public and private repos, 400 CI minutes/month
- Paid: Premium at $29/user/month, Ultimate at $99/user/month
- vs Codeberg: heavier, more corporate, and the CI story is far ahead
Migrating from Codeberg: GitLab’s importer supports Gitea/Codeberg repos with issues, MRs, and wiki. Time for a mid-size project: 20 minutes.
Download: GitLab, GitLab self-managed CE for Linux, Windows, macOS
Bottom line: Pick GitLab if you want a hosted DevOps stack and don’t want to bolt CI onto a lightweight Git server.
Gitea, best for self-hosted lightweight
Gitea is the small, fast, Go-based Git host that runs on anything with a filesystem and a Postgres or SQLite database. Sets up in five minutes on a Raspberry Pi and scales up to teams of hundreds without changing shape. Package registry, LFS, and Actions-compatible CI ship in the box.
Where it falls short: You run the server. Backups, upgrades, SSL renewals, and outages are your problem.
Pricing:
- Free: open source, MIT
- Paid: Gitea Cloud from $20/month for hosted, none if you self-host
- vs Codeberg: same underlying code (Codeberg is a Gitea instance) so the experience carries over cleanly
Migrating from Codeberg: Native “Migrate repository” clones the repo and issues with a single URL paste. Time for a mid-size project: 5 minutes.
Download: Gitea, self-host binary for Windows, macOS, Linux
Bottom line: Pick Gitea if you want the Codeberg feel on your own hardware without a cloud landlord.
Forgejo, best for community fork of Gitea
Forgejo is the Codeberg team’s own hard fork of Gitea, created to give the community a governance model independent of Gitea’s commercial arm. If you like Codeberg’s software but not its content policy, Forgejo self-hosted is Codeberg without the Codeberg policies.
Where it falls short: Still catching up to Gitea’s feature velocity in some areas. Federation is a preview.
Pricing:
- Free: open source, GPL
- Paid: none (Codeberg hosts the community instance)
- vs Codeberg: identical software, your own policies
Migrating from Codeberg: Direct import from any Gitea/Forgejo instance is one form field. Time for a mid-size project: 5 minutes.
Download: Forgejo, self-host for Windows, macOS, Linux
Bottom line: Pick Forgejo if you want Codeberg’s software with your own moderation rules.
Sourcehut, best for minimalist, no-JavaScript UI
Sourcehut by Drew DeVault is the “email is the API” Git host. No JavaScript required, CI via a well-documented YAML syntax, and mailing-list-style patch submission for people who prefer email-based review to pull requests.
Where it falls short: Deliberately spartan UI. Learning curve if you’ve never sent a git-format-patch email.
Pricing:
- Free: Alpha access with subscription
- Paid: Alpha at $2/month, patron tiers higher
- vs Codeberg: philosophically closer than most, more opinionated on workflow
Migrating from Codeberg: git push a new bare remote, then re-file issues manually. Time for a mid-size project: 20 minutes for code, longer for issues.
Download: Sourcehut
Bottom line: Pick Sourcehut if patch-by-email review appeals and you want a tiny, principled service.
Bitbucket, best for Atlassian-integrated teams
Bitbucket is the Git host most useful when the team already runs Jira and Confluence. Deep two-way linking with Jira issues, easy pipelines integration, and free private repos for small teams keep it competitive for internal projects.
Where it falls short: Weaker as a public open-source host. Fewer external contributors bother.
Pricing:
- Free: unlimited public and private repos, up to 5 users
- Paid: Standard at $3/user/month, Premium at $6/user/month
- vs Codeberg: enterprise-adjacent, quiet as a public community
Migrating from Codeberg: Manual git push and re-file issues. Bitbucket’s importer prefers GitHub/GitLab sources.
Download: Bitbucket, Sourcetree for Windows and macOS
Bottom line: Pick Bitbucket if Atlassian is already the team’s spine.
Radicle, best for peer-to-peer, no central host
Radicle is the peer-to-peer Git host with no central server. Repositories live on the network of nodes running Radicle, and no one company owns the platform. The 2026 desktop client and CLI landed with cleaner clone and push flows.
Where it falls short: Not for teams needing a familiar issue tracker and PR workflow. Discovery is limited by the network’s size.
Pricing:
- Free: open source, MIT
- Paid: none
- vs Codeberg: philosophically similar (community-owned), architecturally different (no central host)
Migrating from Codeberg: rad init inside a Codeberg-cloned repo turns it into a Radicle project. Issues don’t transfer; open new ones.
Download: Radicle, CLI for Windows, macOS, Linux
Bottom line: Pick Radicle if the point is not depending on a central host at all.
How to choose
- If you need scale and integrations: GitHub.
- If you want built-in CI/CD in one product: GitLab.
- If you want to self-host something like Codeberg: Gitea or Forgejo.
- If you like Codeberg’s software and want to keep the same UI you already know: Forgejo self-hosted.
- If you want minimal, no-JS, patch-by-email: Sourcehut.
- If you already live in Jira: Bitbucket.
- If you want no central platform at all: Radicle.
- Stay on Codeberg if: you’re happy with the AI policy, don’t need heavier CI, and value the non-profit charter above scale.
FAQ
Is Codeberg shutting down? No. The policy change is about what’s hosted, not the platform’s future.
Which alternative feels most like Codeberg? Forgejo self-hosted, because Codeberg runs Forgejo underneath.
Can I mirror a repo across GitHub and Codeberg? Yes. Push to two remotes or use each platform’s mirroring feature.
Is GitHub trustworthy if I don’t want AI training on my code? Public repos are covered by GitHub’s terms. If that concerns you, keep private, use GitLab or a self-hosted option.
Do these alternatives support ActivityPub federation? Forgejo has a preview. Others don’t, yet.
