Harvey(opens in a new tab) serves more than 1,000 customers and 74,000 users in more than 58 countries, enhancing high-stakes legal workflows with AI. Early on, Bhavesh Kakadiya — Harvey’s head of product engineering — saw a potential bottleneck forming: document scale, user experience (UX) performance, and compliance readiness were all going to reach breaking points if the company continued to grow at its current pace.

Kakadiya had worked with PSPDFKit, now Nutrient, at a previous company, and he knew exactly when to bring Nutrient in. “Once we hit scale, we brought out the hammer,” he said.

Why early infrastructure couldn’t keep up

As Harvey accelerated its growth, the company’s early document pipeline ‌of ‌an open source, iframe-based stack began to show real strain. At the same time, Harvey’s usage curve was pointing sharply upward, and the company needed a system that could scale predictably and automatically without turning into a DevOps tax.

Compliance introduced a second pressure point. Harvey’s customers include some of the largest law firms in the world, each with strict requirements around data security, auditability, and deployment flexibility. Open source or in-house tooling couldn’t support that level of scrutiny, leading Harvey to seek a vendor that could check the enterprise boxes.

And finally, Harvey’s product vision demanded a far more sophisticated frontend experience than open source tools could support. Real-time highlighting, precision rendering, and the kind of visual accuracy lawyers expect all required technologies that open source libraries couldn’t handle at scale.

All three pressures — ‌scaling demand, enterprise compliance, and advanced user interface (UI) expectations — forced Harvey to rethink its document foundation.

Rebuilding for scale, speed, and compliance

Kakadiya had worked with Nutrient before, so when Harvey reached a stage where performance and scale were particularly crucial, he knew exactly who to call. Harvey wasn’t looking for a basic PDF tool — the company needed a foundation partner that could support explosive growth without slowing the product or the team down.

From the start, scalability was non-negotiable. As Harvey’s customer base expanded and document volume grew by roughly 50 percent month over month, Nutrient quietly absorbed that growth in the background, enabling Harvey to scale without building heavy internal infrastructure. Rather than battling document performance issues, the team focused on product innovation and customer experience. This became a blueprint for how fast-moving AI companies should think about document infrastructure: build once, scale silently.

On the frontend, Nutrient unlocked an experience that went far beyond basic PDF viewing. Harvey delivered dynamic, real-time, client-side interactions within documents — including highlighting, opacity changes, and smooth in-document updates that typically break down at scale. When reflecting on the frontend experience, Kakadiya recalled that “real-time highlighting isn’t supposed to look this smooth in a browser, but Nutrient somehow made it happen.” These weren’t generic UI enhancements; they were purpose-built for lawyers working directly inside dense legal documents, giving them speed and clarity that legacy tools simply couldn’t match.

Just as critical was compliance. Harvey’s customers are major law firms and enterprise legal teams with strict security and infrastructure requirements. “Compliance isn’t optional,” said Kakadiya. Nutrient made it possible to offer compliant, self-hosted-friendly workflows that meet enterprise legal standards. This wasn’t just about checking feature boxes; it was about earning trust with firms that won’t even consider tools that aren’t built for their regulatory reality.

The result was a rare combination: extreme scale without operational drag, differentiated document experiences(opens in a new tab) lawyers can rely on, and enterprise-grade compliance that opened doors with the world’s top firms. Nutrient didn’t just support Harvey’s growth; it made that velocity possible.

What changes when the document layer just works

With Nutrient in place, Harvey no longer has to worry about whether the document layer can keep up with demand. The system absorbs rapid growth, up to 50 percent month over month, without increasing operational load. Engineers no longer spend cycles maintaining iframes or debugging open source quirks, and product teams can release features with confidence, knowing the underlying engine is stable, accurate, and compliant.

For end users, the impact is immediate. Lawyers get a cleaner, more responsive viewing experience with precise rendering and dynamic UI behaviors that make complex documents easier to navigate. And for Harvey’s biggest customers, large law firms and enterprises with strict compliance requirements, Document Engine provides real reassurance.

Ready for the next stage of growth

Harvey’s growth demanded more than a document viewer — it required an enterprise-ready engine built for velocity, precision, and scale. With Nutrient, Harvey delivers a best-in-class experience for legal teams while effortlessly absorbing near-exponential growth without breaking a stride.