Typesense
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
0warn against
Dec 25, 2025first mention
Sep 9, 2026latest mention
Why people recommend it
“compared to a Typesense based setup imo”
“I use Typesense and am happy.”
Show 3 more
“I'm using Typesense to power my take on a md kb, highly recommend this option”
“highly recommend using typesense as the base for that, so many great features”
“redesigned search with Typesense to drop zero-result queries from 40% to 5%”
Caveats and dissent
No one in these comments warned against it.
Who recommends it in their own words
Threads where it came up
- Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs 1 mention
- Show HN: Capn-hook for coding agents – don't grep the same mystery twice 1 mention
- Manticore Search 27.1.5: Auth, sharding, conversational and faster vector search 1 mention
- We built a persistent agent memory layer on Elasticsearch with 0.89 recall 1 mention
- Ask HN: What are tools you have made for yourself since the advent of AI 1 mention
- Leaf Makes Markdown Readable Inside the Terminal 1 mention
Data: typesense.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 10
“compared to a Typesense based setup imo”
“I wanted to use Typesense”
“I use Typesense and am happy.”
“I'm using Typesense to power my take on a md kb, highly recommend this option”
“markdown search and wiki backed by Typesense”
“highly recommend using typesense as the base for that, so many great features”
“redesigned search with Typesense to drop zero-result queries from 40% to 5%”
“a self-hosted instance of Typesense”
“It was very easy to start with the reasonably priced managed service”
“Try loading up some disease definitions into Typesense[2]”