Costs

Hyva Theme Cost UK 2026: Licence, Build & Total Spend

Licence is the easy bit. The honest UK total for a Hyva theme, including the build cost and the bits agencies forget to quote.

The Short Answer

The Hyva Theme itself is now free. Hyva went fully open source under OSL 3.0 / AFL 3.0 in late 2025, so the headline "€1,000 licence" you might still see quoted is historical. The cost is the build: budget £25,000 to £60,000 for a typical UK Hyva re-theme on Magento 2 in 2026, including module compatibility work, design, and QA. Greenfield Hyva builds run from £40,000 into six figures depending on complexity. If you want the Hyva-built checkout instead of the default Hyva-styled Luma checkout, that's a separate paid product (Hyva Checkout, €1,000 one-off plus €250/year support).

Costing a Hyva project is one of the most-asked questions we get from UK Magento merchants, and most of the answers floating around online are misleading or out of date. They either quote the old €1,000 licence (which no longer applies for new merchants), or quote a vague agency range that's been sandbagged so the agency doesn't get burned.

This guide breaks down what Hyva genuinely costs in 2026, what's in a typical scope, where projects go over, and the situations where the maths doesn't work in Hyva's favour.

The licence: Hyva Theme is now free

In late 2025 Hyva moved the Theme to a fully open source model. The Theme is distributed under OSL 3.0 / AFL 3.0, and you get a free licence key via the Hyva portal (with a cap on how many keys one customer or agency can hold, but no per-domain cost for the Theme itself).

What this means in practice for a UK merchant in 2026: when you compare a Hyva quote to a Luma quote, you no longer add a four-figure licence line to the Hyva side. The Theme itself is free of charge, and the cost difference between the two paths is purely the build work to swap the frontend.

The paid products in the Hyva product line today are:

Hyva Checkout. A separate optimised checkout layered on top of the Theme. €1,000 one-off per Magento installation (unlimited store views and domains), plus €250/year for ongoing support and updates, or a flat €1,000 for a five-year package.
Hyva Commerce. The newer bundle that includes Theme, Checkout, the Hyva UI library, an Admin theme, CMS tooling and an Image Editor. €3,000/year (or €12,000 for a five-year bundle).
Hyva UI. A standalone component library, €250 one-off, useful if you're building bespoke pages outside the Theme.
Hyva Enterprise. €2,500/year, targeted at Adobe Commerce + B2B installs.

Most UK merchants doing a Luma to Hyva re-theme on Magento Open Source need only the free Theme plus, optionally, Hyva Checkout. The Commerce and Enterprise bundles are for stores already using the wider stack or running Adobe Commerce B2B.

The build: where the real money goes

The Theme is free. The build is where most of the budget goes.

For a UK Magento 2 store currently on Luma migrating to Hyva, the typical 2026 cost range is:

£15,000 to £25,000 for a small DTC store with a standard module stack and a near-default Luma theme. You're buying a re-theme that ships in 6 to 10 weeks.
£25,000 to £60,000 for a typical mid-market UK store. Customised Luma theme that needs translating to Hyva, 5 to 15 third-party modules to audit and potentially port, some bespoke product page work, and proper QA across the catalogue.
£60,000 to £120,000+ for stores with heavy customisation, multi-brand setups, B2B account features, custom checkout flows, or PIM/ERP integrations that touch the frontend.

If your store is on Adobe Commerce Cloud, add 10 to 20% for the extra environment and deployment complexity. Adobe Commerce on-premise is no different from Open Source on this front.

What's in a typical Hyva quote

A defensible Hyva quote should include:

Module audit. An itemised list of every Magento extension on the store, with a verdict on each: compatible out of the box, compatible via a Hyva Compatibility Module Tracker entry, needs a Hyva-native rewrite, or can be removed. This is the single most under-scoped step.
Theme implementation. Hyva ships with a default theme. Almost no merchant ships that as-is, so the design work is to take your current visual identity and re-implement it in Tailwind. If your current Luma theme is a customised PageBuilder mess, this is more work.
Product page customisations. Anything you do on PDPs that isn't standard (configurable products with non-standard swatches, custom tabs, dynamic pricing, related-product widgets) needs porting.
Checkout strategy. Stay on the Hyva-styled Luma checkout (default, no extra cost), or buy Hyva Checkout for a faster, Alpine-based one.
Performance pass. Image strategy, font loading, third-party scripts. Hyva won't fix any of these for you.
QA across browsers and devices. Real QA, not "we tested it on the developer's MacBook."
Cutover plan. How you switch from Luma to Hyva in production, what your rollback is, and how you handle SEO during the switch.

