AWS Software / SaaS United States

Phind

Enterprise Knowledge Search

While they were still in college, Michael Royzen and Justin Wei saw the potential for using large language models (LLMs) together with high-quality context to build an intelligent search engine for developers.

10 days
15 minutes
15 seconds
5-10% growth in daily users each week

Reported impact

Business outcome

Phind is continuing to make its models faster and will continue using NVIDIA-powered Amazon EC2 P4d and Amazon EC2 P5 instances to achieve its goal. Using NVIDIA’s new TensorRT library, Phind expects to make its models five times faster than previously. While the company is still determining the best split of LLM training and inference across Amazon EC2 instances, it is very pleased with the overall performance.

  • Productivity Improvement

Solution

While they were still in college, Michael Royzen and Justin Wei saw the potential for using large language models (LLMs) together with high-quality context to build an intelligent search engine for developers. When a developer uses Phind, they can type in a complex coding question to the search bar and receive an answer generated by AI along with links on the side to online sources. Phind can answer coding and development-related questions with much more precision than a generic search engine because it is trained in this context. The company trained its LLMs using NVIDIA A100 Tensor Core GPU-powered Amazon EC2 P4d Instances —which deliver high performance for machine learning training and high performance computing applications in the cloud—and NVIDIA H100 Tensor Core GPU-powered Amazon EC2 P5 Instances , the highest performance GPU-based instances for deep learning and high performance computing applications.

Solution architecture

2 components · 1 layer
  1. Compute
    • Amazon EC2 P5 Instances Provide high-performance GPU compute for large model training and inference.
    • Amazon EC2 P4d Instances Provide GPU infrastructure for large-scale model training and inference.

Architecture clues

  • The company trained its LLMs using NVIDIA A100 Tensor Core GPU-powered Amazon EC2 P4d Instances —which deliver high performance for machine learning training and high performance c
  • This led Royzen and Wei to build Phind , a generative artificial intelligence (AI)–based search engine where programmers and developers can get answers to their questions in 15 sec
  • To orchestrate its LLM training, Phind runs Amazon EC2 P4d and Amazon EC2 P5 Instances on connected nodes using AWS ParallelCluster, an open-source cluster management tool used to
  • Using NVIDIA’s TensorRT-LLM, a software development kit for high performance deep learning inference, on Amazon EC2 P5 Instances, Phind has increased its tokens per second speed by
  • “We love using AWS ParallelCluster because it works quickly and reliably, and that’s all we can ask for,” says Royzen.

Evidence from the source

LLMs were becoming more accurate, but many still acted as summarizers.
Phind can answer coding and development-related questions with much more precision than a generic search engine because it is trained in this context.
Software engineering requires a lot of specific knowledge, and traditional search engines often produce responses to technical questions that are too broad or shallow to help developers solve problems quickly.
When a developer uses Phind, they can type in a complex coding question to the search bar and receive an answer generated by AI along with links on the side to online sources.
When the cofounders of Phind were seniors at the University of Texas at Austin, they saw an opportunity to use LLMs as a search engine by feeding them high-quality context.
While they were still in college, Michael Royzen and Justin Wei saw the potential for using large language models (LLMs) together with high-quality context to build an intelligent search engine for developers.
Transparency Evidence & methodology 80/100 reference value · 85% 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 value80/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth15/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
    6 metrics describe measurable impact.
  • Deployment scale0/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence85%
  • 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
    6 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 specificity8/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. AWS

    Phind customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/phind-case-study/
    Source type
    Vendor-published customer story
    Published
    Jan 8, 2024
    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.