Ask HN: Alternatives to GitHub

Hacker News Discussion ↗

Frustration with GitHub’s outages, AI-heavy direction, and lock-in around Actions is pushing many developers to evaluate alternative code forges. Participants compare hosted and self-hosted options such as GitLab, Gitea, Forgejo, Codeberg, Bitbucket, SourceHut, and newer federated platforms like Tangled, alongside standalone CI systems and “forgeless” workflows that keep issues and PRs in Git itself. A recurring theme is the trade-off between GitHub’s network effects and convenience versus greater control, reliability, and ideological alignment (for example, Codeberg’s anti-LLM stance) offered by smaller or self-hosted platforms.

Overall sentiment about GitHub

  • Many are frustrated by recent unreliability, AI “slop,” and lock‑in via Actions and integrations.
  • Others argue outages are overblown and that switching has real costs, especially for larger orgs.
  • Network effects (contributors, discoverability, unified notifications) are seen as GitHub’s biggest moat.

Self‑hosted forge alternatives

  • Forgejo, Gitea, and GitLab Community Edition are the main GitHub‑like self‑host options.
  • Forgejo/Gitea praised as lightweight, fast, and easy to run on small VPS or homelab; GitLab seen as heavier but more feature‑rich, especially for CI.
  • Some report multi‑year positive experiences with self‑hosted GitLab; others warn of maintenance burden, upgrade pitfalls, and frequent security updates.
  • Several people mirror from a self‑hosted origin (Forgejo/Gitea/GitLab) to GitHub for visibility.

Hosted forge alternatives

  • Codeberg (Forgejo‑based, non‑profit, FOSS‑oriented) is a popular choice for open source, but:
    • Limited or discouraged private repos.
    • Uptime is criticized by some as worse than GitHub.
  • Other hosted options mentioned: Bitbucket, SourceHut, Codefloe, Worktree (Canada/OVH‑based), Gitoro, upd.dev, Google/AWS/Azure offerings, and Tencent/Gitee (with geopolitical concerns raised).

CI/CD and GitHub Actions alternatives

  • GitLab CI widely praised; Forgejo and Gitea now offer Actions‑style CI (not fully protocol‑compatible).
  • External CI tools: Woodpecker, Drone, classic vendors (CircleCI, Semaphore), Buildkite (with a GH Actions “adapter”), AWS CodeBuild, RocketRunner (GitLab runners as a service).
  • Several experimental or niche tools: DSCI (monolithic forge+CI), preloop (local/self‑hosted GH Actions replacement using microVMs).

Decentralization, federation, and non‑git options

  • Strong interest in federated/social coding (Tangled on atproto, Radicle, nostr‑based gitworkshop, rngit).
  • Some argue a truly decentralized “GitHub layer” is the real solution, not just moving to another central forge.
  • Non‑git VCS and integrated systems: Fossil and Pijul highlighted for built‑in issues/wiki and simple self‑hosting.

Codeberg and AI/LLM policy debate

  • Codeberg bans projects that are mostly LLM‑generated or tightly tied to the LLM ecosystem; interpretations differ:
    • Some claim “any AI use” violates ToS.
    • Others quote policy/text stating partial AI assistance is allowed; only heavily AI‑generated or AI‑centric projects are disallowed.
  • This strict stance is a major draw for some and a deal‑breaker for others.