Replit Competing for Full App Ownership

Diving deeper into

Product & Engineering leader at Replit on churn & retention in vibe coding

Interview
The big competitors now are definitely Liveblocks, and there's V0, Bolt, Sigma, and Khanzi
Analyzed 7 sources

This competitor set shows that Replit was no longer just fighting code editors, it was fighting for ownership of the whole path from prompt to live app. The common thread across v0 and Bolt is that they turn a plain language request into working software fast, but Replit was strongest where the app also needed storage, auth, hosting, and an execution environment that stayed inside one product. That matters most for nontechnical users who can launch something useful, but cannot easily rewire it onto AWS or GCP later.

  • Liveblocks points to a different flank of competition. It is not a full app builder in the same mold as Replit, but a toolkit for adding real time collaboration like comments, presence, and multiplayer editing into software. When Replit leadership singled it out, that suggested collaborative software creation and shared app experiences were becoming core buying criteria in vibe coding.
  • v0 and Bolt each tied app generation to their own deployment rails. v0 lets users go from prompt to full stack app and deploy on Vercel. Bolt is built on StackBlitz WebContainers and runs the full stack in the browser. That makes competition less about who writes nicer code and more about who offers the shortest route from idea to running product.
  • Replit was also moving upmarket fast while this field was forming. Replit was estimated at $265M ARR by the end of 2025. Vercel was at $200M ARR by May 2025, with v0 helping expand beyond frontend hosting into AI app generation. The competitive line was blurring between dev tool, hosting platform, and app builder.

Going forward, the winners in this market are likely to be the products that make first creation easy and make second and third edits safe, reliable, and cheap. That favors platforms that own deployment, runtime, and key backend services, because once a nontechnical user has a live app with users, data, and auth, the builder becomes the infrastructure.