NVIDIA Software / SaaS Global

Perplexity

Enterprise Knowledge Search

Perplexity needed to customize frontier models for a search experience that returns direct answers instead of links, but rapid model releases, high query volume, and the need for low latency and high throughput made continuous post-training and retrieval optimization a core challenge.

20% improved over the base model on search
340 million queries per month
over 1,500 organizations have integrated Perplexity into their workflows

Reported impact

Business outcome

Perplexity processed 340 million queries a month, integrated into more than 1,500 organizations, and used NeMo-based tuning to produce Sonar models that improved search quality by 20% over newly released base models within days while preserving the low latency users expect.

  • Customer Experience
  • Scalability
  • Speed to Market

Solution

Perplexity used NVIDIA NeMo to create and refresh its Sonar family of online language models for the company's answer engine. The team relies on NeMo to scale supervised fine-tuning, direct preference optimization, and proximal policy optimization across a range of model sizes and architectures, including Llama and Mistral families. Retrieval-augmented generation connects those tuned models to live source material so answers stay current and grounded, while NeMo's distributed training support lets Perplexity experiment quickly after new open-source models appear. The same stack is also used to fine-tune open-source embedding models that improve the retrieval layer itself. This architecture lets Perplexity update both generation and retrieval in a matter of days, rather than leaving a web-scale search product tied to static generic models that are slower and less factual.

Data flow

Search intent and retrieved web context flow into Sonar models that were post-trained in NeMo with SFT, DPO, and PPO; tuned embedding models improve retrieval quality; and the resulting RAG pipeline returns concise grounded answers to users and enterprise integrations.

Solution architecture

4 components · 2 layers
  1. Compute
    • NVIDIA NeMo Provides the distributed post-training framework for Sonar and retrieval-model tuning.
    • Llama Serves as one of the frontier base-model families Perplexity fine-tunes for search.
    • Mistral Provides another base-model family that Perplexity customizes for answer quality and efficiency.
  2. Serving
    • Sonar Delivers the production online language models used in Perplexity's answer engine.

Architecture clues

  • Perplexity fine-tunes open-source embedding models to improve retrieval.
  • Perplexity scaled fine-tuning from 0.5B parameters to 400B+ parameters with NeMo.
  • The team uses SFT, DPO, and PPO to align search models.

Evidence from the source

As of October 2024, the platform processes an impressive 340 million queries per month.
NeMo allows Perplexity to quickly finetune a variety of open-source embedding models.
Perplexity has applied fine-tuning to frontier models, including Llama and Mistral model families, and is leveraging retrieval-augmented generation.
Within a few days of a new open-source release, the team had a new Sonar model that was 20% improved over the base model on search.
Transparency Evidence & methodology 90/100 reference value · 92% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. NVIDIA

    Perplexity customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/perplexity-enhances-model-performance-with-nemo/
    Source type
    Vendor-published customer story
    Published
    Aug 13, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date
  2. LinkedIn

    Perplexity | LinkedIn

    Third-party
    https://www.linkedin.com/company/perplexity-ai/

    The public company page includes numberOfEmployees value 1408 and a PostalAddress with streetAddress 115 Sansome St, addressLocality San Francisco, and addressCountry US.

    Source type
    structured profile
    Supports
    • Company size

Date evidence

  • Published on source page Aug 13, 2025 · NVIDIA · First-party
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.