Lovable says annual run-rate revenue has exceeded $600 million

Lovable has crossed $600 million in annual run-rate revenue, co-founder Fabian Hedin said at the HumanX summit in Amsterdam. The vibe-coding platform had reported a figure of about $500 million in June, marking its latest disclosed revenue milestone.

Hedin said the startup has concentrated on expanding its enterprise business and claimed that two-thirds of Fortune 500 companies now use the product. Microsoft, NVIDIA and Deutsche Telekom are among the named customers.

From code generation to product delivery

Hedin drew a distinction between Lovable and tools such as Codex or Claude Code. Those products can output code, he said, whereas Lovable’s output is intended to be a product and, increasingly, a business.

The company’s proposition includes hosting, deployment and app scaling alongside creation. Hedin said applications made by Lovable users collectively receive nearly one billion views each month, about an order of magnitude more than Lovable itself.

The commercial momentum follows the valuation signal described by Lovable’s rising vibe-coding market valuation as the market for vibe-coding platforms attracted greater investor attention.

Funding and enterprise adoption

Lovable has raised more than $700 million through two funding rounds completed eight months apart. In December, it raised $300 million from Menlo Ventures and CapitalG at a $6.6 billion valuation.

In August, the company raised a further $400 million from Menlo Ventures and the Scaleup Europe Fund at a $13.3 billion valuation. The two transactions provide the financial context for its push into larger organizations.

What businesses should evaluate

Lovable’s reported figures place the focus beyond prompt-to-code generation. Organizations assessing these platforms can examine whether they support the operational work named by Hedin: hosting, deployment and scaling apps once they reach real users.

For business teams, the practical implication is to assess AI application platforms against the complete path from creation to running and scaling a product, rather than treating generated code as the final deliverable.