Does Hyvä work with Algolia, Elasticsearch or a third-party search provider?
Yes. The Hyvä Theme for Magento 2 works with native OpenSearch and with Elasticsearch on Magento 2.4.7 and earlier. Hyvä also works with Algolia, Klevu, ElasticSuite and Doofinder. Native search and Klevu need no extra module, while Algolia, ElasticSuite and Doofinder need a Hyvä compatibility module. Those providers built their storefront code for Luma, Magento’s older default theme.
Quick answer
The Hyvä Theme for Magento 2 runs native OpenSearch search with no extra module. Elasticsearch works on Magento 2.4.7 and earlier, since 2.4.8 dropped support for it. Klevu supports Hyvä natively. Algolia needs a compatibility module such as Blackbird_HyvaAlgoliaSearch, and ElasticSuite uses Hyvä’s official compatibility module. Doofinder relies on a commercial add-on from ExtendWare.
How Hyvä search compatibility depends on your search provider
Search has two halves. The backend indexes products and answers queries. The frontend draws the search box, the autocomplete dropdown, the results page and the filters.
Hyvä only replaces the frontend. It swaps Luma’s RequireJS, jQuery and Knockout.js stack for Alpine.js and Tailwind CSS. So the real question is whether your search provider ships Luma frontend code. Hyvä’s own guidance explains that modules built on Luma need a compatibility module, which usually re-implements their templates.
| Search setup | Works on Hyvä? | What you need |
|---|---|---|
| OpenSearch (native) | Yes, out of the box | Nothing extra |
| Elasticsearch (native) | Yes, on Magento 2.4.7 and earlier | A move to OpenSearch for 2.4.8+ |
| ElasticSuite | Yes, with a module | Hyvä’s official ElasticSuite compatibility module |
| Algolia | Yes, with a module | Blackbird_HyvaAlgoliaSearch or custom work |
| Klevu | Yes, out of the box | Nothing extra |
| Doofinder | Yes, with a module | ExtendWare’s Doofinder for Hyvä |
Does Hyvä work with OpenSearch and Elasticsearch?
Native OpenSearch and Elasticsearch need no extra work on Hyvä, because both run entirely on the server. Hyvä ships its own templates for the search form, results page and layered navigation. The bigger factor is your Magento version.
Per Adobe’s upgrade prerequisites, Magento 2.4.8 and later no longer support Elasticsearch. New Hyvä builds should use OpenSearch.
Does Hyvä work with Algolia?
Algolia’s official Magento extension targets Luma, and an undated Algolia support article says running it on Hyvä requires customization.
The usual route is Blackbird_HyvaAlgoliaSearch, a community compatibility module with over 12,000 installs on Packagist. It covers Algolia Search, InstantSearch, Autocomplete, Recommend and Insights. Its README lists some gaps that are still open:
- Hyvä’s native option selection on product tiles isn’t integrated yet.
- Filter styling on listing pages is basic and usually needs theme work.
- As of its latest Packagist update (February 2026), the module pins the Algolia extension to the 3.17.x line.
The module needs a Hyvä Composer key. Those keys have been free since Hyvä went open source in November 2025.
ElasticSuite, Klevu, Doofinder and other third-party providers
- ElasticSuite: Hyvä maintains an official compatibility module,
hyva-themes/magento2-smile-elasticsuite, through its partnership with ElasticSuite.io. Check its ElasticSuite version constraint before upgrading either package. - Klevu: supported out of the box. Hyvä’s module tracker notes that the old
hyva-themes/magento2-klevu-searchmodule is no longer needed. - Doofinder:ExtendWare sells a compatibility module that sits on top of the official Doofinder extension. Its December 2023 launch notes cite testing up to Hyvä 1.3, so confirm support for your Hyvä version.
- Any other provider: check the Hyvä compatibility module tracker. “Compatible” means the provider needs no module. “Published” means a module exists, though it may cover only part of the features.
What to check before you switch search on Hyvä
- Confirm the Hyvä compatibility module for your search provider supports your Hyvä version and search extension version before upgrading either.
- On staging, test autocomplete, filters, sorting, pagination and add to cart from the results page. These depend most on the compatibility module’s templates.
- Make sure no Luma JavaScript loads on search pages. It brings back the RequireJS and jQuery load that Hyvä exists to remove.
- Recheck Core Web Vitals after go-live. Client-side search such as InstantSearch adds JavaScript that native search doesn’t load.
Which search provider should a Hyvä store use?
Stay on native OpenSearch when its relevance is good enough for your catalog, since it’s the lowest-maintenance Hyvä search setup. For heavier merchandising or synonym management, Klevu is the simplest switch, since it needs no compatibility module. Algolia adds hosted search features such as InstantSearch and Recommend. Budget for compatibility module upkeep each time you upgrade Algolia or Hyvä.
If you’re changing search and theme together, our Hyvä theme development team can scope both in one project.
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Planning search on a Hyvä store?
We’ll check your Algolia, Klevu or OpenSearch setup against your Hyvä version and scope what it takes to get it working.