HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
neuml
txtai
Python2020–2026
neuml / txtai

txtai

💡 All-in-one AI framework for semantic search, LLM orchestration and language model workflows

15Distinct people
119Mentions
0Explicit recommenders
13.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

💡 All-in-one AI framework for semantic search, LLM orchestration and language model workflows

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57: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 year119 dated mentions

Observed mentions: 2020-11-26 16:07:30 UTC to 2026-08-12 17:20:42 UTC.

01020302020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 8 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 32 mentions; 16 submissions, 16 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 35 mentions; 1 submissions, 34 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 35 mentions; 0 submissions, 35 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC211
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC880
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC321616
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC35134
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC35035
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

What Hacker News says

35 sources
This is a small model that will easily run on most modern machines. There are many ways to run this either using Hugging Face Transformers directly or a library built on Transformers that makes it easier. For example, you can run LLM inference with txtai (https://github.com/neuml/txtai) in Python using the following 3 lines of code. from txtai.pipeline import LLM llm = LLM("TinyLlama/TinyLlama-1.1B-Chat-v1.0") llm("""<|im_start|>user What is the speed of light?<|im_end|> <|im_start|>assistant""") I expect they'll be GGUF and AWQ versions of this model soon that will make inference possible on even smaller devices.
In TinyLlama a 1.1B Llama model trained on 3T tokens reaches 1.0 release
My perspective as an open source developer of txtai (https://github.com/neuml/txtai). When you get started in open source, it's a great way for a small team to get the word out. Conversely, when starting as proprietary software or SaaS, you're looking at advertising, websites, sales calls and so forth. If an open source company is lucky enough to be successful, the next phase is having users and perhaps even funding. When the team grows and/or others put their own money or career into the company, they want an outcome. It becomes hard to ignore that there are thousands of people using the software and inevitably it becomes an exercise on how to claw back from the group of "free" users. There is also the fear that a big company will undercut the open source company by offering the software as part of a cloud service. This is my opinion on
Read the rest
how we got here with confusing licensing changes. Most don't have the means to accept little to no income from their work. But there shouldn't be a "fixed pot" mentality. In order to be a successful open source company, one has to see the "free" users as beneficial. Think of it as a big wide open world and that while some will never pay, if you add value in other ways on top of your open source offerings, there will be significant income opportunities. Could be consulting projects, hosted/cloud/SaaS versions or specialized components. One should also look at operations. There will be a new wave of companies, especially in the AI space, that are lean and using automation to build great things with a very limited amount of resources. Perhaps they don't even need funding and can build a profitable company without it. In those cases, they won't have those internal pressures and hence likely to be more competitive. Something to watch in 2024.
In The life and death of open source companies
I agree that RAG doesn't have to be paired with vector search. Other types of search can work in some cases. Where vector search excels is that it can encode a complex question as a vector and does a good job bringing back the top n results. Its not impossible to do some of this with keyword search (term expansion, stopwords and so forth). Vector search just makes it easy. In the end, yes this is a better search system. And thinking about this step is a good point. I would go a step further and say it's also worth thinking about the RAG framework. Lots of examples use a OpenAI/Langchain/Chroma stack. But it's also worth evaluating RAG framework options. There might be frameworks that are easier to integrate and perform better for your use case. Disclaimer: I am the author of txtai: https://github.com/neuml/txtai
In Build a search engine, not a vector DB
Nice project! I've spent quite a lot of time in the medical/scientific literature space. With regards to LLMs, specifically RAG, how the data is chunked is quite important. With that, I have a couple projects that might be beneficial additions. paperetl (https://github.com/neuml/paperetl) - supports parsing arXiv, PubMed and integrates with GROBID to handle parsing metadata and text from arbitrary papers. paperai (https://github.com/neuml/paperai) - builds embeddings databases of medical/scientific papers. Supports LLM prompting, semantic workflows and vector search. Built with txtai (https://github.com/neuml/txtai). While arbitrary chunking/splitting can work, I've found that integrating parsing that has knowledge of medical/scientific paper structure increases the overall accuracy and experience of downstream applications.
In Oracle of Zotero: LLM QA of Your Research Library
I've seen a number of projects come over the last couple years. I'm the author of txtai (https://github.com/neuml/txtai) which I started in 2020. How you approach performance is the key point. You can write performant code in any language. For example, for standard keyword search, I wrote a component to make sparse/keyword search just as efficient as Apache Lucene in Python. https://neuml.hashnode.dev/building-an-efficient-sparse-keyw....
In VectorDB: Vector Database Built by Kagi Search
I'll add txtai to the list: https://github.com/neuml/txtai txtai is an all-in-one embeddings database for semantic search, LLM orchestration and language model workflows. Embeddings databases are a union of vector indexes (sparse and dense), graph networks and relational databases. This enables vector search with SQL, topic modeling and retrieval augmented generation. txtai adopts a local-first approach. A production-ready instance can be run locally within a single Python instance. It can also scale out when needed. txtai can use Faiss, Hnswlib or Annoy as it's vector index backend. This is relevant in terms of the ANN-Benchmarks scores. Disclaimer: I am the author of txtai
In Choosing vector database: a side-by-side comparison

Showing the 15 most recent of 35 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.