NVIDIA Media and Entertainment Global

PYLER

Risk Management

PYLER needed to verify brand safety across millions of videos per day, but keyword and rule-based moderation could not provide the semantic precision, throughput, or operating cost profile required for real-time advertising decisions.

10X reduction in operational costs
2 million videos daily
30 seconds (human benchmark) to just 0.011 seconds (AI)
reducing unsafe content exposure by 76.7%

Reported impact

Business outcome

PYLER processed 2 million videos a day, reduced unsafe content exposure by 76.7% for major advertisers, cut validation time from 30 seconds to 0.011 seconds, and used the consolidated NVIDIA stack to achieve a 10x reduction in operational costs while serving major global brands.

  • Cost Reduction
  • Risk Reduction
  • Scalability

Solution

PYLER built a multimodal video-intelligence platform on NVIDIA DGX systems, CUDA, NVLink-connected Blackwell infrastructure, NVIDIA NeMo, and Mission Control to create what it calls semantic primitives for brand safety. Video, audio, text, and metadata are embedded into a single representation, stored in a PostgreSQL vector database with pgvector, and served through SingleStore for high-throughput retrieval and policy evaluation. NVIDIA NeMo Curator automates data curation and filtering, while the DGX environment accelerates model training, hyperparameter search, and large-scale inference. The platform can then label and search millions of videos in near real time so advertisers can validate placements against trust-and-safety rules instead of relying on manual review or brittle keyword heuristics. The result is a neutral validation layer that scales across YouTube and emerging CTV inventory.

Data flow

Incoming video, audio, text, and metadata are embedded into unified vectors, stored in PostgreSQL with pgvector, retrieved and scored through SingleStore-backed services, and then evaluated by PYLER's policy logic to classify brand-safe or unsafe video environments in near real time.

Solution architecture

7 components · 4 layers
  1. Compute
    • NVIDIA DGX Platform Provides the core training and inference infrastructure for PYLER's multimodal models.
    • NVIDIA NeMo Supports model development and data curation for PYLER's semantic video workflows.
    • NVIDIA CUDA Accelerates the video embedding, search, and labeling pipeline.
  2. Storage
    • PostgreSQL with pgvector Stores vector embeddings for similarity search across time-aware video contexts.
  3. Serving
    • SingleStore Serves high-throughput retrieval and policy-evaluation workloads.
  4. Orchestration
    • NVIDIA NVLink Connects the GPUs so large multimodal training and inference jobs can run efficiently.
    • NVIDIA Mission Control Helps manage the DGX infrastructure used by the trust-and-safety platform.

Architecture clues

  • PYLER processes roughly 100 GB of video per day and 700 million videos cumulatively.
  • The move to DGX B200 delivered a 3x improvement in multimodal model training speed.
  • The team reduced model training iteration cycles from three months down to one.

Evidence from the source

Processed 2 million videos daily-equivalent to 60 years of content every 24 hours.
Reducing unsafe content exposure by 76.7% for major advertisers.
Validation times from 30 seconds (human benchmark) to just 0.011 seconds (AI).
leveraging NVIDIA Video Search & Summarization (VSS), and NVIDIA NeMo to achieve a 10X reduction in operational costs.
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
    3 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

    PYLER customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/pyler/
    Source type
    Vendor-published customer story
    Published
    Aug 25, 2026
    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. Prospeo

    PYLER Revenue, Funding & Valuation

    Independent secondary
    https://prospeo.io/c/pyler-revenue

    The page's Organization JSON-LD lists numberOfEmployees value 21.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

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