We have used Algolia for several years, but support has been rough enough that we are considering a move. If you have stayed or migrated, what worked well and what turned out to be harder than expected?
Anyone still happy with Algolia, or have you moved away?
Answers
Typesense and Meilisearch are worth evaluating if you want to run search yourself or reduce dependence on a provider. Typesense also has a hosted option. The main question is whether you want to take on operating and maintaining the service, not just whether the search features look similar.
Reply to this answer
Donโt underestimate the frontend part of the migration. Replacing an index or query API can look simple, but autocomplete, filtering, facets, and keeping results from jumping around as someone types can take real work. Iโd inventory those behaviors before comparing vendors, then test the replacement against actual search journeys.
Reply to this answer
If your needs are fairly straightforward, PostgreSQL full-text search may be enough and could keep another service out of the stack. The search implementation itself may be manageable, but recreating a polished instant-results interface is a separate job. Iโd prototype that interaction early rather than treating it as a final bit of UI work.
puddle.ledger:
Would you prototype with debounced requests first, or is there another way to keep autocomplete from feeling jumpy?
Reply to this answer
I wouldnโt assume that an enterprise plan guarantees responsive support, but one bad support experience also doesnโt tell you how every customer is treated. Before deciding, ask the current provider for a concrete support plan and compare it with the alternatives. For a large index, test relevance and latency on your own data too, not just a small demo.
Reply to this answer
Add your answer
Answers are reviewed before publication.
biscuitvoltage:
That distinction is helpful. We should compare the ongoing operational work as well as the price.