I think the new plan makes sense if you're selling to sites with purchase intent, but for searching knowledgebases it seems like it's way too expensive -- the value per search just isn't there. Especially when using instant searching and counting each slightly debounced keystroke as a search.
I couldn't find a way to create synonyms, is this possible?
Is it also possible to control typo sensitivity like algolia? e.g. min chars for 1 typo, min chars for 2 typos.
The curation features looks handy, but I haven't tried it yet.
Install and config was a breeze which is appreciated.
I hope it takes off for you. Nice work.
> Is it also possible to control typo sensitivity
You can control overall number of typose with ?num_typos=1 -- there is no way to define min chars for a specific typo. The engine does make some intelligent decisions to optimize. For example, for a 2 letter query it does not use a num_typos=2 even if that is specified.
Glad to hear about the setup. Will continue to improve.
We now only count search request and we did a simulation on our existing free plan base, offering 10 units cover all of them.
Btw, we keep offering more quota for opensource projects.