Gitea
Open-source · self-hostable · replaces 3 SaaS tools on os-alt
go-gitea/gitea · alive · ★ 55.5k · last commit today · 2777 open issues
License: MIT
Good fit for Small teams escaping Bitbucket Cloud after the Server EOL with a low-footprint replacement.
Weak at No first-class Jira link; you'd run a separate issue tracker if you keep Jira on the side.
In a terminal? npx -y github:SolvoHQ/os-alt-cli bitbucket prints
the Bitbucket comparison table including Gitea.
how the CLI works →
Replaces these SaaS
- Bitbucket · Git hosting + Pipelines
Site Administration → Migrations → New Migration → choose Git/Generic, give Bitbucket repo URL + app password. Issues require a CSV export from Bitbucket (Repository settings → Export issues) and a manual import via the Gitea API. Pipelines do not port — re-author as Gitea Actions (GitHub Actions YAML).
- GitHub Issues · Issue tracking (for code repos)
Gitea → Site Administration → Migrations → New Migration → GitHub. Paste a GitHub PAT; it pulls repos with issues, PRs (as issues), labels, milestones, and wiki.
- GitLab · DevOps platform / git hosting + CI
Site Administration → Migrations → New Migration → GitLab. Paste a GitLab.com PAT; pulls repos, issues, MRs (as issues), labels, releases. CI does not transfer — Gitea Actions speaks GitHub Actions YAML, so port `.gitlab-ci.yml` jobs by hand.
README badges for the SaaS this replaces
Maintainers and forks: drop a badge in your README to link readers from the SaaS-comparison page back to your repo.