Hyva Enterprise Is Now All-Inclusive: The July 2026 Pricing Change Explained

What actually changed on July 1, 2026

Before this change, Hyva's commercial products were licensed separately. You picked what you needed: the theme was one purchase, Checkout was another, and the newer products around them each had their own commercial terms. That worked fine when Hyva was mostly a theme, but by 2026 the product line had grown into a real suite, and buying it piecemeal meant a procurement conversation for every addition.

The new model collapses all of that into one decision. If you run Adobe Commerce, Hyva Enterprise is now a single license that includes the full product suite, the Adobe Commerce integrations, premium support from the Hyva team, and all updates for as long as the license is valid. There is no product matrix to configure and no upsell ladder to climb later. When Hyva ships a new product next year, it lands inside the license you already have.

One thing the announcement does not spell out: migration terms for merchants who already hold existing Hyva Enterprise licenses under the old structure. If that is you, ask Hyva directly what your renewal looks like rather than assuming anything. I am not going to guess at terms they have not published.

The pricing, exactly

Here is the whole model. I have put the old approach next to it conceptually, because the structural change matters more than any individual number.

Note the currency: Hyva prices in EUR. If you budget in dollars, apply your own conversion on the day you sign, because I am not going to bake an exchange rate into a blog post that will outlive it.

What "per instance, no GMV fees" actually means

This is the part of the pricing I would highlight if I could only highlight one thing. The license is fixed per Adobe Commerce instance. It does not scale with your revenue, your traffic, or your seat count.

A lot of commerce software has moved the other way. Revenue-share and GMV-based pricing is common across SaaS platforms and their app ecosystems: you pay a percentage of what you sell, so the vendor's invoice grows every time your business does. I will not quote competitor numbers here because they change constantly, but the structural difference is the point. Under a GMV model, a great Q4 raises your software bill. Under Hyva's model, it does not. Your license costs the same in the year you double revenue as it did the year before.

"Per instance" cuts the other way too, and it is generous for multi-store setups. Magento's architecture lets one instance serve many websites and store views. Run a multi-brand or multi-country operation from a single Adobe Commerce instance and you pay for one license, with unlimited storefronts included. Add unlimited staging and development environments and the things that usually generate licensing friction in enterprise projects, like spinning up a second staging box for a big migration, simply stop being conversations.

The flip side: if you deliberately run separate Adobe Commerce instances, each instance needs its own license. That is worth checking before you architect a new project, because consolidation onto one instance now has a licensing argument behind it as well as an operational one.

What is inside the bundle

The suite covers nine named products plus the connective tissue around them:

• Hyva Theme: the storefront frontend itself, the reason most people show up.
• Hyva Checkout: the checkout experience, historically a separate purchase.
• Hyva CMS: content management built for the Hyva frontend.
• Hyva Edge: Hyva's edge delivery layer.
• Hyva UI: the component library you build sections and features from.
• Admin Theme and Dashboard: a reworked admin experience.
• Image Editor, Media Optimisation, Menu Builder: the workflow tools around content and media.

On top of the products, the license includes deep Adobe Commerce integrations: B2B, Live Search, Product Recommendations, Loyalty Points, and Gift Cards. If you are on Adobe Commerce specifically because of those native features, this matters, because historically the friction point for any third-party frontend was exactly these Adobe-proprietary modules. A frontend replacement that ships with those integrations maintained by the vendor removes the ugliest line from your compatibility risk register.

You also get access to Hyva AI Skills, premium support from the Hyva team itself, and all updates during the license validity. Support from the people who wrote the code is not a small thing on an enterprise build; I have burned days on issues that a vendor-side engineer resolved in one email.

The TCO math nobody puts on the pricing page

Now the honest part. The license is the cheapest component of a Hyva Enterprise project, and treating the license price as "the cost of Hyva" is how budgets go wrong.

Implementing a Hyva Enterprise storefront on a real Adobe Commerce store is typically a few hundred hours of work: theme build, checkout configuration, migrating or rebuilding third-party module frontends, content migration into Hyva CMS, performance tuning, QA across the catalog. Call it 300 hours for the math, and adjust for your store's complexity. I break down where those hours actually go in my Hyva migration cost guide, so I will not repeat the line items here.

Who does those hours changes the total more than anything Hyva charges:

• Agency at 100 to 200 USD per hour: 300 hours lands between 30,000 and 60,000 USD for the build alone. The license is a rounding error next to that.
• Freelancer at my rate of 25 USD per hour: the same 300 hours is 7,500 USD. The build and the first-year license end up in the same ballpark, and the whole project fits inside what an agency would bill for the discovery phase.

That is not a knock on agencies; some projects genuinely need a ten-person team. But most Hyva builds do not. They need one senior developer who has done it before and a clear scope. This is exactly the work I do as an Adobe-certified freelance developer through my Hyva theme development service, and the rate difference is the whole reason a mid-size merchant can now afford the same stack the big retailers run.

And if you are still weighing Hyva against a headless build, read my PWA Studio vs Hyva comparison first. The TCO gap between those two paths is far wider than anything in this pricing change.

Who should not buy Hyva Enterprise

The clearest disqualifier is right in the product definition: Hyva Enterprise is for merchants on Adobe Commerce. If you run Magento Open Source or Mage-OS, this product is not aimed at you, and buying decisions built on the wrong product page waste everyone's time.

Open Source stores have their own lane: Hyva Commerce, the suite for Magento Open Source, which reached version 1.3.0 "Solstice" on June 30, 2026, and deserves its own post rather than a footnote here.

A few more cases where I would tell you to hold off:

• You are mid-replatform away from Magento. Do not license a new frontend for a platform you are leaving. Obvious, but I have seen it happen.
• You are contractually committed to a headless stack. If the business has already invested heavily in a headless frontend that works, ripping it out to save on complexity is a bigger conversation than a license purchase.
• Your Luma frontend genuinely is not hurting you. Rare in 2026, but if your conversion, Core Web Vitals, and maintenance costs are all fine, you do not need to buy anything. Most stores I audit do not pass that test, which is why the audit comes first.

A decision checklist before you sign

Run through this before the purchase order goes out:

• Confirm your platform. Adobe Commerce: Hyva Enterprise. Magento Open Source or Mage-OS: Hyva Commerce. Do not mix them up.
• Count your instances. The license is per Adobe Commerce instance. Multi-storefront on one instance is one license; genuinely separate instances are not.
• Model three years. 7,500 EUR plus 5,000 EUR plus 5,000 EUR, alongside your implementation cost, gives you an honest three-year figure to put next to any alternative.
• List your Adobe-native dependencies. If you use B2B, Live Search, Product Recommendations, Loyalty Points, or Gift Cards, verify your use cases against the included integrations during a scoping call, not after signing.
• Get an implementation quote before licensing. The build is the big number. Scope it first so the license decision sits inside a real budget instead of an optimistic one.
• Existing licensee? Ask Hyva what the all-inclusive change means for your current terms, because the announcement does not say.