Cursor Enterprise Results: NVIDIA, Salesforce, Stripe

Cursor's customers page reports adoption at large scale across the enterprise. The four headline numbers below all come from Cursor's own published material, so read them as vendor-reported reach rather than independently audited counts.

The 93% preference and the 100-million-lines-a-day figure are the kind of claims worth flagging as Cursor-reported when you put them in front of a buyer. They are real published statements, not measurements you can reproduce from the outside.

NVIDIA CEO Jensen Huang has named Cursor directly in public remarks. Cursor cites him on its customers page; the quote below is attributed to him.

Per the same remarks, every one of NVIDIA's roughly 40,000 engineers is now assisted by AI, with productivity up "incredibly." NVIDIA runs Cursor inside its own guardrails: it uses hooks and other enterprise controls to keep development activity within its compliance boundaries.

Salesforce reports broad adoption and roughly 2x gains in both code quality and velocity. Cursor's case study puts more than 90% of Salesforce engineers on the tool, across about 20,000 developers and a monorepo near 30 GB.

Cursor credits its codebase indexing with making one of the world's largest monorepos workable for agents - a ~30 GB tree is where indexing quality stops being a nicety and starts gating whether the tool is usable at all.

Stripe's story is reliability-first. The team operates against a stated target of 99.99999% uptime, so any tool that touches the codebase has to clear a high bar before it earns trust. Cursor reports that it reduced setup and debug time and helped Stripe reach a five-year high in developer sentiment.

• Reliability bar: a stated target of 99.99999% uptime sets the context for everything else.
• Less setup and debug time: reported reductions in the slow parts of the loop.
• Developer sentiment: a reported five-year high.
• Faster prototyping: prototypes in hours rather than days.

Stripe also reports a second-order effect: Cursor "opened up new skill sets." Front-end engineers started contributing to back-end work, and an iOS engineer began exploring another part of the stack. That mobility is harder to measure than a velocity number, but it is the kind of change teams notice in who can pick up which ticket.

Cursor reports that about 40% of its own merged PRs are created end-to-end by cloud agents - opened, iterated and landed without a human writing the code by hand. This is Cursor reporting on Cursor, so read it as a vendor dogfooding claim.

The inflection was Cloud Agent Artifacts. Cursor reports that the merged-PR share from cloud agents roughly tripled after that shipped. By about March, Cursor says roughly 99% of its generated code came from cloud or IDE AI agents rather than being typed by hand.

Most figures on this page are customer-reported or Cursor-reported. That does not make them false. It means the burden of context is on you: before any of this goes into a deal deck, sort the durable, third-party-verifiable facts from the perishable ones.