Perplexity Launches Fast Search: Rust-Based Photon Engine Delivers Results in 230ms

Perplexity's Fast Search delivers sub-230ms retrieval via its Rust-based Photon engine, co-built with hundreds of AI Agents.
Perplexity has added Fast Search to its Search API, returning 95% of results within 230ms thanks to Photon, an in-house retrieval and ranking service built in Rust. The GC-free design and fine-grained memory control make high-concurrency, low-latency retrieval viable for RAG pipelines and multi-step AI Agent workflows. The launch also carries an industry signal: Photon was built by a small engineering team working alongside "hundreds of AI Agents," suggesting AI-assisted development can now handle correctness-critical, high-performance infrastructure projects.
Perplexity Adds Fast Search to Its Search API
Perplexity has announced Fast Search, a new capability for its Search API with one core promise: speed. According to official figures, Fast Search returns 95% of search results in 230 milliseconds or less — a latency level that approaches the threshold of instant human perception, and one that carries significant implications for AI applications that rely on frequent search calls.
For developers, search latency is often a critical bottleneck when building real-time Q&A systems, retrieval-augmented generation (RAG) pipelines, and Agent workflows. When an AI Agent needs to call external retrieval multiple times within a reasoning chain, response times compound with each request. Fast Search compresses this step to the millisecond range, directly shaping the overall responsiveness of applications built on top of it.
The Engine Behind It: Photon, a Retrieval and Ranking Service Built in Rust
Fast Search draws its performance from Photon, Perplexity's new in-house retrieval and ranking service. Photon is built in Rust — a technical choice that signals the team's dual commitment to performance and memory safety.
Rust is renowned for its near-C/C++ runtime efficiency and garbage-collection-free (GC-free) design, making it particularly well-suited for latency-sensitive infrastructure. In high-concurrency, low-latency services like retrieval and ranking, avoiding GC pauses and maintaining fine-grained control over memory layout are often the keys to keeping response times consistently under a few hundred milliseconds. Perplexity's decision to rewrite its core retrieval pipeline in Rust reflects a deliberate pursuit of both peak speed and system stability.
From "Search Company" to "Search Infrastructure Provider"
What's notable here is that Perplexity is no longer positioning search purely as a consumer-facing product. By opening its underlying retrieval capabilities to external developers through the Search API, Photon represents a deliberate move to transform internally developed retrieval engineering into broadly accessible infrastructure. This aligns closely with a broader industry trend: AI Agents need high-quality, low-latency access to external knowledge.
Retrieval and ranking services handle two core stages in a search engine: recall (rapidly filtering a candidate set from a massive document corpus) and ranking (re-scoring and ordering candidates by relevance). Traditional implementations rely on inverted indexes and machine learning models, placing heavy demands on memory bandwidth and compute throughput. Rust's advantage here goes beyond raw speed — its ownership model allows developers to eliminate data races at compile time, making memory access patterns more predictable under high concurrency. This directly impacts tail latency, which is precisely the metric that determines whether an SLA like "95% of requests returned within 230ms" can actually be met.
The "Hundreds of Agents" Signal
There's one detail in the official description worth lingering on: Photon was built by "a small team of engineers and hundreds of agents."
This statement is itself an industry signal. It implies that Perplexity made extensive use of AI coding Agents during the development of this core infrastructure — to assist with coding, testing, or optimization. A small number of human engineers handled architectural decisions and overall direction, while a large volume of AI Agents took on implementation and iteration work. This model — human-AI collaboration, with Agents as a scalable form of engineering capacity — is moving from concept into real production practice.
If accurate, this validates that AI-assisted software engineering can handle complex, correctness-critical projects like high-performance infrastructure, not just prototypes or simple scripts. That has meaningful implications for how the broader software industry thinks about development workflows.
"AI coding Agents" in this context typically refers to automated systems capable of autonomously reading and writing code, running tests, and iterating based on feedback — representative tools include Cursor, GitHub Copilot Workspace, and Devin. Unlike traditional code completion, the Agent paradigm emphasizes multi-step autonomous execution: Agents understand a task goal, break it into subtasks, invoke tools (such as compilers, testing frameworks, and code search), and self-correct on failure. Deploying such Agents at scale on a high-performance infrastructure project implies these tools can already handle non-trivial engineering challenges — such as writing async concurrent Rust code or tuning memory allocation strategies — not just generating boilerplate. If this narrative is backed by further detail, it will stand as an important marker of AI-assisted engineering maturity.
What This Means for Developers
Taken together, Fast Search and Photon offer several concrete benefits for AI application builders:
- Improved real-time responsiveness: 230ms latency allows search to be embedded in conversation flows and Agent reasoning chains with virtually no perceptible delay.
- Scalable API access: Developers gain industrial-grade retrieval capabilities without building and maintaining their own search infrastructure.
- RAG and Agent-friendly: Low-latency retrieval is a prerequisite for high-quality RAG pipelines and multi-step Agent workflows.
It's worth noting that the information currently available from Perplexity is largely limited to performance metrics and technology stack. Specifics around Photon's architecture, index scale, pricing, and comparative benchmarks against competing products have not yet been detailed. Developers will still need to evaluate result quality, cost, and reliability against their own use cases before integrating.
Retrieval-augmented generation (RAG) is one of the dominant deployment paradigms for large language models: before generating a response, relevant passages are retrieved from an external knowledge base and injected into the prompt as context, compensating for the model's knowledge cutoff and reducing hallucination risk. RAG is highly sensitive to retrieval latency — when retrieval takes longer than 500ms, noticeable wait times accumulate across multi-turn conversations or multi-step Agent reasoning. Each additional retrieval call adds to the delay linearly. Fast Search's sub-230ms responses mean that executing 3–5 serial retrieval calls within a single user request can still keep total latency under one second — a meaningful improvement to the user experience of complex Agent workflows.
Summary
Perplexity's Fast Search pushes Search API response times into the millisecond range, with the Rust-based Photon engine reflecting a serious investment in performance infrastructure. The narrative of a small team building alongside "hundreds of Agents" offers a case study worth watching as AI takes on a larger role in complex system construction. For teams building AI Agent and RAG applications, high-speed retrieval APIs like this are likely to become a standard component in the stack.
Related articles

Free Unlimited Claude Code Solution: Agnes AI + CC Switch Setup Guide
No paid subscription needed — pair the free AI platform Agnes AI with the open-source tool CC Switch to provide a backend for Claude Code, enabling unlimited free calls to text, image, and video models. This guide covers the full setup, test results, and usage boundaries.

A Complete Zero-Cost Guide to Getting Started with Claude Code for Beginners in China
A beginner's guide to Claude Code for users in China: two installation methods (command line and IDE plugin), full configuration steps for replacing the official API with the free domestic LongCat model, and a hands-on demo of building a small tool with natural language, plus tips.

When the NSA Gets Involved: The AI Supply Chain Crisis Behind Open-Source CVEs and API Key Hijacking
Multiple open-source projects disclosed severe CVEs in one day, PHP flaws alarmed the FBI, and Railway and OpenCode were breached with API keys stolen. This article breaks down the vulnerability window, AI-accelerated exploitation, and the AI supply chain crisis behind the API key black market, with a developer defense checklist.