Is Hyvä a Theme, a Framework, or Both?

Hyvä is technically a theme, since you install it the same way you install any other Magento 2 storefront theme. But in practice it behaves like a frontend framework, because it does not just restyle Magento’s default frontend, it replaces the entire rendering stack underneath it. That dual identity is why the “theme or framework” question comes up so often.

Why Hyvä counts as a theme

Structurally, Hyvä is packaged and applied the same way Luma is. You install it as a theme in your Magento instance, assign it to a store view, and it controls layout, templates, and styling from there. Merchants and developers who have only worked with traditional Magento themes will recognize the installation pattern immediately.

Why Hyvä also counts as a framework

Where Hyvä stops acting like a normal theme is under the hood. It strips out Knockout.js, RequireJS, jQuery widgets, and LESS, the technologies Luma relies on for interactivity and styling. In their place, Hyvä uses standard server-rendered Magento PHTML templates, Tailwind CSS for styling, and Alpine.js for interactivity. That is a full architectural swap, not a reskin, which is why most engineers describe Hyvä as a frontend framework rather than a simple theme.

This distinction matters practically. Extensions built against Knockout or RequireJS do not just work under Hyvä. They need Hyvä-compatible modules, because the rendering approach itself has changed.

What this means if you are evaluating Hyvä

The core Hyvä Theme has been free and open source since November 10, 2025, released under version 1.4.0 and licensed under OSL 3.0 and AFL 3.0, the same dual license Magento Open Source itself uses. Add-on products built on top of it, such as Hyvä UI, Hyvä Checkout, Hyvä Commerce, and Hyvä Enterprise, remain separate paid products. So the free, open source piece is the framework layer itself. The commercial layer sits on top of it, not underneath it.

If you are planning a move from Luma to Hyvä, treat it as a frontend rebuild project, not a theme swap. Extension compatibility, custom components, and checkout behavior all need to be re-evaluated. Our Magento 2 development team handles this as a standard part of Hyvä migration work if you want a second opinion on scope before committing.