If you build software by describing it, the companies you describe it to are having the best fundraising year in the category's short history. As of late July 2026, Lovable is reportedly in talks to raise about $300M at a $13.2B valuation — double the $6.6B it set just seven months ago — after hitting a roughly $500M annualized revenue run rate in June, with Menlo Ventures expected to lead (TechCrunch). Replit raised $400M at a $9B valuation in March, roughly tripling its price from six months earlier, and says it's aiming for a $1B run-rate by year-end (Replit; FNEX). Emergent, the newer name, raised a $130M Series C. Every one of those numbers is a bet on the same thing — and it isn't the product you think it is.
The valuations price velocity, not a moat#
Read the round logic and one variable does all the work: how fast annualized revenue is compounding. Lovable's markup tracks its run rate going from a $100M ARR milestone last summer — reportedly the fastest any SaaS company has crossed it — to a ~$500M run rate this June (TechCrunch). Replit's $9B is priced against a $1B run-rate target. These aren't discounted-cash-flow numbers. They're velocity numbers: the market is paying for the slope of the line, not the width of the moat under it.
That matters because the thing being generated — the app — is portable. A Lovable or a Replit build is ordinary React, standard components, a normal repo you can, in principle, export and host anywhere. The generator is not the lock-in. So what, exactly, are investors valuing at $13.2B?
The moat isn't the code generator. It's everything wrapped around the code that's annoying to leave — the hosting, the database, the auth, the integrations. That's not a product feature. It's your switching cost, priced as their asset.
Why the raise is your risk, not just your tool's upside#
Here's the part the launch coverage skips. A raise this size has a job: consolidate the category and, eventually, capture the customers it already has. The capital funds enterprise sales, deeper hosting, managed databases, auth, and the long tail of integrations that make an app stay — because a company priced on run-rate velocity has to defend that slope, and the durable way to do that is to raise the cost of leaving.
For a funded startup racing the same clock, that's a fine trade. For a solo founder or a bootstrapped team, it inverts. The platform you pick this quarter is being financed specifically to make next year's version of you less able to move. The convenience that got you shipping — hosting, DB, and auth all handled — is the exact surface where lock-in accretes. Our head-to-head on Emergent vs. Lovable vs. Replit is about which builds fastest; this is about which one you can still walk away from in eighteen months.
The cheap hedge#
None of this is an argument against vibe-coding. It's an argument for using the moment. While three well-funded platforms are competing for you, you have leverage — on price, on export, on support — that evaporates the day one of them wins the category. Spend it now, and spend it on portability.
- Own the repo. Make sure you can export the generated code to a git remote you control, not just a platform-hosted project. If you can't get a real repo out, you don't own the app.
- Keep the data movable. Prefer a database you could point elsewhere — a standard Postgres you can dump — over a bespoke, platform-only store.
- Keep auth swappable. An auth layer you can repoint is the difference between a migration and a rewrite.
Run the own-your-code checklist before your app gets deep enough that leaving means starting over. The $13.2B headline is a story about how fast this category is compounding. Your job is to make sure that when it consolidates, you're a customer with options — not an asset on someone's cap-table math.
