NVIDIA Software / SaaS United States

Perplexity

Perplexity needed a production-grade inference stack for pplx-api that could serve open-source LLMs with lower latency, lower first-token delay, and lower operating cost while still scaling elastically across large GPU fleets.

$600,000 per year in savings
200% higher throughput on H100 compared with A100 in the same configuration
4x lower cost
Up to 3.1x lower latency

Reported impact

Business outcome

Perplexity achieved up to 3.1x lower latency and up to 4.3x lower first-token latency, cut serving cost by 4x, saved about $600,000 per year by re-pointing external API references to pplx-api, and doubled throughput when moving comparable workloads from A100 to H100 GPUs with FP8 precision.

  • Cost Reduction
  • Scalability
  • Speed to Market

Solution

Perplexity built pplx-api on NVIDIA-accelerated AWS infrastructure so developers could call open-source language models through a low-latency API instead of managing their own inference clusters. The serving layer runs on Amazon P4d and P5 instances backed by NVIDIA A100 and H100 GPUs, and NVIDIA TensorRT-LLM applies optimizations such as FlashAttention, masked multi-head attention, quantization, and tensor parallelism to improve both context processing and token generation. NVIDIA AI Enterprise supplies the production-ready software base around those optimizations, while AWS-integrated Kubernetes scales the service across hundreds of GPUs. This combination gives Perplexity a faster and cheaper inference plane for real-time applications without sacrificing elasticity or uptime.

Data flow

Developer API requests hit pplx-api, where TensorRT-LLM-optimized model servers run on A100 and H100 GPU fleets in AWS. Kubernetes scales those services beyond hundreds of GPUs, and the optimized inference path returns tokens with lower latency and lower first-token delay than Perplexity's prior external API routing model.

Solution architecture

4 components · 3 layers
  1. Compute
    • NVIDIA A100 GPUs Provide the cost-effective baseline GPU infrastructure that powers pplx-api inference on Amazon P4d instances.
    • NVIDIA H100 GPUs Deliver lower latency and higher throughput for the most demanding inference configurations on Amazon P5 instances.
  2. Serving
    • NVIDIA TensorRT-LLM Optimizes LLM inference with GPU-aware attention, batching, and parallelism techniques to improve response speed.
  3. Orchestration
    • NVIDIA AI Enterprise Provides the secure production software platform around TensorRT-LLM and the surrounding inference stack.

Architecture clues

  • FP8 precision is used on H100-based deployments
  • TensorRT-LLM applies FlashAttention, masked MHA, quantization, and tensor parallelism
  • The service scales beyond hundreds of GPUs with Kubernetes
  • pplx-api is served on Amazon P4d and P5 instances

Evidence from the source

By leveraging NVIDIA H100 GPUs and FP8 precision on Amazon P5 instances, they can cut their latency in half and boost throughput by 200 percent compared to NVIDIA A100 GPUs.
Perplexity harnesses the power of NVIDIA's hardware and software to solve this challenge.
Perplexity was able to lower costs by 4X by simply switching their external inference-serving API references to call pplx-api, resulting in savings of $600,000 per year.
Pplx-api can achieve up to 3.1X lower latency and up to 4.3X lower first-token latency relative to other deployment platforms.
Transparency Evidence & methodology 100/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 value100/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 impact25/25
    5 metrics 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/
    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.