InhaltsverzeichnisTable of contents

Hyvä Open Source: High-End E-Commerce Without Licensing Costs

  • Kategorien:
  • Categories:
  • Performance

TL;DR

The Hyvä theme has been open source since November 2025 and can be used without a traditional theme license. For many merchants, however, another factor is even more exciting than the elimination of license fees: With Magento Open Source and Hyvä, they retain significantly more control over their system than with many SaaS solutions.
Making the switch is particularly worthwhile if you want your store to run faster, wish to remain more independent in the long term, or are planning a relaunch anyway.

In this article, we summarize the key takeaways from our deep-dive webinar with the digital agency TWOFOUR. Thomas Reichhart, Team Lead Development at TWOFOUR, brings over 15 years of Magento experience to the table and answered four questions during the webinar:

  • Where does the performance gap originate?
  • What does Adobe Commerce actually cost?
  • What makes Hyvä technically different?
  • And when does switching pay off?

Tip: If you want to understand why it’s the setup, not the platform, that determines performance, read our article “Open Source vs. SaaS: Why the Setup Matters” first.

The Performance Gap: Why Speed Is the Key to Revenue

E-commerce in 2026 is fast, and so are users. About 75% of traffic now comes from mobile devices (Source: Statista, 2025). The share of revenue is slightly lower because mobile visitors make purchases less frequently than desktop users. Nevertheless, the first impression is almost always formed on a smartphone, and that’s where the decision to stay or leave is made in a matter of seconds.

Added to this is the topic of AI, which is gaining even more importance this year. AI-powered search results shorten the customer journey, and in agentic commerce, it’s becoming clear that AI is taking over part of the purchasing decision—especially when it comes to comparable products. For you, this means your pages must be clearly structured and load quickly. This applies just as much to real customers as it does to the growing number of bots and agents crawling your store.

A streamlined front end helps you in both areas. Real visitors get the page faster, and the infrastructure remains stable even when many automated requests are running simultaneously. This way, real users compete less with bots for processing power.

In short: Speed isn’t just a matter of convenience—it’s a revenue driver. Here are a few real-world figures to illustrate this:

  • A page that loads in 1 second achieves a conversion rate roughly three times higher than a page with a 5-second load time (Source: Portent, 2024).
  • According to the same analysis, online stores that load in under 2 seconds convert significantly better than those with a load time of 3 to 4 seconds (Source: Portent, 2024).
  • Google defines a good user experience as an LCP under 2.5 seconds and a CLS under 0.1, and uses Core Web Vitals in its ranking systems (Source: Google Search Central, 2025).

User Expectations for 2026 vs. Magento Reality

A direct comparison shows exactly where the gap lies:
 

MetricExpectations for 2026Typical Magento Reality (Luma)
LCP< 2 seconds3–4 seconds
CLS (Layout Stability)stableunstable
Mobile PageSpeed Score> 9050–70

The classic Luma frontend that comes standard with Magento can certainly be improved with some effort. However, this is rarely a one-time task but rather ongoing work on the system. There is no one-click solution or module that you can install to make the store run fast afterward. With Hyvä, this ongoing effort is significantly reduced.
 

The Licensing Dilemma: Adobe Commerce or Magento Open Source?

When people hear “Magento,” they often automatically think of Adobe Commerce—that is, the paid version (formerly Enterprise). However, Magento Open Source is a fully-fledged and very powerful platform with the same core codebase. The main differences lie in the licensing model, support, and certain B2B features.

MetricAdobe CommerceMagento Open Source
Licensing CostsAnnual, revenue-basedNone (open source)
Support24/7 Adobe-SupportCommunity support
HostingCloud (often included) or on-premisesfreely selectable, self-hosted
Target Audiencemedium to large companiessmall to large companies, especially B2B

Adobe Commerce typically charges based on revenue, usually through three-year contracts. There’s an unfortunate logic to this: the more successful your store becomes, the higher your licensing costs get. So scaling up means rising fixed costs, and a portion of the budget that should actually be going toward growth ends up being spent solely on using the software.

Important: The actual cost depends heavily on revenue and negotiation. Typically, for a store with around €3 million in revenue, costs can quickly reach six-figure amounts over the contract term. For larger retailers, this adds up to several hundred thousand euros over five years—just for the license.

