Cursor launches Origin code hosting platform as GitHub outage exposes opening in AI coding race

Cursor unveiled its own code hosting platform, Origin, on Monday, just three and a half hours after GitHub experienced a six-hour-and-forty-two-minute global outage. During the outage, GitHub's status page showed an error rate of nearly 20% for pull requests, issues and the API, and close to 50% for archive and raw file downloads, according to GitHub's incident log. Not only did the outage halt GitHub's services, but it also disrupted Copilot, GitHub's AI-powered coding assistant.

Origin is designed to host code repositories and deploy them to Vercel via Cursor Origin, which is itself hosted on Vercel. This launch came at a perfect time, as the GitHub outage exposed an opportunity for Origin to stand out in the AI coding race. Matt Palmer, a Cursor employee, quipped on Twitter that they had planned to release Origin earlier but were delayed by GitHub's problems.

Origin functions within a new Codebase tab in Cursor. Teams create a codebase, which becomes part of its URL, and push to it via the command line. Origin then provides the necessary machinery, including the service layer that wraps Git and handles storage, permissions, checks and merges. Pull requests, timelines, commits, checks and files changed are all available, and reviewers can read the diff, leave comments and merge, without ever leaving the editor.

Around these core features, Origin integrates three key components: Vercel for preview deployments of pull requests, Depot for continuous integration, and Buildkite for executing existing GitHub Actions workflows unchanged. This compatibility layer is crucial, as it enables Origin to stay true to the existing workflows that teams have already established, rather than forcing them to overhaul their build systems or deployment pipelines.

The smartest design choice in Origin is its decision to remain a read-mostly mirror of GitHub rather than competing for source control authority. Origin connects to a GitHub organization, allowing users to pick repositories, which then appear alongside Origin-native ones. Pushes continue to go to GitHub, which remains the source of truth for any work that begins there. Access permissions mirror GitHub's existing read and write settings, and pull request conversations sync in both directions.

This approach allows teams to try Origin without risking their existing workflows or incurring significant costs. If Cursor's review experience proves better than GitHub's, the source of truth will eventually follow the attention, making Origin a compelling option for engineering organizations looking to explore AI-powered code collaboration.