OpenData Vector: MIT-Licensed Vector Search on Object Storage
apurvamehta
35 points
4 comments
May 14, 2026
Related Discussions
Found 5 related stories in 76.2ms across 8,303 title embeddings via pgvector HNSW
- You Don't Need a Vector Database kencho · 20 pts · March 08, 2026 · 61% similar
- OpenData Timeseries: Prometheus-compatible metrics on object storage apurvamehta · 13 pts · April 16, 2026 · 54% similar
- OpenCode – Open source AI coding agent rbanffy · 607 pts · March 20, 2026 · 49% similar
- Show HN: XTrace – Encrypted vector DB (search embeddings without exposing them) TristanX · 13 pts · April 22, 2026 · 49% similar
- OpenData Buffer: HA pipelines without Kafka apurvamehta · 12 pts · April 30, 2026 · 49% similar
Discussion Highlights (2 comments)
oliverio
Very interesting, thanks for sharing. This has a lot of nods to Turbopuffer's architecture [0]. My impression is they've spent a lot of time optimizing at the hardware/firmware layer to achieve extremely fast query results. Inarticulately - how ~close is OpenData Vector to Turbopuffer in terms of performance today and where are the major gaps + mountains to scale? Really excited to keep an eye on the repos, great read! [0] https://turbopuffer.com/blog/turbopuffer
Reubend
Stupid question: I was under the impression that object storage was super expensive compared to "normal" SSDs if the QPS numbers got high. Is that not the case for DBs based on object storage because they cache data before sending it to the object storage? Or because they do some other processing on the DB server before it hits storage?