What’s Often Underestimated About Community Support

A common objection is that Adobe support is “more reliable” than community support. In practice, however, this isn’t necessarily the case. Magento has been on the market for a long time and has a broad user base worldwide, so you can find help almost anywhere. Often, the solution is already available in one of the many knowledge bases—and frequently faster than it would take to process a support ticket. So you don’t have to make any major compromises when it comes to support.

Be Cautious with GMV Models

There are factors that rarely show up in the initial cost estimate. Revenue-based models raise the question of exactly what is included in the calculated GMV:

  • Are orders from external systems—ones that never went through the store—included?
  • How are returns handled—for example, in the apparel sector, which has high return rates?

Such issues come to light at the latest during contract renewal and can subsequently throw off the cost calculation. This is a typical consequence of vendor lock-in. Added to this are limited data sovereignty and a front end that offers only limited customization options.

Incidentally, three assumptions often don’t hold up in practice. Time and again, experience shows that neither a cloud solution nor a high license price automatically guarantees a fast online store. There are plenty of enterprise-level online stores that run entirely on Magento Open Source and deliver reliable performance.

What Hyvä Is Doing Differently Now

The actual catalyst for the webinar was a decision made in November 2025: Since then, the Hyvä theme has been open source and is licensed under the same licenses as Magento Open Source (OSL 3.0 and AFL 3.0). The previous theme license fee of approximately €1,000 has thus been completely eliminated (Source: Hyvä, 2025). Developers, merchants, and agencies are free to use, customize, and distribute the theme, even in commercial projects.

But be aware: Open source does not mean that everything is free. The base theme is free. The following remain commercial:

  • Hyvä UI – the component library, available separately (approximately 250 € per store)
  • Hyvä Checkout – a modern, highly customizable checkout
  • Hyvä Commerce and Hyvä Enterprise – advanced feature packages

This model funds further development and keeps the ecosystem stable.

For Hyvä, this isn’t just about eliminating the theme license. What’s more exciting is the broader context: open-source commerce offers merchants an alternative to SaaS models, where many decisions regarding infrastructure, data, extensibility, and cost structure depend more heavily on the provider.

With Magento Open Source and Hyvä, the store remains technically flexible, customizable, and free from traditional SaaS lock-in. This is particularly relevant for merchants who want to retain control over their system, their data, and their future development.

At the same time, Hyvä is evolving beyond the free theme into its own commerce ecosystem. Products like Hyvä Commerce remain subject to licensing fees but do not follow a SaaS model. The licensing costs are around €3,000 per year and provide a predictable cost basis without tying usage directly to revenue, transaction volume, or a completely closed platform.

Ultimately, it’s less about the question of “free or paid” and more about how independent you want to be from your provider in the long term. 

Technically: a radically streamlined frontend stack

Luma comes with a heavy setup using Knockout.js and RequireJS—exactly the components that have been a thorn in developers’ sides for years. Hyvä, on the other hand, relies on lean tools:

  • A JS bundle under 100 KB instead of the usual frontend bloat
  • Better Core Web Vitals out of the box, without having to fight for every optimization individually
  • Full Magento compatibility—Hyvä affects only the frontend; the backend remains unchanged

Since the theme became open source, the ecosystem has been growing noticeably. More agencies and extension providers are adopting Hyvä, and the selection of compatible extensions is expanding. In addition to the theme, there is now an entire portfolio: an optimized checkout, a practical page builder, and, most recently, a POS system for brick-and-mortar retail based on the same data foundation.

For those concerned about Magento’s long-term development: The MageOS initiative will continue to develop Magento Open Source independently should Adobe ever discontinue development. The platform will therefore remain usable in the long term.
 

Real-World Examples: Two Relaunches with Hyvä

That’s the theory. What’s more interesting is how this plays out in real-world projects. During the webinar, TWOFOUR presented two examples from very different industries.
 

B2B Spare Parts: ALGEMA Fitzel

ALGEMA Fitzel is a B2B manufacturer of vehicle transporters, trailers, and accessories with its own online store. The spare parts store was migrated from a classic Magento setup to Magento + Hyvä. The year-over-year results:

  • +72% revenue
  • +43% orders
  • +8% average cart value

