HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
asg017
sqlite-vec
C2024–2026
asg017 / sqlite-vec

sqlite-vec

A vector search SQLite extension that runs anywhere!

17Distinct people
22Mentions
0Explicit recommenders
8.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A vector search SQLite extension that runs anywhere!

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month22 dated mentions

Observed mentions: 2024-05-03 04:15:56 UTC to 2026-10-16 10:37:30 UTC.

012342024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsMay 20242024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 20252025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC303
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC110
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC110
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC422
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC101
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC000
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC000
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC101
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC101
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC101
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC321
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC101
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC303
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC101
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC000
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC000
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC101

What Hacker News says

22 sources

Show HN: Digger Solo – Semantic Search and Maps for Local Files

Hey, I am Sean and I built Digger Solo - a privacy respecting file explorer from the "future". The core features are semantic file search and interactive data maps allowing to explore your files with ease. All processing happens locally - your files never leave your machine. The file search works by combining full text search with semantic search allowing to search for content of text and image files by their meaning / content (even if the image has no descriptive file name). You can start a search query using a tag e.g. "#jpg cat" to search all your jpg files for cats. Files are clustered by content similarity in interactive maps that reveal hidden connections and patterns across your collection (text, image, video & audio files supported). Tags are inferred from imported file paths and file types. Technicalities: Digger Solo is quite a
Read the rest
complex beast: I am using PyTauri (https://github.com/pytauri/pytauri - Python bindings for Tauri). Python is used to import files, run the dimensionality reduction algorithms (t-SNE, UMAP etc.) and for most database logic (using SQLite3). The CLIP model (JINA CLIP v1) runs as ONNX model using the Rust crate ORT (https://ort.pyke.io/) - inference supports right now only CPU. The semantic search is powered by the SQLite3 extension https://github.com/asg017/sqlite-vec which just adds support for optimized brute-force based nearest neighbor vector search (no approximate vector index). So Digger Solo is not meant for millions of files, more like a few 100 thousands. Happy to answer questions!
2 points · Open discussion

Show HN: Digger Solo – Semantic File Search and Maps

I built Digger Solo a privacy respecting file explorer from the future. The core features are semantic file search and interactive data maps allowing to explore your files with ease. All processing happens locally - your files never leave your machine. The file search works by combining full text search with semantic search allowing to search for content of text and image files by their meaning / content (even if the image has no descriptive file name). You can start a search query using a tag e.g. "#jpg cat" to search all your jpg files for cats. Files are sorted by content similarity in interactive maps that reveal hidden connections and patterns across your collection (text, image, video & audio files supported). Tags are inferred from imported file paths and file types. Technicalities: Digger Solo is quite a complex beast: I am using
Read the rest
PyTauri (https://github.com/pytauri/pytauri - Python bindings for Tauri with a Rust backend with JS frontend). Python is used to import files, run the dimensionality reduction algorithms (t-SNE, UMAP etc.) and for most database logic (using SQLite3). The CLIP model (JINA CLIP v1) runs as ONNX model using the Rust crate ORT (https://ort.pyke.io/) - inference supports right now only CPU. The semantic search is powered by the SQLite3 extension https://github.com/asg017/sqlite-vec which just adds support for optimized brute-force based nearest neighbor vector search (no approximate vector index). So Digger Solo is not meant for millions of files, more like a few 100 thousands. The installer contains all model files used (text, vision and audio encoders) that is why the download size is so big - I did not want to have additional downloads after installation. The Windows version had problems running the Python modules reliably for some customers (working on a fix). So I recommend trying the free version first and see if file importing works before purchasing a key.
1 points · Open discussion
> Won’t he eventually ran out of context window? The "memories" table has a date column which is used to record the data when the information is relevant. The prompt can then be fed just information for today and the next few days - which will always be tiny. It's possible to save "memories" that are always included in the prompt, but even those will add up to not a lot of tokens over time. > Won’t this be expensive when using hosted solutions? You may be under-estimating how absurdly cheap hosted LLMs are these days. Most prompts against most models cost a fraction of a single cent, even for tens of thousands of tokens. Play around with my LLM pricing calculator for an illustration of that: https://tools.simonwillison.net/llm-prices > If one were to build this locally, can Vector DB similarity search or a hybrid combined with fulltext se
Read the rest
arch be used to achieve this? Geoffrey's design is so simple it doesn't even need search - all it does is dump in context that's been stamped with a date, and there are so few tokens there's no need for FTS or vector search. If you wanted to build something more sophisticated you could absolutely use those. SQLite has surprisingly capable FTS built in and there are extensions like https://github.com/asg017/sqlite-vec for doing things with vectors.
In A hackable AI assistant using a single SQLite table and a handful of cron jobs
I'm always cautious with a one-size-fits-all approach. If a team is working on a small project and SQLite works then great. You can use a SQLite database on something like a $4/month DigitalOcean droplet. Can't say the same for Postgres. > AI is a bubble Many say this but Generative AI and LLMs have gotten bunched up with everything else. There is a clear need for vectors and multimodal search. There is no core SQL statement to find concepts within an image for example. Machine learning models support that with arrays of numbers (i.e. vectors). pgvector adds vector storage and similarity search for Postgres. There was a recent post about storing vectors in SQLite (https://github.com/asg017/sqlite-vec). > Even if your business is another AI grift, you probably only need to import openai. There's much more than this. There are frameworks su
Read the rest
ch as LangChain, LlamaIndex and txtai (disclaimer I'm the primary author of https://github.com/neuml/txtai) that handle generating embeddings locally or with APIs and storing them in databases such as Postgres.
In Just use Postgres
otoolep·Aug 15, 2024Submission

Show HN: rqlite and Docker and SQLite-vec – highly-available Vector Search

Hi -- I'm the creator of rqlite[1], a lightweight distributed database built on SQLite. Recently I released support for SQL Extensions[2], making it possible to load extensions into rqlite at launch time. This has opened up a bunch of new possibilities for the database. I have now taken it one step further, and baked a bunch of SQLite extensions into the rqlite Docker images[3]. All of this means that rqlite can be deployed as highly-available Vector Search database in a matter of seconds, thanks to the convenience of Docker and loading sqlite-vec[4] -- but all in a lightweight, easy-to-use manner: Launch an rqlite node with vector search enabled: docker run -e SQLITE_EXTENSIONS='sqlite-vec' -p4001:4001 rqlite/rqlite Set up vector search tables using the rqlite shell: 127.0.0.1:4001> CREATE VIRTUAL TABLE vec_examples USING vec0(sample_emb
Read the rest
edding float[8]) This feels like a promising new product area for rqlite -- super easy to use, network accessible Vector Search, all in a highly available package if you want that. I'm looking for any and all feedback, as this is a very new area for rqlite (SQLite extensions, and new types of search). [1] https://rqlite.io [2] https://www.philipotoole.com/rqlite-8-27-loadable-sqlite-ext... [3] https://www.philipotoole.com/rqlite-828-enhanced-docker-supp... [4] https://github.com/asg017/sqlite-vec
2 points · Open discussion

Showing the 15 most recent of 22 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.