Version Control & Code Hosting
Version control and code hosting platforms store Git repositories and wrap them with pull or merge requests, code review, permissions and issue tracking.
3 results in Version Control & Code Hosting
Active Pro listings from this category appear first. Your sort applies within Pro and Free results.
Shortlists for Version Control & Code Hosting
Explore collections with tools relevant to this category, grouped by deployment, source model or workload.
Open-source CI/CD tools for engineering teams →
2 matching tools from this category
Self-hosted IT tools →
4 matching tools from this category
IT tools with an API →
4 matching tools from this category
How to choose Version Control & Code Hosting tools
Version control and code hosting platforms store Git repositories and wrap them with pull or merge requests, code review, permissions and issue tracking. Most now bundle CI/CD pipelines, package registries and security scanning, so the choice shapes much of the development workflow. They differ from local Git clients and editors because they are the shared, authoritative home of the code and its review history.
Who uses these tools
- Development teams collaborating through pull requests
- Platform engineers administering repositories and runners
- Open source maintainers reviewing outside contributions
Capabilities to compare
- Pull or merge request review with required approvals
- Branch protection and code owner rules
- Built-in CI/CD runners and package registries
- Secret scanning and dependency alerts
- Self-managed edition for on-premises hosting
Operating considerations
- Pipeline minutes and storage billed beyond free tiers
- Data residency of source code and build logs
- Migration of issues, wikis and pipelines, not only Git
- Single sign-on and user provisioning for large teams
Selection checklist
- Decide whether CI/CD should live in the same platform, then compare pipeline syntax and runner costs together.
- Test a migration of one repository with its issues, pull requests and history to see what survives.
- Check that branch protection, required reviews and audit logs meet your compliance requirements.
- Compare self-managed and cloud editions on upgrade effort, uptime responsibility and feature parity.
What belongs in this category: A product belongs here when it hosts shared repositories and manages review and access around them, as a cloud service or self-managed server, rather than only editing code locally.
Typical use cases
- Reviewing and merging feature branches with required approvals
- Hosting private repositories for a regulated on-premises team
- Accepting outside contributions to an open source project
- Running build pipelines triggered by every push
Trade-offs to model
- All-in-one DevOps platforms reduce integrations, while hosting combined with separate CI keeps each piece replaceable.
- Self-managed servers keep code on your infrastructure but require upgrades, backups and runner capacity planning.
Common mistakes
- Migrating repositories without the pull request history and issue links that explain past decisions.
- Leaving default branch settings that allow anyone to push directly to the main branch.
Version Control & Code Hosting on iThub in figures
iThub lists 5 tools in Version Control & Code Hosting. 3 of 5 are open source, 4 of 5 can be self-hosted, 5 of 5 have a free, freemium or open-source pricing model and 4 of 5 offer an API.
- Tools listed
- 5
- Open source
- 3
- Self-hostable
- 4
- Free to start
- 5
- With an API
- 4
- Web app
- 3
- Desktop app
- 4
Compare GitHub and GitLab Browse all code hosting tools Explore CI/CD tools
Continue the technical evaluation
Use the resources that match your decision stage. Profile data and linked sources were refreshed through November 13, 2026.
