Searx VS Typesense

I think searx was largely built by a single person.

https://github.com/searx/searx

I use Recoll to index all of it. Recoll WebUI exposes an API, which I plugged into Searx.

The quality of Google search results has been awful for many years now, but if you still want to use it, the only usable way is via a frontend like Searx[1]. Using any of Google's frontends for any of their services is an exercise in frustration from dodging ads and fighting their hostile UI.

[1]: https://github.com/searx/searx

RSS-Bridge has a Google search adapter. You can also fake it with Searx (which offers RSS feeds of search results).

I've recently wondered how effective local models were at chaining together thoughts as proposed in https://ofir.io/self-ask.pdf. Turns out they are indeed capable of doing so while also creating reasonable chains of thoughts that are easily as good as OpenAI's models. To make it completely free to run I used SearX running inside a Docker container with a second model curating the search results for the main model to get answers from the web.

There are actually plenty of non-ES products that are way easier to integrate and tune (and get better results with less effort).

- Typesense (https://github.com/typesense/typesense)

- Algolia

- Google Programmable Search Engine (https://programmablesearchengine.google.com/about/)

Typesense - Open Source Alternative to Algolia

If you like your penny take a look at Typesense https://typesense.org/ - nothing to complain here. Especially nothing complain about pricing.

I work on Typesense [1] (historically considered an open source alternative to Algolia).

We then launched vector search in Jan 2023, and just last week we launched the ability to generate embeddings from within Typesense.

You'd just need to send JSON data, and Typesense can generate embeddings for your data using OpenAI, PaLM API, or built-in models like S-BERT, E-5, etc (running on a GPU if you prefer) [2]

You can then do a hybrid (keyword + semantic) search by just sending the search keywords to Typesense, and Typesense will automatically generate embeddings for you internally and return a ranked list of keyword results weaved with semantic results (using Rank Fusion).

You can also combine filtering, faceting, typo tolerance, etc - the things Typesense already had.

[1] https://github.com/typesense/typesense

[2] https://typesense.org/docs/0.25.0/api/vector-search.html

For something small with a minimal footprint, I'd recommend Typesense. https://github.com/typesense/typesense

I haven’t used Publish, but I’d assume you could use something like https://typesense.org/ to index and search the vault.

A cheaper option would be to use https://typesense.org. You can use DynamoDb streams to automatically load records. It has worked well for me.

Try tigris | typesense for faster search

I’m also checking out Typesense as a possibility for replacing Elastic: https://typesense.org/