If any of these are missing from a quote, ask why. The honest answer is sometimes "we'll handle it in the build budget," which is fine if it's explicit. The bad answer is silence followed by a change request in week 8.

Where Hyva projects blow up

Three places, in our experience and every UK Hyva agency we've spoken to:

Module compatibility. Stores with 30+ extensions installed almost always have a long tail of niche ones that the Compatibility Module Tracker doesn't cover. Each one is a small judgement call: rewrite, swap, or remove. A few small judgement calls add up.

PageBuilder content. If your marketing team built the homepage and category pages with Magento PageBuilder, that content needs migrating. Hyva supports PageBuilder, but the existing content may rely on Luma-specific styling that doesn't translate cleanly. Plan for a content audit and rework.

Custom checkout customisations. Any custom Luma checkout work (multi-step changes, custom fields, payment integrations with bespoke UI) doesn't survive a switch to Hyva Checkout. You're rebuilding it.

Total cost of ownership, year one

For a typical mid-market UK Hyva re-theme:

Hyva Theme licence: free
Build: £35,000 (mid-point of the range)
Hyva Checkout (if you go for it): €1,000 one-off + €250/year (~£1,075 in year one)
Hosting: unchanged from your current Magento setup
Ongoing support: 10 to 20% of build per year is the agency norm

Year one total: in the £35,000 to £50,000 range for a typical UK mid-market store. That's the number to plan around.

When the maths doesn't work

Be honest about whether Hyva is the right spend. The maths against Hyva is:

You're under £500,000 annual revenue and the conversion-uplift case can't recoup £35,000 of build in 18 months.
You're already planning to replatform off Magento entirely within 18 months.
Your performance problem is actually hosting, not the frontend. Move to better hosting first and re-evaluate.
You're a B2B store where 95% of orders come from logged-in account users on a desktop, and Core Web Vitals doesn't move your funnel.

In any of these scenarios, look at hosting upgrades, image optimisation, and third-party script cleanup before committing to a Hyva build.

Getting accurate quotes

The single best thing you can do before talking to an agency is to send them your current Magento 2 module list. Run bin/magento module:status, paste it into the brief, and any decent agency will give you a far sharper estimate than they would from a generic "we're on Magento 2 with Luma" message.

If you want quotes from UK Hyva specialists who've shipped projects in your size band, use the quote form. We'll match you with two or three teams to compare on like-for-like scope.

Frequently asked questions

Wait, the Hyva Theme is really free now?

Yes, since late 2025. Hyva announced at Meet Magento Netherlands that the Theme would move to fully open source, distributed under OSL 3.0 / AFL 3.0 with free licence keys via the Hyva portal. The historical €1,000 per domain pricing still gets quoted in older blog posts but isn't the model for new merchants. Hyva's paid revenue now comes from Checkout, Commerce, UI, and Enterprise tiers.

Why are agency Hyva quotes so different from each other?

The biggest variable is how thoroughly the agency has scoped your module stack. A £15,000 quote that ignores your extensions will turn into £30,000 of change requests in week 6. A £35,000 quote that itemises every module is usually closer to the real number. Send agencies your module:status output and they'll quote tighter.

How long does a Hyva re-theme take?

8 to 14 weeks is typical for a UK mid-market store. Faster than that and either the scope is unusually clean or the agency is cutting corners. Slower than that and the customisations are heavier than average.

Do I need Hyva Checkout, or is the default Hyva checkout fine?

The default Hyva theme uses a Hyva-styled version of Magento's Luma checkout under the hood. That's faster than Luma but slower than Hyva Checkout. If your checkout drop-off is a known conversion problem, the €1,000 + €250/year for Hyva Checkout typically pays for itself. If your conversion bottleneck is somewhere else (PDPs, category navigation), stay on the default and save the budget.

What about Hyva Commerce?

Hyva Commerce is the newer €3,000/year bundle that combines Theme, Checkout, UI library, Admin theme, CMS tooling and an Image Editor. Sensible if you're using more than just the Theme; less sensible if you only need the storefront and a fast checkout, in which case the standalone Theme (free) + Checkout (€1,000 + €250/yr) is cheaper.

Will Hyva still be around in five years?

Hyva is the de facto modern frontend for Magento 2, with a large community and broad agency adoption, and the move to open source in 2025 reduced the platform-vendor risk meaningfully. Adobe / Magento haven't endorsed Hyva officially but haven't taken any position against it either. The bigger long-term risk is Magento itself, not Hyva specifically.

Built by Limely

Ready to get a quote for your project?

We're a UK Magento agency. Tell us what you're working on and we'll come back with a straight answer.

Get a quote