When is Hyvä worth it? An honest decision guide for Magento stores

Hyvä is worth it when your Magento store will stay on Magento for several more years, the Luma frontend is slowing down both customers and developers, and your extensions either have Hyvä compatibility modules or can be replaced. It is usually not worth it yet when the store is on an unsupported Magento version, depends on many Luma-only extensions, is about to be replatformed, or when the slowness comes from the server rather than the frontend. Since November 2025 the Hyvä Theme itself is free and open source, so the decision is about migration effort, not licence cost.

Below is how we walk store owners and agencies through that decision.

What Hyvä actually changes

Hyvä replaces Magento’s storefront theme, not Magento itself. The admin, catalogue, orders, integrations and backend code stay as they are.

Two consequences follow from this table:

• Backend developers stay at home. Layout XML, blocks and view models work the way they always did, so the learning curve sits in the frontend (Tailwind and Alpine.js), not in Magento.
• Every piece of Luma JavaScript has to be rebuilt. Anything that relies on RequireJS, Knockout or UI components on the storefront (your custom theme, extension widgets, checkout steps) needs a Hyvä version.

Licence and products (as of November 2026)

• The Hyvä Theme was relicensed under OSL3 + AFL3 in November 2025. It is installed with a free Packagist key from a hyva.io account.
• Hyvä Checkout, Hyvä Enterprise and Hyvä Commerce remain commercial products with their own licences.
• Hyvä UI (a library of ready-made components) became a separate paid product.

Check hyva.io for current prices before you budget; they are not part of this guide.

Version requirements

Hyvä’s documentation currently requires Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7, 2.4.7-p1 or newer, and PHP 8.1 to 8.4. Development machines need Node.js 20 or newer for the Tailwind build.

Note that Adobe lists PHP 8.5 for Magento 2.4.9. If you plan to combine a 2.4.9 upgrade with a Hyvä migration, confirm that Hyvä and every compatibility module you need officially support PHP 8.5 at that point. The PHP and service versions per release are listed in the upgrade checklist.

What drives the cost and effort

A Hyvä migration is a frontend rebuild with a known structure. Four things decide how big it gets.

1. Your current theme

• Close to Luma with brand colours and a few custom blocks: the most predictable case. Most of the work is restyling with Tailwind.
• Heavily customised theme with many template overrides, custom JavaScript widgets and page-builder content: each custom component is rebuilt in Alpine.js. The number of distinct components usually matters more than the page count.
• Design refresh at the same time: often the right moment, but it adds design and approval time. Keep “migrate” and “redesign” as separate line items so the scope stays visible.

2. Extensions with a storefront

Hyvä’s documentation is direct about this: modules built for Luma or Blank need a compatibility module to work on a Hyvä storefront. Backend-only modules (ERP connectors, feeds, admin tools) are unaffected.

For each extension with frontend output, there are four outcomes:

1. The vendor ships Hyvä support in the module itself. Update and test.
2. A compatibility module exists, listed in Hyvä’s public Compatibility Module Tracker. Install and test.
3. No compatibility module yet. Someone has to write one, which re-implements only the frontend parts of the module.
4. The extension is not worth porting. Replace it with a Hyvä-ready alternative or remove it.

This list is one of the most useful inputs for an estimate. We build it in the audit before quoting a fixed price.

3. The checkout decision

Checkout is where Luma’s JavaScript stack is heaviest, so it needs its own decision. Hyvä’s documentation describes three routes:

• Hyvä Checkout. The checkout built for Hyvä, on Magewire (a server-driven PHP component framework). It is a separate commercial licence. It can also run on Luma stores and can be enabled per store view, so it can be rolled out step by step.
• Keep the Luma checkout through Hyvä’s theme fallback module. The checkout routes keep loading RequireJS, Knockout and jQuery while the rest of the store runs on Hyvä. It needs extra styling work to match the new storefront.
• Keep a third-party Luma-based checkout (several one-step checkout extensions are listed in Hyvä’s docs) through the same fallback.

How to choose:

• Payment and shipping methods with Hyvä Checkout support available → Hyvä Checkout is the cleanest result.
• Heavily customised checkout, or payment providers without Hyvä Checkout support → migrate the storefront first, keep the existing checkout through the fallback, and plan the checkout as a second phase.

4. Integrations that touch the frontend

Tag managers, analytics data layers, consent banners, search and recommendation widgets, reviews and chat scripts all need to be re-wired and re-tested. They rarely block a migration, but they belong in the estimate and the test plan.

The benefits, without the hype

• Lighter frontend. Hyvä drops RequireJS, Knockout and the UI components stack on the storefront. In our experience that is one of the most effective levers for Core Web Vitals on Magento, but measure your own store before and after. Server response time, images and third-party scripts still count.
• Faster frontend development. Tailwind and Alpine.js are smaller and easier to reason about than Luma’s LESS and Knockout layers. Changes that used to take a deep dive into UI components become ordinary template work.
• A shared ecosystem. Extension vendors can ship Hyvä support inside their own modules, and the compatibility modules that support the theme were relicensed as open source alongside it.
• No theme licence fee since November 2025, which removes one argument against it for smaller stores.

What Hyvä does not do: fix slow server responses, a low full-page cache hit rate, unindexed catalogue data or a slow ERP sync. Those are backend problems and stay after the migration.

When Luma or a lighter fix is the better choice

Hyvä is a good default for a store with a future on Magento, but not always the next step. We usually recommend something else when:

• The store is on an unsupported or soon-unsupported version. Upgrade Magento and PHP first. A migration on top of an outdated platform doubles the risk, and the upgrade may change your extension list anyway. Our Magento 2.4.x upgrade checklist walks through that upgrade step by step.
• The slowness is on the server. If time to first byte is high, the full-page cache misses or Varnish is not used, fix that first. It is usually cheaper and helps every page, whatever the theme.
• Third-party scripts dominate. If tag manager containers, chat widgets and marketing pixels take most of the main thread, cleaning them up is a quick win on Luma too.
• Many key extensions have no Hyvä support and no good replacement. The cost of writing compatibility modules may outweigh the gain, at least for now.
• Replatforming or a headless frontend is already planned within a year or two. Spend the budget on that project instead.
• Low traffic and a stable design. If the store converts well and nobody needs to touch the frontend, a Luma performance pass may give enough for much less.

A simple decision checklist

Answer these before you ask for a quote:

1. Will the store stay on Magento / Adobe Commerce for at least three more years?
2. Is it on a supported 2.4.x line and the latest patch?
3. How many extensions have storefront output, and how many have Hyvä support or a compatibility module?
4. Is the checkout standard or heavily customised, and do your payment providers support Hyvä Checkout?
5. Where is the time going today: server response, frontend JavaScript or third-party scripts?
6. Do you want a redesign at the same time, or a like-for-like migration first?

If most answers point to “long future, supported version, manageable extension list, frontend is the bottleneck”, Hyvä is very likely worth it.

Next step

Our free express audit looks at versions, patch level, performance and basic security, and tells you whether the frontend or the server is the real bottleneck. If Hyvä makes sense, the Hyvä migration package starts at €2,000 (fixed price after an audit) and is part of our upgrade services, so it can be combined with a 2.4.x and PHP upgrade. For ongoing care after the launch, see Magento support retainers.

Sources: Hyvä: Hyvä Theme is now open source and free, Hyvä Theme licence, What is Hyvä?, Getting started (requirements), Compatibility modules, Luma theme fallback, Luma checkout with Hyvä, Hyvä Checkout; Adobe: System requirements.