← All writing
4 min read

Magento 2 with Hyvä: is it worth it?

magentohyva

This post was written in December 2025. Hyvä and its ecosystem move fast, so some of the details below (especially pricing and module support) may change. Last updated: December 21, 2025.

A few years ago I wrote about Magento PWA Studio and concluded that it wasn't ready for complex stores. Since then, Hyvä has become the frontend most Magento agencies actually reach for, and I've now done some work with it. So here are my honest thoughts.

What Hyvä actually is

Hyvä is a replacement for the default Luma frontend. It throws away RequireJS, Knockout, jQuery and LESS and replaces them with Alpine.js and Tailwind CSS. It is still a regular Magento theme with server-rendered .phtml templates, layout XML and view models. It is not headless.

That last point is why it succeeded where PWA Studio struggled. You don't need GraphQL coverage for every module, you don't run a separate Node app, and the backend, admin and most of your existing PHP knowledge stay the same.

The good parts

The performance gain is real and comes without much effort. A stock Hyvä store ships a fraction of the JavaScript Luma does, and getting good Core Web Vitals scores stops being a constant fight.

Developer experience is the other big win. Templates are readable, there's no RequireJS mixin maze, and frontend changes that used to take hours in Luma take minutes. Developers who know Tailwind and a bit of Alpine become productive very quickly.

The biggest caveat: 3rd-party modules

Any module that adds frontend functionality was most likely built for Luma, and its JavaScript and templates won't work on Hyvä as-is. You need a compatibility module for it, and you have three ways to get one:

  • The vendor ships Hyvä support. Most of the big extension vendors do now, and this is the best case.
  • A compatibility module exists on the Hyvä module tracker. It's community-maintained, so double-check the status with the vendor.
  • You write it yourself. This means porting the module's frontend to Alpine and Tailwind, then maintaining that port every time the vendor updates the module.

The third option is where budgets go wrong. A store with a handful of frontend-heavy modules that have no Hyvä support can easily spend more on compatibility work than on the theme itself.

There is also the Luma theme fallback, which lets specific routes keep rendering with a Luma theme. It's a useful escape hatch, but those pages load the whole Luma stack again and need to be styled twice.

Checkout options

Checkout is where module compatibility matters most, because it's where your payment and shipping methods live. You basically have three options:

  1. Hyvä Checkout: built on Magewire, fast and pleasant to customize. Your payment and shipping modules need Hyvä Checkout support, though, so check every one of them before committing.
  2. Luma checkout through the fallback: everything that worked before keeps working, but you lose the performance benefit on the most important page and maintain two sets of styles.
  3. A 3rd-party checkout that supports Hyvä: worth considering if you already use one.

If your payment provider doesn't support Hyvä Checkout yet, the fallback is a perfectly fine starting point. You can move over later.

Cost & licensing

This used to be the main objection, and it's mostly gone now. Since November 2025 the Hyvä theme is free and open source (OSL 3.0 / AFL 3.0). What's still paid: Hyvä Checkout (€1,000 one-time, then €250 a year), Hyvä UI (€250), and the Enterprise and Commerce offerings.

The license was never the real cost, though. The real cost is the build. Moving an existing Luma store to Hyvä is a rebuild of the frontend, not a reskin, plus whatever compatibility work your modules need. Your team (or agency) also needs to be comfortable with Tailwind, Alpine and, for checkout, Magewire.

So, is it worth it?

It depends, mostly on your module list.

It's worth it if:

  • you're starting a new Magento 2 store, or your current theme needs a redesign anyway
  • most of your frontend modules already support Hyvä
  • performance and conversion actually matter to your business (they usually do)

Think twice if:

  • you rely on a lot of frontend-heavy or niche modules without Hyvä support
  • your checkout is heavily customized, or your payment provider has no Hyvä Checkout integration
  • there's no budget for ongoing compatibility maintenance after launch

In my opinion, Hyvä is the most practical Magento frontend available right now and the default I'd pick for a new build. For a mature, heavily customized store, audit every module first. That audit tells you whether Hyvä is a quick win or a long project.