Hyvä Theme review 2026: free, fast and what still costs money

Hyvä Theme is now the default answer to "how do we make a Magento storefront fast?", and since 10 November 2025 it costs nothing. The theme is open source under OSL 3.0 and AFL 3.0, the same licences as Magento Open Source. Hyvä UI, Hyvä Checkout, Hyvä Enterprise and Hyvä Commerce remain paid products. For most stores on 2.4.7 or later, Hyvä is worth adopting. The real cost is not the licence but making your extensions compatible.

This review covers what you get in October 2026, what still costs money, the version history that matters for Magento 2.4.9, and the trade-offs we would weigh before switching from Luma.

What Hyvä actually changes

Magento's default Luma theme is built on RequireJS, KnockoutJS, jQuery and LESS. That stack is flexible but heavy, and it is the main reason Luma storefronts struggle with Core Web Vitals. Hyvä replaces the whole frontend layer with two small tools:

• Tailwind CSS for styling, compiled into a single small stylesheet that contains only the classes your templates use.
• Alpine.js for interactivity, written directly in the .phtml templates.

The backend stays unchanged. Layout XML, blocks, view models and plugins all work as before, so PHP developers keep their Magento knowledge. What changes is everything the browser receives.

What is free and what is paid in 2026

Hyvä founder Willem Wigman announced the move on 6 November 2025, and it took effect on 10 November with the 1.4 release line. Here is how the product range now splits:

Existing licence holders kept their premium support and Hyvä UI access. Free accounts can create up to five Composer keys through the Hyvä Portal.

Requirements and installation

Hyvä's getting-started page lists Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7, 2.4.7-p1 or higher. The 1.4.6 release added compatibility with Magento 2.4.9 and PHP 8.5. Tailwind needs Node.js 20 or later, but only where you build the CSS: Hyvä advises building on development or CI, not on production servers.

Create a free key in your hyva.io account, then install through Hyvä's private Packagist repository:

composer config --auth http-basic.hyva-themes.repo.packagist.com token <your-key>
composer config repositories.private-packagist composer https://hyva-themes.repo.packagist.com/<your-project-name>/
composer require hyva-themes/magento2-default-theme
bin/magento setup:upgrade

Then select hyva/default under Content > Design > Configuration. Hyvä's docs warn that you should also set the theme at the website level, or the storefront may break.

In practice you will create a child theme rather than editing hyva/default, and run the Tailwind build from your theme's web/tailwind directory as part of your deployment pipeline.

Versions that matter for Magento 2.4.9

If you upgraded Magento to 2.4.9 and are not ready for the 1.5 theme changes, Hyvä says it is safe to update only the Hyva_Theme module, which carries the PHP 8.5 fixes:

composer require hyva-themes/magento2-theme-module --update-with-dependencies
bin/magento setup:upgrade

The real cost: extension compatibility

Any module that ships Luma or Blank frontend code needs a compatibility module to work on a Hyvä storefront. A compatibility module reimplements the parts that rely on RequireJS or Knockout templates. Hyvä keeps a Compatibility Module Tracker on its GitLab that lists available modules and their status, and many vendors now ship Hyvä support themselves.

Before you commit, list every module with frontend output and check each one:

bin/magento module:status --enabled | grep -v '^Magento_'
find app/code vendor -path '*view/frontend/requirejs-config.js' | grep -v '/magento/'

Every hit in the second command is a module with Luma JavaScript that needs a Hyvä version, a compatibility module or a rewrite. Payment, search, reviews and product configurators are the usual hard cases.

The checkout question

The free theme does not include a Hyvä-native checkout. You have two options:

• Luma checkout fallback. Hyvä's Theme Fallback module serves configured routes, such as checkout/index, with a traditional Luma theme. RequireJS and the Luma assets load only on those pages. It works with the default checkout and Luma-based one-step checkouts, and Hyvä positions it mainly as a migration tool.
• Hyvä Checkout. The paid, native option. Recent updates added a Payments API backport module for stores that cannot upgrade fully, plus full Tailwind v4 support.

Who should switch now, and who should wait

Switch now if you run Magento Open Source or Adobe Commerce 2.4.7 or later, your Luma storefront fails Core Web Vitals, and most of your extensions already have Hyvä support. A redesign or replatforming budget is the natural moment, because a Hyvä project is effectively a new frontend.

Plan, then switch if you depend on several Luma-only extensions with no compatibility module. Budget the rewrites first; one complex product configurator can cost more than the rest of the theme work.

Wait if you are still on 2.4.6 or older. Upgrade Magento first: the support window for older lines is closing, and Hyvä's current releases target supported versions.

Headless projects with a separate React or Vue frontend are a different decision altogether. Hyvä keeps the storefront inside Magento, which is simpler to run but less flexible than a fully decoupled build.

Verdict: strengths and weaknesses

Strengths

• Performance by design. Far less JavaScript than Luma, which helps Core Web Vitals without a headless rebuild.
• No licence fee for the theme, under the same open-source licences as Magento.
• Familiar for Magento developers. Layout XML and PHP stay the same; only the frontend tools change.
• Active releases. Six default-theme releases between May and July 2026 alone, starting with 2.4.9 support on the day Magento 2.4.9 shipped.
• A strict CSP variant (magento2-default-theme-csp) for stores that need a tight Content Security Policy.

Weaknesses

• Extension gaps. Niche modules may have no compatibility module, which means writing one yourself.
• Two frontends during migration if you rely on the Luma checkout fallback.
• Paid extras add up. UI components and the native checkout cost money, and agencies often use both.
• Node.js in the build. Teams with PHP-only pipelines need to add a Tailwind build step.

Gotchas when switching

• Set the theme at both the default and website scope, as Hyvä's docs warn.
• Do not run the Tailwind build on production; commit or deploy the generated CSS.
• Clear var/view_preprocessed and pub/static/frontend and redeploy static content after switching themes.
• Recheck third-party scripts such as tag managers and chat widgets, which can undo the performance gains.

What to do next

1. Audit your extensions with the commands above and check each against the Compatibility Module Tracker.
2. Install Hyvä on staging with a free key and create a child theme.
3. Decide between the Luma checkout fallback and Hyvä Checkout before you estimate the project.
4. Measure Core Web Vitals on Luma first, so you can show the improvement after launch.