Candidate research

GitHub alternatives to research

Start with the job GitHub needs to do for you. Use the same acceptance checks for each candidate; do not infer a recommendation from a catalogue label.

These are editorial research candidates. A listing does not establish a tested integration, current price or universal winner. Use each profile’s dated evidence and run a small trial against your requirements.

What to test before switching

  1. Rehearse a branch, review, merge and release in a disposable repository.
  2. Check secret storage, required checks and collaborator access removal.
  3. Quote CI usage, storage, security features and maintenance responsibilities.

Build a shortlist

Candidate profile

GitLab

Compare this candidate against the same code collaboration requirements. Check the profile’s evidence and the selected plan before a trial.

Research GitLab →
Candidate profile

Bitbucket

Git repository hosting with a five-user free workspace and shared Pipelines allowances. Selected plan details checked 28 October 2026; see the profile for billing and limitations.

Research Bitbucket →
Candidate profile

Forgejo

Compare this candidate against the same code collaboration requirements. Check the profile’s evidence and the selected plan before a trial.

Research Forgejo →

Keep the switch reversible

Export a small sample, verify it can be restored or imported, and keep the existing workflow available until the trial passes. Record the missing features and migration work before moving a team.

Check the budget and evidence

The 9 October pricing receipt records source observations for 20 tools with their currency and billing scope. It does not verify every tool here. For any other candidate, check the vendor’s current plan and include usage, seats, integrations and ongoing maintenance in your quote.