Context: This growth isn’t solely attributable to Hyvä. A revamped concept, improved user guidance, and additional paid traffic all played a role. However, the high-performance frontend was the prerequisite for these measures to be effective in the first place.

Design-Driven: maloja

For the outdoor brand maloja, the focus was different. Here, the emphasis was less on long, filterable product lists—as seen on Amazon and similar platforms—and more on the brand experience. The goal is to inspire users, much like a well-decorated wall in a brick-and-mortar store where pants, jackets, and accessories are displayed together.

The key factor here wasn’t the licensing issue, but rather the freedom in design. It was also important that the editorial team be able to see the design across all breakpoints—mobile, tablet, and desktop—exactly as it will appear when it goes live. With Hyvä Commerce, that’s possible today.
 
 

From Concept to Business Case: Costs and Payback Period

It sounds like a big step, but it usually isn’t. The effort involved in a switch is easy to plan because, in most cases, the backend remains the same. It’s primarily the frontend that’s replaced, often in conjunction with a relaunch and a more modern design.

A realistic look at the effort involved:

  • 2 to 4 months project duration—predictable and calculable
  • No system change—just the front end
  • Concept, implementation, testing, and content populating should be factored into the realistic timeline

Technically, a new site could be set up quickly with Hyvä. In practice, however, a solid concept is necessary to ensure that the front end, design, content, and technical requirements truly align in the end.

Financially, such a switch usually pays for itself within 12 to 18 months, depending on the initial situation. After that, the ongoing licensing costs are eliminated, and budget is freed up again for further development, optimization, and new requirements such as AI processing. The question, then, is less “How much does the migration cost?” and more: “What does stagnation cost?” In e-commerce, stagnation is the one thing you can least afford.

And what about the infrastructure?


This is where both sides converge: whoever hosts the site controls its performance. A lean front end only truly shows its advantages on a hosting platform that reliably handles traffic spikes, bot traffic, and growth. A SaaS or cloud solution is often a black box in this regard. You get what you get, and you have few options for targeted optimization.

At maxcluster, several tools are here to help you:

  • the ShopPerformance Check for a quick assessment of your current status,
  • APM powered by Tideways for in-depth performance analyses that wouldn’t be possible in a black box,
  • and the daily ShopSecurity Scan—an especially important feature given the current landscape of security vulnerabilities.

This way, you retain your data and maintain control over performance and security.

Conclusion

Hyvä’s open-source release makes getting started much easier. Today, a modern Magento front end can be implemented without an additional theme license. For many retailers, however, the most appealing aspect is that they retain control over their system and don’t have to switch to a SaaS model.

If ongoing costs outweigh the benefits, performance is holding back growth, or a relaunch is on the horizon anyway, it’s worth taking a sober look at the numbers. A modern front end is only part of the equation. How well a store ultimately performs also depends on the underlying infrastructure.

You can find the complete webinar recording with all practical examples here: High-End E-Commerce. No License Costs. With Hyvä.

FAQ

Is the Hyvä theme really free?


Yes. As of November 10, 2025, the Hyvä theme is licensed under OSL 3.0 and AFL 3.0 and is therefore free to use. The previous theme license no longer applies. However, it’s important to note that Hyvä is not entirely free. Add-on products such as Hyvä UI, Hyvä Checkout, and Hyvä Commerce remain commercial. The biggest advantage, therefore, lies not only in the elimination of the theme license but also in an open commerce approach that offers more control, flexibility, and predictable costs.

Do I have to switch my entire store system to use Hyvä?


No. Hyvä replaces the front end of your Magento store. The back end and most of the features remain unchanged. That’s why the switch is more like a relaunch than a migration.

For whom is the switch particularly worthwhile?


Above all, for merchants whose license costs exceed the benefits, whose performance is limiting growth, or who are planning a relaunch anyway. Experience shows that the payback period is 12 to 18 months.

What does hosting have to do with this?


A streamlined frontend only works on a stable infrastructure. If you host your own site, you retain control over performance and data. Managed hosting for Magento and Hyvä, combined with performance and security tools, ensures that the speed benefits are actually realized in day-to-day operations.

 

 

| Hyvä Open Source: High-End E-Commerce Without Licensing Costs