What Is Hyva? A Plain-English Guide for Magento Merchants

If you've started reading anything about modern Magento ecommerce, you've probably tripped over the word "Hyva" a dozen times. The marketing copy makes it sound like a platform. Agency blog posts make it sound like a religion. The reality is more boring and more useful: Hyva is a frontend theme, full stop.

This guide is the answer to "what actually is this thing?" for anyone in a Magento store who doesn't write code for a living. If you're after the cost or migration plan, those have their own guides.

What Hyva replaces

A Magento 2 store has three layers: the database and admin (your catalogue, customers, orders), the application logic (the PHP modules that handle the business rules), and the storefront theme (what your customers see in their browser). Hyva only changes the third one.

Out of the box, Magento 2 ships with a default storefront theme called Luma. Luma was built in 2015 around the JavaScript frameworks of the day: Knockout.js for interactivity, RequireJS for module loading, jQuery for DOM work, and Less for CSS. Each of these was reasonable in 2015. Each is now considered slow, large, or both.

Hyva replaces all of that with:

• Tailwind CSS for styling. Hyva 1.4 in late 2025 added support for Tailwind 4.
• Alpine.js for interactivity. A tiny JavaScript framework (around 15KB) that handles cart updates, dropdowns, mini-cart, and the bits Luma uses Knockout for.
• PHP templating directly, with no Knockout view models and no RequireJS loader.
• No jQuery on the storefront.

The visible result is a Magento store that ships roughly 90% less JavaScript to your customer's browser. On a typical UK store, that's the difference between a 1.5-2.5 MB Luma payload and a 50-200 KB Hyva payload.

Why anyone cares about a frontend theme

Three reasons, in roughly the order businesses notice them.

Conversion uplift from faster pages. Mobile page speed is now a measurable conversion driver, and Magento Luma stores typically score in the 25-45 range on mobile Lighthouse. Hyva stores typically score 85-95. The conversion lift varies, but UK merchants we've worked with report 5 to 15% improvements on mobile traffic post-Hyva.

Core Web Vitals pass. Default Magento 2 with Luma cannot pass Google's Core Web Vitals on mobile without aggressive customisation. Hyva passes out of the box. CWV is a real Google ranking signal, and "we're passing now" matters for organic traffic alongside the conversion impact.

Development speed. Frontend work is faster on Hyva. Tailwind plus Alpine plus PHP templates is more pleasant than Knockout plus RequireJS plus LayoutXML. Agencies report shipping new features in roughly half the time on Hyva versus Luma. For in-house teams, the same benefit shows up as faster sprints.

What Hyva does not do

This is the part most marketing copy skips. Hyva does not:

• Replace Magento. You still need Magento. Hyva sits on top of it.
• Change your data. Catalogue, customer accounts, order history, URLs, prices, inventory — all untouched.
• Fix slow hosting. If your TTFB is 1.5 seconds because your host is under-resourced, Hyva can't help.
• Fix unoptimised images. Same as above.
• Make your custom Luma modules work automatically. Anything that touched your Luma frontend needs adapting or rewriting for Hyva. This is the module audit conversation.
• Eliminate the need for a real performance pass. Hyva is the biggest single lever, not the only one.

Who built it, and is it going anywhere

Hyva was founded by Willem Wigman in 2020, with the first public release in February 2021. It's now used by thousands of Magento stores worldwide and supported by dozens of UK and European agencies, including most of the established Magento partners.

In late 2025, Hyva moved the Theme to fully open source under OSL 3.0 / AFL 3.0. That removed the previous €1,000 per-domain licence and significantly reduced the long-term platform-vendor risk for merchants. Hyva still sells paid products: Hyva Checkout (a faster alternative to the default checkout), Hyva Commerce (a bundled stack), Hyva UI (a component library), and Hyva Enterprise (for Adobe Commerce B2B installs).

Adobe / Magento has neither endorsed Hyva officially nor moved against it. The de facto position across the ecosystem is that Hyva is the modern frontend for Magento 2.

The Hyva product line in one paragraph

The Hyva Theme is the headline product and is now free. Hyva Checkout is a separate paid product (€1,000 one-off + €250/year) that replaces the default checkout with a faster Alpine-based one. Hyva Commerce (€3,000/year) is a bundle including Theme, Checkout, UI, an Admin theme, CMS tooling, and an Image Editor. Hyva UI (€250 one-off) is the standalone component library. Hyva Enterprise (€2,500/year) is the offering for Adobe Commerce + B2B installs. For a typical UK Magento Open Source store, the free Theme plus optionally Hyva Checkout is the right starting point.

Who should use Hyva

Almost every UK Magento 2 store that's actively trading and being developed. The narrow exceptions are:

• Stores in maintenance mode where there's no plan to ship features and no commercial pressure on performance.
• Stores already planning to replatform off Magento entirely within 12 to 18 months.
• B2B stores where most traffic is logged-in desktop users and Core Web Vitals doesn't drive the funnel.
• Stores with heavily Luma-dependent custom extensions that nobody wants to rewrite.

For everyone else, the question isn't "if" but "when."

If you're new to all of this

The natural next reads are Hyva vs Luma (decision-focused) and how much it costs in the UK. If you're already thinking about migrating, the migration guide walks through the plan.