← Back to feed

Perplexity launches Photon, a Rust retrieval engine cutting p99 latency to 65 ms

On 30 September 2026 MarkTechPost and technical coverage reported Photon, Perplexity’s new Rust retrieval and ranking engine, already serving production traffic. The company says it cut p99 latency from about 800 ms to 65 ms, and offers a Fast Search API mode at $1 per 1,000 requests.

Perplexity launches Photon, a Rust retrieval engine cutting p99 latency to 65 ms

On 30 September 2026 the conversation about agents and frontier models left room for search infrastructure: Perplexity introduced Photon, a Rust retrieval engine that, per the company and MarkTechPost’s report, already serves live traffic. The headline figure is latency: p99 reportedly fell from about 800 milliseconds to 65.

Photon handles the retrieval and ranking that feed Perplexity’s cited answers. In a product whose promise is to answer with sources, the search queue is not a backend detail: it is the user experience. Cutting p99 by nearly an order of magnitude changes how many agentic tools can be chained before users abandon the flow.

Choosing Rust points to memory control, predictable parallelism and freedom from garbage-collection pauses that often punish p99 in Java or Python services. It is not the first AI firm to move hot paths to Rust, but it is one of the few to publish such a concrete latency jump tied to an internal product name promoted to a brand.

On the API, Fast Search mode is enabled with `search_type: "fast"` and priced at $1 per 1,000 requests, according to coverage. That pushes Perplexity beyond the chatbot toward a search-infrastructure provider for developers building web-grounded agents—a field contested by Brave, Bing APIs and open-source stacks.

Timing matters: while OpenAI, Google and Anthropic discuss distillation, Argon and Sonnet 5.5, Perplexity hardens the layer many agents take for granted. An agent with GPT-6 or Claude is still slow if each search hop takes nearly a second at the worst percentile. Photon is a bet that retrieval speed is a moat.

Nuance remains. The 800→65 ms figures are vendor claims reported by technical media; exact corpus size, measurement hardware and like-for-like comparison with the prior stack are not publicly audited in the cited material. Neural Pulse treats them as a product claim, not a third-party benchmark.

For API customers, the practical question is quality versus speed: does fast mode cut recall or source diversity for latency? If Fast Search skips deep indexes, legal or medical agents may still need the slow path. Pricing docs should come with relevance SLOs, not only milliseconds.

Competitively, a faster Perplexity pressures Google and Bing in the “answer with citations” narrative, and startups selling search-RAG on low latency alone. It also strengthens Perplexity’s valuation story as infrastructure, not merely a wrapper on others’ LLMs—useful with investors after months of model warfare.

Architecturally, teams that self-host retrieval should read Photon as a design signal: hot path in a systems language, ranking close to fetch, and p99 metrics as a product KPI. Copying the idea does not require copying the code; it requires instrumenting true percentiles in staging with realistic traffic.

Risks include silent quality regressions while chasing latency, dependence on a single proprietary engine, and rivals with aggressive caches matching perceived speed without rewriting the core. Also, 65 ms p99 in one datacentre does not guarantee the same queue in remote regions.

The announcement rhymes with September’s agentic wave: Managed Agents, dots, Autopilot, Muse. All assume a queryable outside world. Whoever controls that world’s latency captures part of the agent’s margin even without owning the LLM.

Neural Pulse’s close: Photon is a reminder that the 2026 race is not only parameters and RL. Sometimes the product jump is a Rust engine and a p99 that stops hurting. If fast mode keeps reliable citations, Perplexity will have turned invisible infrastructure into a visible sales argument.