Hosting incentives drive AI builder adoption
Marketing executive at Bolt.new on AI code editor adoption patterns
This reveals why Vercel can justify giving away more convenience earlier in the workflow than a standalone AI builder can. If a user goes from prompt to preview to custom domain to production on Vercel, the company can earn not just from the builder seat but from ongoing compute, bandwidth, storage, and team plans. That makes fast deployment and low friction handoff into hosting the core business loop, not just a product feature.
-
Vercel already monetizes the post build layer. It charges for infrastructure usage, paid seats, and v0 subscriptions, so every prototype that becomes a live app can turn into recurring hosting revenue. That is different from tools that mainly monetize chat credits or editing sessions.
-
The practical effect is product priorities around getting code live fast. Vercel has built around GitHub connected deploys, previews, rollbacks, environment variables, and auto deploy paths like Open in V0, all of which reduce the work between generated code and a running app.
-
That model contrasts with Bolt.new and Lovable, where users often generate an app, move the repo elsewhere, edit in Cursor or another IDE, and deploy on third party infrastructure. Those products can grow fast, but they do not automatically capture the long tail of infrastructure spend in the same direct way.
The next leg of competition is likely to center on who owns the path from rough prototype to durable production app. Companies with native hosting, database, auth, and deploy hooks are positioned to turn bursty AI generation into stable monthly infrastructure revenue, which should make vertically integrated builders harder to displace over time.