TRACKING · Tracking record

Perplexity Lily · Records and changes

The Lily inference-server subproject within pplx-garden, tracked by supported checkpoints, hardware, and measurement conditions.

00
UNDERSTANDING · What we know

Uses, conditions and important changes.

Each record has its own date and scope; these do not establish the live state of the whole product.

Perplexity Lily · Recorded by the site · 3 Sept 2026

Perplexity open-sources Lily, a Metal inference server for exactly one checkpoint

Perplexity open-sourced Lily (Apache-2.0) in the pplx-garden repo: a Rust+Metal Mac inference server whose load-time validation admits exactly one checkpoint — mlx-community/Qwen3.6-35B-A3B-4bit with the HF revision pinned; any other architecture or quantization is rejected. It exposes a minimal OpenAI chat-completions subset, decodes greedily, keeps a two-entry LRU prefix cache, and requires Apple GPU family 10+ with macOS 26+. 704 stars at capture. AlphaSignal reports 1.35x over MLX-LM; the README states no such number but ships dated benchmark reports with reproduction steps.

Evidence: Perplexity's official repository README plus AlphaSignal and r/LocalLLaMA aggregation (BitShovel fetched and verified the repo on 2026-09-03). The 1.35x speedup does not appear in the README — it is an aggregator claim awaiting independent reproduction; the support surface is narrow (M5-and-newer Apple silicon, macOS 26+, a single 4-bit checkpoint); stars are attention, not proof of quality; this is not an independent review.

Read the record and sources →

01
THE FULL RECORD · Full timeline

3 events retained by the site.

This object’s records stay together across live coverage, the watch pool and history. Every event links to its source record; corroboration and material changes have separate labels.

Dates use Beijing time. Open an event for its full record, original source and evidence. Corroboration adds support without counting as a material change.

02
COVERAGE · Record status

How these records are currently listed.

Coverage status describes how this site maintains its records, not whether a product is worth using. Existing records remain available after leaving the current list.

Registered follow-up scope

These are registered scopes, not complete product coverage or a receipt for the latest successful check.

03
THE LINEAGE · Lineage

An ongoing record around the same identity.

Source evidence identifies this line. Changing category or moving into history does not create a new identity.

04
RELATIONSHIPS · Evidence-backed connections

Every connection has a source and a scope.

These relationships come from evidence in the records. They describe specific uses or connections, not unconditional interchangeability.

Map 1 evidence-backed connection

Arrows show direction. Open a relationship label for its evidence card or an object for its record. Each connection’s scope is listed below.