Cursor launches Origin, GitHub alternative

Original Article ↗ Hacker News Discussion ↗

Cursor has launched Origin, a Git hosting service positioned as a more reliable, AI-integrated alternative to GitHub amid frustration over GitHub’s recent outages and scaling issues. Commenters are sharply divided: some welcome competition and potential performance gains, while many refuse to entrust source code to a Musk-controlled company, citing privacy, ethics, and fears about AI training on private repositories. Others argue that Origin currently offers little beyond a GitHub clone, and see more promise in self-hosted or decentralized forges like GitLab, Forgejo, Tangled, or Radicle to address long‑term concerns over lock‑in and control.

Product Scope & Differentiation

  • Many see Origin as essentially “GitHub but hosted by Cursor,” with near feature parity and deep Cursor integration.
  • Team members describe it as a Git hosting beta focused first on matching GitHub, with agent-focused features (agent-written code understanding, auto-merging PRs, agent swarms) promised “over the next weeks.”
  • Current limitations: repositories are private to Cursor teams, public browsing isn’t supported yet; GitHub linking is needed for sync. No Actions-equivalent yet, which some consider a deal-breaker.

Uptime, Performance, and GitHub’s Problems

  • Strong frustration with recurring GitHub outages, especially for enterprises heavily dependent on Actions/CI.
  • Some argue GitHub’s issues stem from Azure scaling constraints and AI-driven load; others blame poor architecture, practices, and Microsoft’s prioritization.
  • A few believe any smaller Git host will have better uptime simply due to lower scale; others doubt Origin’s ability to operate reliably at GitHub scale.

Trust, Ownership, and Musk Association

  • A major thread: strong refusal by many to host code with any Musk-controlled entity, citing ethical concerns, past data behavior, and perceived likelihood of unauthorized training on private code.
  • A minority explicitly state they trust Musk more than other tech leaders.
  • Some worry Origin increases supply-chain risk compared to existing options.

AI Training, Privacy, and Code Use

  • Broad suspicion that an AI company hosting git will inevitably train on hosted code, especially private repos and version histories.
  • Comparisons drawn to GitHub Copilot; some see all major AI players as similar risks and advocate self-hosting if integrity matters.
  • Questions raised about ToS, data usage, and whether code would feed Grok; lack of clear legal docs is noted as a concern.

Ecosystem, Lock-In, and Standards

  • Many commenters say GitHub’s real moat is integrations (CI, issue trackers, Sentry, etc.) and social/network effects, not raw git hosting.
  • Requests for GitHub API compatibility and standardized forge APIs so tools can more easily support multiple hosts.
  • Skepticism that a GitHub-like clone, even with better uptime, can overcome ecosystem lock-in.

Self‑Hosting and Decentralized Alternatives

  • Numerous calls to self-host (Forgejo, GitLab, Gitea, SourceHut) or adopt decentralized/federated systems (Radicle, Tangled/ATProto, Git over Reticulum).
  • Debate over practicality: decentralization appeals to a niche; most users still prefer centralized UX and integrated workflows.

Naming, UX, and Onboarding Concerns

  • Mixed reactions to “Origin” as a name: some praise its git connotation; others see ambiguity, SEO conflicts, and LLM confusion.
  • Complaints about SMS phone-number requirement, access blocks on registration, and Origin feeling rushed to capitalize on GitHub’s outages.