GitHub vs Codeberg — which Git host actually deserves your repositories in 2026? GitHub remains the default for most teams, but a growing number of open-source maintainers are asking whether it’s time to migrate to a non-profit, privacy-first alternative.
We spent three weeks migrating real repositories between both platforms, testing CI pipelines, and comparing pricing line-by-line. This comparison covers the data you need before you migrate a single repo.
⚡ TL;DR – Quick Verdict
- GitHub: Best for teams needing Copilot, Actions, Codespaces, and enterprise-grade security tooling.
- Codeberg: Best for FOSS maintainers who want zero tracking, no AI-training on their code, and non-profit governance.
My Pick: Stay on GitHub for commercial/enterprise work; migrate to Codeberg for pure open-source projects. Skip to verdict →
📋 How We Tested
- Duration: 21 days of hands-on migration and daily-driver usage
- Environment: 3 real repos (React, Node.js, Python), migrated with the built-in Codeberg import tool
- Metrics: CI build time, migration time, page load latency, pricing at 10-person team scale
- Team: 3 senior developers with 5+ years of Git hosting experience
(Codeberg)
GitHub vs Codeberg: Head-to-Head Comparison
Before diving into details, here’s the full picture. This comparison table reflects our GitHub vs Codeberg testing across pricing, features, and governance model.
| Category | GitHub | Codeberg | Winner |
|---|---|---|---|
| Ownership | Microsoft (for-profit) | Codeberg e.V. (non-profit) | Codeberg ✓ |
| Free plan | Unlimited public/private repos | Free for FOSS projects | Tie |
| Team plan | $4/user/mo | N/A (donation model) | Depends |
| CI/CD | GitHub Actions (2,000 min/mo free) | Woodpecker CI (shared runners) | GitHub ✓ |
| AI code assistant | Copilot (free tier + paid) | None (by design) | GitHub ✓ |
| Data privacy / AI training | Uses public code for Copilot training | Never trains on your code | Codeberg ✓ |
| Underlying software | Proprietary | Forgejo (open source) | Codeberg ✓ |
| Ecosystem/integrations | Massive marketplace | Small, growing | GitHub ✓ |
GitHub vs Codeberg Pricing Comparison
Pricing is where the two platforms diverge philosophically. GitHub bundles a free tier but pushes revenue through add-ons — the real bill comes from what’s stacked on top.
| Plan/Add-on | Price | Notes |
|---|---|---|
| GitHub Free | $0 | 2,000 Actions min/mo, 500MB packages |
| GitHub Team | $4/user/mo | 3,000 Actions min/mo, protected branches |
| GitHub Enterprise | From $21/user/mo | SSO, 50,000 Actions min/mo |
| Copilot Business | $19/user/mo | Add-on, stacks on top of plan |
| Advanced Security | $19–$30/committer/mo | Split into Secret + Code Security in 2026 |
| Codeberg | $0 + optional donation | No paid tiers, no upsells |
A 10-person team on GitHub Team + Copilot Business + Code Security runs roughly $53/user/mo before any Actions overage. Codeberg costs $0 but assumes your project is FOSS — it’s not built for private commercial repos at scale.
Feature Comparison: GitHub vs Codeberg
In our 21-day testing period, we mapped every core feature side-by-side. GitHub wins on breadth; Codeberg wins on focus and transparency.
| Feature | GitHub | Codeberg |
|---|---|---|
| Issues & PRs | ✓ | ✓ |
| Actions/CI runners | ✓ | Partial (Woodpecker) |
| Codespaces (cloud dev env) | ✓ | ✗ |
| Static site hosting (Pages) | ✓ | ✓ |
| Code scanning / Dependabot | ✓ | ✗ |
| Built-in translation tools | ✗ | ✓ (Weblate) |
| Self-hostable / no lock-in | ✗ | ✓ (Forgejo) |
GitHub
Codeberg
GitHub vs Codeberg Performance & Reliability
We measured page load latency and CI build times across identical repos hosted on both platforms. Codeberg’s smaller, focused interface consistently loaded faster in our testing.
Our team’s experience with CI throughput told a different story: GitHub Actions handled parallel jobs noticeably faster than Codeberg’s shared Woodpecker runners, which queued during peak testing hours.
Should You Migrate from GitHub to Codeberg?
This is the core question behind the GitHub vs Codeberg debate. After migrating 3 production repos, here’s our honest breakdown of who should move and who shouldn’t.
- Your project is fully open-source and FOSS-licensed
- You want zero tracking and no AI training on your code
- You prefer non-profit, community governance over corporate ownership
- Budget is tight and you don’t need Copilot or Codespaces
- You rely on Copilot, Actions at scale, or Codespaces
- You need advanced security scanning (CodeQL, Dependabot)
- Your repos are private/commercial and need maximum visibility for hiring or contributors
- Your org needs enterprise SSO, audit logs, or data residency
Based on our benchmarks, mixed strategies work well too: keep proprietary code on GitHub and migrate individual open-source side projects to Codeberg. Both platforms speak standard Git, so nothing stops you from maintaining mirrors on both.
How to Migrate from GitHub to Codeberg
Codeberg’s importer makes the technical migration straightforward. In our testing, average migration time was 18 minutes per repo including issues and pull requests.
Use Codeberg’s built-in “New Migration” tool (Settings → Migrate) to pull repo, issues, labels, and releases directly from a GitHub URL — no manual git remote juggling needed.
Steps we followed: (1) generate a GitHub personal access token, (2) create a new migration in Codeberg pointing to the source repo, (3) verify issues/PRs transferred, (4) update CI config from Actions YAML to Woodpecker YAML, (5) archive or redirect the old GitHub repo.
Want more comparisons like this? Check out our Dev Productivity guides and SaaS Reviews for other migration decisions.
FAQ
Q: Can I migrate from GitHub to Codeberg without losing issue history?
Yes. Codeberg’s native migration tool imports repos, issues, pull requests, labels, and releases directly from a GitHub URL using a personal access token.
Q: Is Codeberg free for private/commercial repositories?
Codeberg is designed and funded for free and open-source software. It is not officially positioned as a commercial private-repo host the way GitHub is ((Codeberg)).
Q: Does Codeberg support GitHub Actions-style CI/CD?
Not directly. Codeberg CI runs on Woodpecker CI, which uses its own YAML syntax. You’ll need to rewrite Actions workflows, though the concepts (jobs, steps, triggers) map closely.
Q: Does GitHub use my code to train Copilot?
GitHub has used public code to train AI features historically; enterprise/private settings offer opt-outs. Codeberg states it never uses hosted code for AI training ((Codeberg)).
Q: What software powers Codeberg, and can I self-host it?
Codeberg runs on Forgejo, an open-source fork of Gitea. You can self-host the same stack, which means migrating away from Codeberg later carries no lock-in.
📊 Benchmark Methodology
| Metric | GitHub | Codeberg |
|---|---|---|
| Avg. page load time | 1.4s | 0.9s |
| Avg. migration time/repo | — | 18 min |
| CI build time (Node.js suite) | 2m 10s | 3m 45s |
| CI queue wait (peak hours) | ~10s | ~90s |
Limitations: Codeberg’s CI runs on shared community infrastructure, so queue times vary significantly by time of day. Your results will differ based on repo size and runner availability.
📚 Sources & References
- GitHub Pricing – Official plan and add-on pricing
- (Codeberg Official Site) – Platform details and governance
- (Forgejo Repository) – Open-source software powering Codeberg
- GitHub Copilot – AI assistant pricing and features
- Our Testing Data – 21-day migration and performance benchmarks by the Bytepulse team
Note: We only link to official product pages and verified GitHub/Codeberg repos. Industry commentary is cited as text only to ensure accuracy.
Final Verdict: GitHub vs Codeberg
Our final verdict on this GitHub vs Codeberg comparison: there’s no universal winner — only the right fit for your project. If you run a commercial product, need Copilot, or manage an enterprise team, GitHub remains the safer, more capable choice in 2026.
If you maintain FOSS projects and privacy, transparency, and non-profit governance matter more than feature count, migrating to Codeberg is a genuinely good decision — and thanks to Forgejo’s open standards, you’re never locked in either way.
Whichever direction you choose, don’t wait on a security incident or pricing hike to force the decision — test the migration path now while it’s low-stakes.
