OpenAI Software / SaaS Global

NVIDIA

Application Refactoring · IT Operations Automation

NVIDIA needed AI tooling that could autonomously handle complex engineering sessions and full machine-learning research workflows, not just short coding assists, while respecting privacy and infrastructure constraints.

10x speed improvement for running experiments
Python repositories rewritten into Rust with about 20X more efficiency

Reported impact

Business outcome

NVIDIA accelerated both software delivery and ML experimentation, lowered the threshold for building internal tools, and gave researchers a more autonomous partner for exploring ideas, tracing evidence, and launching end-to-end studies.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

NVIDIA uses Codex with GPT-5.5 as a default tool for complex engineering work and end-to-end machine-learning research. In software delivery, Codex can sustain long sessions with multiple compactions, choose the right tools or skills, and evolve internal systems from MVP to production-ready services with better scalability and reliability than earlier models. Engineers have used it to build and autonomously test a podcast-recording app in hours, including video and audio workflows via the Codex desktop app. In research, the same model acts as a creative partner: teams point it at large corpora of papers, let it trace evidence chains, map knowledge graphs, write experimental scripts, and run workloads remotely through SSH on machine-learning infrastructure. That combination means Codex can move from idea generation to experiment execution and system implementation in one flow, including rewriting legacy Python repositories into far more efficient Rust when performance improvements justify it.

Data flow

Engineering tickets, internal platform code, and research corpora are fed into Codex, which reasons with GPT-5.5 to propose designs, generate code, run tests, and launch remote experiments through SSH. Outputs are then reviewed or executed on NVIDIA’s infrastructure as production systems or ML research runs.

Solution architecture

3 components · 3 layers
  1. Compute
    • GPT-5.5 Provides the long-session accuracy, creativity, and autonomy behind Codex workflows.
  2. Serving
    • Codex desktop app Enables computer interaction and autonomous testing of built applications.
  3. Orchestration
    • Codex Acts as NVIDIA’s autonomous engineering and research agent across software and machine-learning workflows.

Architecture clues

  • Codex runs in production on NVIDIA GB200 and GB300 infrastructure
  • Desktop app can test audio and video functionality autonomously
  • Research workflows include pointing Codex at large corpora of papers and running scripts remotely over SSH
  • Team uses Codex as the default tool for complex engineering work

Evidence from the source

"Codex is our go-to tool for complex engineering tasks"
"It’s been a 10x speed improvement just in terms of running experiments"
"it was built and tested completely autonomously"
"it’s rewriting it into Rust and making it like 20X more efficient"
Transparency Evidence & methodology 96/100 reference value · 87% 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 value96/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 specificity16/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 confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/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

    NVIDIA customer story

    First-party
    https://openai.com/index/nvidia/
    Source type
    Vendor-published customer story
    Published
    May 12, 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

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.