Amjad Masad Doesn't Want to Sell Replit. That Matters for Every Indie Builder.
In a week when Cursor might sell for $60 billion, Amjad Masad said he would rather keep Replit independent. That stance says more about building in 2026 than any exit headline ever could
SpaceX wants to buy Cursor for $60 billion. That rumor dominated TechCrunch's StrictlyVC event in San Francisco this week. Every investor in the room had dollar signs in their eyes. Every founder was doing the mental math on their own AI coding tool. Then Amjad Masad took the stage and changed the subject.
The Replit CEO said he would rather not sell. He talked about fighting Apple and competing with Cursor directly. While the rest of the industry treats acquisitions like graduation ceremonies, Masad sounds like he wants to keep working on the actual product. Independence, in his view, is not a consolation prize. It is the goal.
Why Ownership Beats the Exit
This stance is almost rebellious right now. We are living through a gold rush where every promising AI tool gets measured by its price tag instead of its usefulness. The script is familiar. You build fast, grow big, and sell before the cracks show. Then someone else figures out the mess. Masad is refusing to read from that script. He wants to keep building Replit even though the market is waving a check big enough to buy a small country.
Replit has survived some brutal turns. It bet early on browser-based coding, then watched the AI wave rewrite every assumption about how people make software. Now it competes with Cursor, GitHub Copilot, and a dozen vibe-coding tools that spin up entire apps from a single sentence. Through all that, Masad seems to treat ownership as a feature. When you sell to a rocket company or a social media giant, your roadmap stops answering to users and starts answering to someone else's quarterly strategy.
Your Stack Needs an Escape Hatch
This matters for indie builders in a very direct way. Most of us are not running venture-backed startups with billion-dollar term sheets on the table. We are shipping side projects, launching micro-SaaS ideas, or prototyping between day-job meetings. We do not have time to migrate off a platform that suddenly changes its API, doubles its price, or folds into a division that loses funding three months later.
Platform risk is not theoretical. Developers who built businesses on Twitter's API before the Musk acquisition learned that lesson fast. Teams who trusted Heroku's free tier learned it too. When your coding environment, your deployment pipeline, or your database lives inside someone else's closed garden, you are renting your own product. The terms change overnight and the eviction notice is an email you get on a Tuesday.
Masad's reluctance to sell highlights exactly what builders should demand from their tools. You want to pack up and leave without rewriting everything. GitHub-native workflows, open-source runtimes, and code that lives in your own repo matter more than slick marketing. If the company that makes your favorite IDE suddenly pivots to enterprise defense contracts, you should still be able to ship on Friday. Botflow follows this principle. Code exports straight to your repo, the backend is fully open source, and you can self-host if the terms change. The tool should get out of your way when the relationship ends.
Build Like You Might Need to Walk
The best insurance against platform risk is not a legal contract. It is architecture. Choose backends that expose your data. Pick generators that spit out standard code you can host anywhere. Avoid black boxes that promise speed in exchange for lock-in, because the speed vanishes the moment the business model shifts. The work is only yours if you can move it.
Nobody cares which logo you click to start your project. What matters is whether you can finish it on your own terms. Masad wants to keep Replit independent so it can keep serving builders first. Own your tools and your code. Keep the option to walk away. That is the only exit strategy that actually protects the work.