OpenAI Media and Entertainment Asia-Pacific & Oceania

JioStar

Traditional recommendation systems were not enough to address the nuance of how viewers describe what they want to watch. JioStar needed fast, reliable, cost-conscious discovery for entertainment, live-sports moments, and detailed cricket statistics at very large audience scale and across multiple languages.

72.5 million concurrent live-sports viewers
More than 60% of our users use voice rather than text
more than 15 languages in about eight weeks
more than 500 million consumers

Reported impact

Business outcome

JioStar built and launched a conversational discovery experience for videos and cricket information across more than 15 languages in about eight weeks, giving viewers a voice-and-visual way to find entertainment, sports moments, and statistics.

  • Customer Experience
  • Scalability

Solution

JioStar built a conversational video and cricket-stat discovery assistant into JioHotstar using the OpenAI API. Viewers can speak or type requests about movies, shows, live-match moments, or cricket statistics, and receive results through a visual, conversational experience. The team framed production design as a balance of accuracy, latency, and cost, and put answer-scope guardrails in place. Its evaluation approach used a seed dataset expanded with model-generated variations and a maker-checker pattern: one model helped determine an answer while another LLM acted as validator, with domain experts shaping sports-statistics tests. Codex helped generate evaluation cases and update the system. The source does not describe the content-data ingestion, storage, or underlying serving infrastructure beyond the OpenAI API and JioHotstar interface.

Data flow

Viewers speak or type discovery requests in JioHotstar; the conversational assistant built using the OpenAI API returns video, live-sports, or cricket-stat results in a visual conversational experience.

Solution architecture

2 components · 1 layer
  1. Uncategorized
    • OpenAI API Powers the conversational video and cricket-stat discovery assistant built into JioHotstar.
    • Codex Helped the team generate evaluation cases and update the discovery system during development.

Architecture clues

  • A maker-checker pattern paired an answer-generating model with an LLM validator.
  • A seed evaluation dataset was expanded with model-generated variations.
  • Accuracy, latency, and cost were treated as a three-way production tradeoff.
  • Domain experts contributed to sports-statistics evaluation.
  • The team identified production monitoring of model efficacy as an area to invest in earlier.

Evidence from the source

Codex helped the team accelerate work such as generating eval cases and updating the system
More than 60% of our users use voice rather than text
Using the OpenAI API, JioStar built a conversational video and cricket-stat discovery assistant into JioHotstar.
We worked on bringing entertainment, sports moments and detailed cricket statistics into one experience, across multiple languages, in a very short period.
one model helped determine how to answer a question, while another acted as a validator—an LLM as judge
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

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
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability19/25
    9 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference 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. OpenAI

    JioStar’s chief architect on AI discovery at 500M-user scale

    First-party
    https://openai.com/index/jiostar-vijay-seshadri/
    Source type
    Vendor-published customer story
    Published
    Nov 11, 2026
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Business outcome
    • Metrics
    • Architecture

Date evidence

  • Published on source page Nov 11, 2026 · OpenAI · First-party
    Open date source