Linear replaced Elasticsearch & pgvector to cut down ops and unify their search infrastructure. Cost wasn't the focus, but 70% savings has Linear thinking about indexing far more data.
70%
cost reduction
250M+
documents
13ms
p50 latency
1.5M+
namespaces
Their responsiveness and shipping velocity make us feel like we are their only customer.
Tom Moor, Head of Engineering
Linear was drawn to turbopuffer for its ability to ingest 100s of millions of full-text search documents & vectors without having to think about machine types. Instead, Linear can focus on shipping features.
Linear does hybrid search (FTS + vector) on multiple (org_id, table)
namespaces, rank fuse, and re-rank:
┌─turbopuffer queries──┐
│ ┌───────────────┐ │░
┌┼─▶│ Issues Vector │──┐│░
││ ├───────────────┤ ││░
├┼─▶│ Issues FTS │──┤│░
││ ├───────────────┤ ││░
┌────────┐ ┌----------┐ ├┼─▶│Document Vector│──┤│░ ┌------┐ ┌--------┐
│ Linear │ | Cohere | ││ ├───────────────┤ ││░ | Rank | | Cohere |
│ Query │─▶| Embedding|─┼┼─▶│ Document FTS │──┼┼─▶ | Fuse |──▶| Rerank |
└────────┘ | Model | ││ ├───────────────┤ ││░ └------┘ └--------┘
└----------┘ ├┼─▶│Project Vector │──┤│░
││ ├───────────────┤ ││░
└┼─▶│ Project FTS │──┘│░
│ └───────────────┘ │░
└──────────────────────┘░
░░░░░░░░░░░░░░░░░░░░░░░░
Customer data security is critical to Linear. The ability to use customer managed encryption keys (CMEK) on a per namespace basis stood out.
When a user submits a search, Linear will issue parallel queries across multiple namespaces (documents, issues, projects, comments, attachments, issues, and initiatives) using vector + FTS to return a list of results that then get passed into a reranker:
Linear also leverages turbopuffer for:
Linear plans to leverage turbopuffer to power all of their AI features.
Linear
"Linear is a purpose-built tool for planning and building products"