← all SaaS
Self-host GitHub Issues
Issue tracking (for code repos) ·
Category: git hosting, CI & dev tooling
GitHub Issues is the default issue tracker for OSS projects. Self-hostable replacements come bundled with full git hosting — you trade the GitHub network effects for control.
GitHub Issues pricing anchor: Free for public repos; $4/user/mo for private (Team).
- GitHub
- ★ 55.5k · last commit today · 2777 open issues
- License
-
MIT - Setup time
- 10min (single Go binary or docker-compose)
- Monthly cost
- $5 VPS easily — very low footprint.
Migration sketch. Gitea → Site Administration → Migrations → New Migration → GitHub. Paste a GitHub PAT; it pulls repos with issues, PRs (as issues), labels, milestones, and wiki.
Good fit forTeams that want a GitHub-shaped experience including code hosting + CI (Gitea Actions).
Weak atSmaller integration ecosystem than GitHub.
- GitHub
- ★ — · last commit unknown
- License
-
MIT (with copyleft for some modules) - Setup time
- 10min (Gitea-compatible images)
- Monthly cost
- $5 VPS.
Migration sketch. Identical to Gitea — Forgejo is a community-governed soft fork. Use the same Migration UI with a GitHub PAT.
Good fit forTeams that prefer a community-led governance model over Gitea's company-led one.
Weak atSame gaps as Gitea (smaller integration ecosystem).
- GitHub
- ★ 24.3k · last commit today · 36 open issues
- License
-
MIT - Setup time
- 30-60min (Omnibus package or docker)
- Monthly cost
- $20+ VPS — wants 8GB RAM minimum, hungry stack.
Migration sketch. Admin Area → Settings → Import → GitHub. Provide a PAT; imports repos + issues + PRs (as MRs) + wiki + comments. Most fidelity of any option here.
Good fit forLarger teams that want issues + CI + container registry + everything in one stack.
Weak atResource-heavy; many features are EE-only (paid).
In a terminal? npx os-alt github-issues prints this table —
how the CLI works →