OpenAI is reportedly building a GitHub competitor. My first reaction: of course they are. My second reaction: every developer who has 100% of their workflow on GitHub should be sweating.
This isn't about whether OpenAI's product will be good. It's about what happens when AI companies start vertically integrating the entire developer stack.
The vertical integration play
Think about what OpenAI already controls: the model layer (GPT), the chat interface (ChatGPT), the API, the plugin ecosystem, and now potentially the code hosting and collaboration layer.
If they pull this off, a developer could write code with ChatGPT, store it on OpenAI's platform, deploy it through their infrastructure, and monitor it with their tools. End to end. No leaving the ecosystem.
Sound familiar? It should. This is the Google playbook from the 2010s. It's the Apple playbook from always. Build the whole stack, make leaving painful, extract maximum value.
Why GitHub is vulnerable
GitHub has been coasting. I say this as someone who uses it every single day and has for over a decade. The core product hasn't meaningfully evolved in years. Yes, Copilot exists. But GitHub's actual hosting, collaboration, and review workflows feel stuck in 2019.
Pull requests still work the same way. Code review is still painful for large changesets. Project management (Issues, Projects) is still worse than every dedicated alternative. The mobile experience is still an afterthought.
Microsoft acquired GitHub in 2018 for $7.5 billion. Eight years later, the biggest innovation is an AI autocomplete that OpenAI built for them. That's not a good sign.
Platform dependency is a trap
I learned this lesson the hard way with Heroku. Built an entire company's infrastructure on it. Then Salesforce acquired it and slowly let it rot. Migration took 4 months and cost us $180K in engineering time.
The pattern repeats: build on a platform, the platform changes priorities, you're stuck.
Here's what worries me about the current moment. GitHub isn't just where code lives. It's where CI/CD runs (Actions), where packages are hosted, where security scanning happens, where project management lives for millions of teams. The switching cost isn't just moving git repos. It's untangling an entire operational dependency.
If OpenAI launches a competitive product and starts offering better AI-native code review, smarter CI, and tighter model integration, GitHub will be forced to respond. That response might involve making the platform more closed, more expensive, or more dependent on Microsoft's AI stack.
Either way, you lose optionality.
What I'm doing about it
I keep my git repos portable. Every project I run can be mirrored to GitLab, Gitea, or any other host in under an hour. The key is not depending on GitHub-specific features for anything critical.
CI/CD: I run critical pipelines on self-hosted runners. GitHub Actions is convenient, but convenience is how dependency creeps in.
I also keep local backups of every repo. Sounds paranoid. But I've seen enough "impossible" platform failures to know that paranoia is just preparedness with a bad reputation.
The real lesson
The developer tool market is about to get very turbulent. OpenAI, Google, Microsoft, and Anthropic all want to own the developer workflow end to end. The companies that win will be the ones that own the data and the distribution.
Your job as a developer or engineering leader is to not be the product. Keep your code portable. Keep your CI flexible. Keep your options open.
The best platform strategy is the one that lets you leave.