Hyvä explained: is a Magento front-end rebuild worth it?

A Hyvä rebuild is worth it when your Magento store is healthy underneath but slow and expensive to change on the front end, and you’re staying on Magento for at least a few more years. The theme itself has been free since November 2025, so the cost is the build work, not a licence. It is not worth it on an unsupported Magento version unless you upgrade first, and it won’t rescue a store whose real problems are in the backend.

What Hyvä is

Magento 2 has two halves: the backend (catalogue, orders, pricing, integrations) and the front end, the pages customers actually see. Magento’s own front end, called Luma, is built on a large stack of JavaScript libraries that makes pages heavy and slow, and makes every change fiddly and costly for developers.

Hyvä is a replacement front-end theme. It throws away most of that stack and rebuilds the storefront with a much lighter set of tools. The backend stays exactly as it is: same admin, same data, same integrations.

What changed with licensing

Hyvä used to be a paid theme. On 10 November 2025 the company relicensed the Hyvä Theme and its supporting modules as open source, under the OSL3 and AFL3 licences. That means no licence fee to use it.

Not everything went free. Hyvä says its Checkout, Enterprise and Commerce products remain proprietary, and Hyvä UI (a library of ready-made page components) is a separate paid product at €250 per Magento store. For Adobe Commerce merchants, Hyvä Enterprise bundles the theme, checkout, UI and other modules for €7,500 in the first year and €5,000 a year after, per Adobe Commerce instance.

Prices are Hyvä’s published figures in euros, checked on 3 October 2026. The licence was never the big cost of a Hyvä project; the build is.

What Hyvä fixes

Page speed. This is why Hyvä exists. Lighter pages load faster, particularly on mobile, and that’s what customers and Google’s page experience measures notice. How much faster depends on your current theme, images and third-party scripts: a Hyvä build loaded with tracking tags and chat widgets will still be slow.

The cost of front-end changes. Luma is hard to work on, so small changes take longer than they should. Hyvä is simpler, so the same change usually takes less developer time. Over a few years of normal trading, that matters as much as speed.

A cleaner starting point. A rebuild is a chance to drop the dead features and half-used extensions that accumulate on a long-lived store. I ran a Hyvä relaunch for a premium AV retailer, and the cleanup was as valuable as the new theme.

What Hyvä doesn’t fix

• An unsupported Magento version. Hyvä doesn’t change the platform underneath. If you’re on a release that no longer receives security patches, you still are after a Hyvä build.
• Backend debt. Slow admin, stuck indexers, a database full of old data, custom modules nobody understands: all still there.
• Extensions. Every extension that touches the storefront needs a Hyvä-compatible version, a compatibility module, or rebuilding. Some vendors support Hyvä well; others don’t at all. This is often the largest unknown in a quote.
• Integrations. Stock, accounts, couriers and marketplaces work as before, which is good, but a broken integration stays broken.
• Hosting. A fast theme on an underpowered server is still a slow store.

How it fits with Magento end of support

Adobe publishes fixed support dates for each Magento 2.4 release. As of today, 2.4.6 left standard support on 11 August 2026, 2.4.7 leaves it on 31 May 2027, and 2.4.8 on 31 May 2028. Extended support after those dates is for Adobe Commerce customers only; Adobe says extended support patches aren’t available for Magento Open Source. The Magento end of support guide covers what this means in detail.

The sensible order is usually: upgrade to a supported release first (2.4.8 or later), then rebuild the front end on Hyvä. Doing both in one project is possible and can save duplicated testing, but it makes the project bigger and riskier. Building Hyvä on an out-of-support version means paying for a new front end on a platform you’ll have to upgrade anyway.

Not sure which version you’re on? The Magento support checker tells you in seconds.

Checkout options

Checkout is where most of the decisions sit, because it’s where the money changes hands and where extensions cluster (payments, delivery options, address lookup).

1. Hyvä Checkout. Hyvä’s own checkout. It works with a Hyvä storefront and can also run on a non-Hyvä store through Hyvä’s Theme Fallback route. Standard Magento checkout integrations often need compatibility work; confirm your payment, delivery and address-lookup modules before choosing it. €1,000 one-off licence.
2. Keep the existing checkout. Hyvä provides a fallback module that switches back to a traditional Magento theme on checkout pages, so you can keep the default Magento checkout or a supported third-party one-step checkout. It’s a practical bridge, though Hyvä itself recommends its own checkout for performance.
3. A third-party checkout with Hyvä support. Some checkout extension vendors now offer Hyvä-native versions. Check the payment and delivery modules you rely on before choosing.

Whichever you choose, list every payment method, delivery option and checkout extension you use today, and confirm each one works before the build starts, not during testing.

What a Hyvä project involves

A Hyvä build is a front-end rebuild, so treat it like one. The shape is usually the same whoever does it.

1. Audit. List every extension, custom module and third-party script that touches the storefront, and check each for Hyvä support. This step decides the budget, so don’t let anyone skip it.
2. Design. Either reproduce the current design faithfully, which is quicker and easier to test, or take the chance to redesign. Mixing the two halfway through is how timelines slip.
3. Build and compatibility. Templates are rebuilt, and extensions without native support get compatibility modules or custom work.
4. Testing. Every page type, on real devices, with real payment methods, delivery options and promotions. Test against written acceptance criteria rather than a general look around.
5. Launch and measure. Record page speed and conversion before launch so you can compare like for like after it, rather than relying on anyone’s impression.

Because the backend doesn’t change, there’s no data migration and no URL change, which removes the two biggest risks of a replatform. Rebuilding content, titles and structured data faithfully reduces search disruption, but rankings still need monitoring after launch.

Ask any agency quoting for Hyvä how they’ll handle each extension, which checkout they’re proposing and why, and whether the quote includes a Magento upgrade or assumes you’ve done it. Those three answers explain most of the difference between quotes.

Hyvä or replatform?

The question underneath is whether Magento still fits the business. If it does, Hyvä makes it cheaper to live with. If it doesn’t, a new theme won’t change that, and I’ve written a separate guide on leaving Magento for Shopify or WooCommerce. For the wider picture, see choosing a platform.

Where to start

I’d start with a health check of the whole store: version, extensions and whether each has Hyvä support, custom code, hosting and integrations. That tells you whether Hyvä is the right next step, what has to happen before it, and what a fair brief for agencies looks like.

My Magento version and support review is from £750, with the fee agreed before work starts. I review the available platform information with you and your developer; deeper technical testing is scoped separately. If an upgrade needs to come first, I can help scope and coordinate it with specialist developers, whose implementation work is quoted separately. And if your current front end is fine for now, you’ll hear that too.