Replit's Cycles creates internal marketplace

The important point is that Replit is monetizing not just software usage, but work that gets created and traded inside the product. Cycles turns the platform into a small internal economy, where a user can pay for compute, pay another builder to do a task, or buy an upgrade without leaving the browser. That matters because marketplace fees are lighter cost revenue than GPU heavy agent usage, and they deepen retention by keeping both project owners and freelancers inside Replit's workflow.

• Replit already sells subscriptions and metered infrastructure like deployments, databases, bandwidth, and agent credits. The marketplace adds a third stream on top, a take rate on transactions between users, which looks more like software marketplace revenue than cloud revenue.
  1 sacra 2 sacra
• The product fit is concrete. Someone building an app in Replit can post a bounty in Cycles for a bug fix, feature, or design tweak, then keep hosting, editing, and shipping that same app on Replit. The transaction and the ongoing app spend both stay on platform.
  2 sacra 4 sacra
• This is unusual among close peers. Bolt, Lovable, and Cursor mainly monetize subscriptions and usage. Lovable is pushing toward a forkable project ecosystem, but Replit already ties community activity to an internal currency and paid jobs, giving it a more explicit marketplace layer than most AI coding tools.
  1 sacra 3 sacra 4 sacra

Going forward, the companies that win this category will capture the full life of a project, from idea, to code generation, to deployment, to paid help from other users. Replit is pointed in that direction already. If more non technical builders start apps with agents, Cycles can become the bridge that turns one off creations into recurring infrastructure spend and repeat marketplace transactions.