AI coding tools are increasingly becoming the place where developers write and modify software. SpaceX-owned Cursor now wants to bring code hosting into that same environment, potentially challenging GitHub’s position as the center of the software development lifecycle (SDLC).
The company, earlier this week, launched Origin, an early-beta code-hosting platform that brings repositories, pull requests, and code browsing into its AI coding environment, on the same day that Microsoft-owned GitHub faced an outage for nearly eight hours, disrupting several of its services, including Actions, API requests, Git operations, and Copilot.
The move puts Cursor and GitHub on opposite sides of the same software development stack. GitHub built its position as the code-hosting and collaboration platform before expanding into CI/CD, security, project management, and AI-assisted development. Cursor is moving in the opposite direction, starting with an AI coding environment and adding code hosting around it.
In essence, that means Origin wants to change the traditional software development model, where developers typically use GitHub as their codebase and collaboration layer while relying on separate tools for coding, AI assistance, and other parts of the development lifecycle.
The rationale is that Origin’s model could reduce the number of tools involved in writing, reviewing, and managing code by bringing those workflows closer to the AI agents that are increasingly taking on software development tasks.
For enterprises and their CIOs, however, the question is whether Origin’s tighter integration with AI agents makes the code-hosting layer compelling enough to justify moving core development workflows away from a mature platform with a broader ecosystem and established enterprise controls, and eventually rethink where their canonical codebase should live. As of today, analysts say GitHub remains the safer enterprise choice.
Primarily because Origin is still in early beta and doesn’t match GitHub’s depth in enterprise controls, compliance, audit, and third-party integrations, said Manoj Chandra Jha, principal analyst at Nord-IQ Research.
Specifically, it lacks enterprise controls and security capabilities, such as branch protection and rulesets, CODEOWNERS, required reviewers, signed commits, SSO, SCIM, granular roles, IP allowlisting, audit logs you can ship to a SIEM, secret scanning with push protection, dependency alerts, SBOM, package registries, and GitHub’s broader CI/CD ecosystem, echoed Advait Patel, senior site reliability engineer (SRE) at Broadcom.
This is despite Origin’s integrations with Depot and Buildkite to support CI, Patel said, adding that “trusting a third party for CI” could introduce additional trust and operational considerations.
Another challenge for enterprises, when moving to Origin, would be reproducing the depth of GitHub’s Actions ecosystem, self-hosted runners, and integrations such as OpenID Connect (OIDC) for connecting CI workflows to cloud accounts, Patel further pointed out.
Beyond these capabilities, the senior SRE cautioned that CIOs would also need to consider compliance and operational safeguards, including certifications such as ISO 27001, data-residency options, clear terms on whether hosted code can be used to train AI models, and FedRAMP support for public-sector customers.
Those considerations, Patel added, should also extend to requirements around backup and restore guarantees, recovery point and recovery time objectives (RPO and RTO), a published SLA, an established incident history, and a documented way to export code in bulk.
That option to export code, according to Jha, is particularly important because Origin’s tight integration between AI coding and code hosting could also create a new form of vendor lock-in, where a single AI vendor ends up controlling the entire development loop, from writing and modifying code to hosting and managing it.
There are other reasons to consider GitHub over Origin despite its promise of less tool switching to deliver a simpler, tighter development workflow.
For its initial release, Origin still relies on GitHub for parts of the development workflow, meaning enterprises adopting it would not necessarily replace GitHub outright but might end up running two systems in parallel. That could limit some of the tool-consolidation benefits Origin is designed to offer while adding another layer of integration and management for engineering teams, Patel pointed out.
And that distinction may become an important factor in Origin’s enterprise adoption, echoed Jha.
Rather than treating Origin as a replacement for GitHub, CIOs should keep GitHub as the system of record while testing Origin on lower-risk repositories and expanding its use only as its enterprise capabilities mature, he advised.
That approach, however, could change if GitHub responds by building tighter AI-agent workflows of its own, Jha added.