Hyvä in 2026: is it time to replace Luma?

For years, the question “should we move to Hyvä?” started with a license fee. That changed in late 2025. Hyvä Theme is now free, the 1.4 and 1.5 lines have shipped with Tailwind CSS 4 and strict Content Security Policy variants, and the paid products have been reorganized.

This article covers where Hyvä stands in 2026, what still costs money, how extension compatibility works, and how to decide whether replacing Luma is the right move for your store.

Where Hyvä stands in 2026

The theme is free and open source

Hyvä announced at Meet Magento Netherlands on November 6, 2025 that it would relicense Hyvä Theme under OSL3 + AFL3, the same dual license used by Magento Open Source. The change took effect on November 10, 2025. The theme is available on GitHub and through free Packagist Composer keys from the Hyvä Portal, and the supporting modules were relicensed under OSL3.

Previously the theme required a paid license. Today any Magento 2 store can install it without a fee.

Current versions

According to the Hyvä default theme changelog, the 1.4.0 release arrived on November 10, 2025. It upgraded to Tailwind CSS 4, added design tokens, introduced HTML dialog elements for the mobile menu and minicart, made view transitions stable, and replaced older slider code with Hyvä Snap Slider. The 1.4.x line continued with regular releases through 2026, and a 1.5.x line followed in July 2026 (1.5.1 on July 1 and 1.5.2 on July 10), adding PHP-rendered configurable swatches and a reworked product gallery with a built-in lightbox. Both lines ship separate CSP variants of the default theme.

CSP and PCI DSS 4.0

Hyvä’s documentation points out that PCI DSS 4.0 requires disallowing unsafe-eval and unsafe-inline for scripts on payment-related pages, effective April 1, 2025. Hyvä’s CSP approach uses nonces for inline scripts on uncached pages and SHA-256 hashes for cached content, together with an Alpine.js CSP build. A CSP-compatible default theme is published as a separate package, and Hyvä Checkout has its own CSP documentation, including a guide to running a CSP checkout without migrating the full theme.

Moving to strict CSP is a real project: every inline script in your custom code and extensions has to be compatible. Plan time for it.

What is still commercial

The theme is free. The rest of the Hyvä product line remains under commercial licenses. Prices below are taken from hyva.io at the time of writing.

Hyvä states that Hyvä Checkout can run on stores that do not use the Hyvä Theme via a theme fallback mechanism. That makes it possible to modernize checkout first and the rest of the storefront later.

Extension compatibility: the real work

Luma relies on RequireJS, Knockout.js and jQuery. Hyvä uses Alpine.js and Tailwind CSS and drops the Luma JavaScript stack. Any extension that renders something on the storefront needs a Hyvä-compatible frontend. Admin-only and backend modules usually work unchanged.

You have three options for each frontend extension:

1. Vendor support: many vendors now ship Hyvä-compatible versions directly.
2. Compatibility modules: Hyvä maintains a public Compatibility Module Tracker on its GitLab that lists available and requested compatibility modules and their status.
3. Custom rework: for in-house or unsupported modules, your team rewrites the templates and JavaScript.

Start every Hyvä project with an inventory. A quick way to list enabled third-party modules:

bin/magento module:status --enabled | grep -v '^Magento_'

For each module, record whether it affects the storefront, whether a Hyvä version exists, and whether you still need it. This audit is the most reliable way to size the project, and it often reveals modules that can simply be removed.

What a migration actually costs

With the license fee gone, cost comes from three places:

• Frontend build: recreating your design in Tailwind and Alpine.js. A store close to the default layout costs far less than one with many custom templates.
• Extension work: buying Hyvä-compatible versions, installing compatibility modules, and rewriting custom modules.
• Testing and launch: functional regression, SEO checks (URLs, structured data, canonical tags), analytics and tag manager validation, and performance verification.

Optional commercial products (Checkout, Commerce, Enterprise) sit on top. We do not publish fixed migration prices because the range is wide; a scoped audit is the only honest way to estimate it.

When replacing Luma is worth it

• Your Luma theme is due for a redesign anyway.
• Core Web Vitals are holding back mobile conversion or organic visibility.
• Frontend development is slow because every change fights RequireJS and Knockout.
• You need a clear path to strict CSP on payment pages.
• Most of your storefront extensions already have Hyvä support.

When it may not be

• You run a heavily customized Luma frontend with many unsupported extensions and a tight budget. Fixing the biggest performance issues on Luma first, or starting with Hyvä Checkout, may deliver more per euro.
• You are planning a move to a headless storefront or to Adobe Commerce as a Cloud Service, where the storefront model is different.
• You are about to do a major platform upgrade. Sequence the projects; running both at once multiplies risk.

A phased approach

1. Audit extensions and custom frontend code.
2. Upgrade Magento to a supported release line first if you are behind.
3. Optionally introduce Hyvä Checkout on the existing Luma storefront.
4. Build the Hyvä theme on staging, page type by page type.
5. Run SEO, analytics and payment regression tests, then launch outside peak season.
6. Plan strict CSP adoption as a follow-up if you did not start with the CSP variant.

Frequently asked questions

Is Hyvä Theme really free in 2026?

Yes. Hyvä Theme has been licensed under OSL3 + AFL3 since November 10, 2025. Hyvä Checkout, Hyvä Commerce, Hyvä Enterprise and Hyvä UI remain commercial products.

Does Hyvä work with Adobe Commerce?

Yes. Hyvä Theme works on Magento Open Source and Adobe Commerce, and Hyvä Enterprise is positioned specifically for Adobe Commerce instances, including B2B features.

Can I use Hyvä Checkout without moving to the Hyvä Theme?

Hyvä states that Hyvä Checkout works on non-Hyvä stores through a theme fallback. Test it with your payment and shipping extensions before committing.

Will my existing extensions work?

Backend and admin modules usually do. Storefront features need a Hyvä-compatible version, a compatibility module, or custom work. Check the Hyvä Compatibility Module Tracker and your vendors’ documentation.

Sources

• Hyvä: We’re making Hyvä Theme open source and free
• Hyvä Docs: Default theme changelog
• Hyvä Docs: Security compliance
• Hyvä Docs: Alpine.js CSP build
• Hyvä Docs: CSP checkout without migrating your full theme
• GitHub: hyva-themes/magento2-default-theme-csp
• Hyvä Checkout
• Hyvä Commerce
• Hyvä: Evolving Hyvä Enterprise
• Hyvä Compatibility Module Tracker