You know how the old saying goes…
P.S. you can get these nice shiny stickers at @aiDotEngineer next week, just find @marek_galovic and @jerguslejko at our booth
"Just let the agent access our documents."
Sounds simple, until you try to build it. Here's the entire system hiding behind that sentence - and how you can ship it in a day with one tool 🧵
We built a Postgres-compatible SQL layer for TopK.
Our existing query API is already a DataFrame-style API, so SQL fits naturally:
topk Python -> topk SQL
----------------------------------------------------------
select("name") -> SELECT name
filter(field("age").gt(3)) -> WHERE age > 3
fn.semantic_similarity(...) -> semantic_similarity("...")
fn.vector_distance(...) -> vector_distance(...)
SQL is another interface to the same TopK engine, fronted by Pgwire — the Postgres wire protocol. That means any Postgres client "just works":
```
psql "host=https://t.co/bg6AKMTmyO password=<api-key>"
```
I love how simple it turned out! Feels more native than anything else IMHO.
Most search engines force your team to learn a new query language.
Today, we bring hybrid, multi-vector search to the language your team already knows.
SQL becomes your Search Query Language
🧵
Most search engines force your team to learn a new query language.
Today, we bring hybrid, multi-vector search to the language your team already knows.
SQL becomes your Search Query Language
🧵
Most search engines force your team to learn a new query language.
Today, we bring hybrid, multi-vector search to the language your team already knows.
SQL becomes your Search Query Language
🧵
Since there's no official @aidotengineer world's fair SF afterparty, @apify, @joinmassive, and @topk_io are joining forces to host an unofficial one on Thursday, 2nd July in South Park https://t.co/ibzLbo01Ft
Single-vector retrieval is cheap, but throws away important detail. Multi-vector keeps it at 10-100x storage and compute cost.
Join me, @HamelHusain, and @isaac_flath to learn how we made multi-vec search practical in production with @topk_io.
Sign up👉 https://t.co/qdG6BNUzhm
All vector dbs are gonna die except turbopuffer.
You’ll still get low latency in memory ones that are opensource, but as a business tpuffer will be the only unicorn.
All vector dbs are gonna die except turbopuffer.
You’ll still get low latency in memory ones that are opensource, but as a business tpuffer will be the only unicorn.