Open-source GitHub alternatives
Replacing GitHub is about more than moving Git repositories. Your team may also depend on pull requests, issue history, automation, packages, permissions, and the community around public projects. Start by deciding which of those workflows you need to own and which you are happy to keep with a service provider.
Gitea is worth evaluating when your priority is running a Git collaboration service under your own control. Our current shortlist starts with Gitea; it is a starting point for evaluation, not an exhaustive ranking of every GitHub alternative.
By OSS Hunter · An editorial starting point, with project facts in the live directory below.
Gitea: when to consider it

Gitea brings repository hosting, code review, issue tracking, and automation into a service you can run yourself. The practical attraction is control over where your development workflow lives. That control also means deciding who maintains the service and how your team recovers when it fails.
Explore Gitea: repository, license, and website
What to compare before replacing GitHub
Repository history
Try a representative repository with branches, tags, large files, and submodules. A successful clone alone does not prove that your complete workflow has moved.
Issues and reviews
Gitea provides a GitHub migration workflow. Check the imported issues, pull requests, attachments, and user attribution against your own sample before agreeing on a cutover.
Automation
Gitea Actions aims for GitHub Actions compatibility, but similar syntax is not a guarantee that every workflow behaves identically. Test runners, secrets, artifacts, and third-party actions.
Team access
Map organizations, teams, repository permissions, and service accounts. Include the people who review code only occasionally, not just administrators.
Tradeoffs to plan for
A self-hosted forge does not automatically replace the reach of an existing public GitHub project. Consider whether contributors still need a mirror, where issues should be filed, and how you will keep that policy clear. For private repositories, compare administration effort with the control you gain.
A practical migration pilot
Move a non-critical repository first. Have one developer open a change, another review it, and your automation build and release it. Test a backup restoration before moving the repositories your business depends on. Keep the old repository available until the team has agreed which system is authoritative.
Agree on a small set of acceptance criteria before the trial. Give each requirement an owner, record the gaps you find, and keep a rollback path until the new workflow is proven. Our software migration guide can help you structure that decision.
Frequently asked questions
Can Gitea import a GitHub repository?
Gitea documents a built-in migration flow for GitHub. Use that guide, then validate the data your team relies on; repository migration and workflow migration are separate checks.
Will my GitHub Actions workflows work unchanged?
Do not assume so. Test the workflows and actions you actually use, including their runner requirements and external dependencies.
Should we self-host just to reduce subscription costs?
Compare hosting, storage, backups, upgrades, and staff time alongside subscription costs. Ownership can be valuable, but an unmaintained service is not a saving.
How we approach this comparison
We start with the projects currently in the OSS Hunter directory and explain where to investigate fit. Inclusion is not a certification of security or a guarantee of feature parity. We link to the project and its documentation so you can inspect the source and verify the requirements that matter to you. Paid placements are disclosed; a placement is not a comparative score.
Official documentation
Continue your research
Choosing an open-source alternative · Self-hosting readiness checklist
Google Analytics alternatives · Figma alternatives · Slack alternatives · Microsoft Teams alternatives
