When Hyvä Theme became free and open source in November 2025, one practical question for Magento merchants was how the wider ecosystem of compatibility modules, tooling and integrations would continue to support Hyvä implementations. By June 2026, there was useful evidence of that ecosystem continuing to develop beyond the core Theme.
The Hyvä Compatibility Checker
One useful development for merchants and agencies evaluating a Hyvä migration is the third-party open-source Hyvä Compatibility Checker, maintained by Ross McKay (rossmc).
For merchants and agencies evaluating a Hyvä migration, one of the biggest questions is: "How many of our installed extensions already support Hyvä, and where will additional compatibility work be needed?"
Previously, answering that question often involved manual research: checking extensions against Hyvä compatibility resources, reviewing vendor documentation and testing modules individually.
The Compatibility Checker is a Node.js CLI tool that scans a Magento project and generates JSON and CSV reports to help teams identify modules likely to require frontend compatibility work.
Its reports include information such as:
-
module name and path
-
whether a compatibility module is installed
-
JavaScript file counts and line counts
-
PHTML file counts and line counts
-
layout file counts and line counts
-
lists of relevant frontend files
This can make the initial audit more structured, but it should not be treated as a definitive compatibility verdict.
A module can contain frontend files without all of them requiring changes, while other compatibility issues may only become apparent through functional testing.
Hyvä also provides compatibility module documentation covering how compatibility work is handled across the ecosystem.
This matters because extension compatibility remains one of the most important practical considerations when evaluating a Hyvä migration.
Hyvä states that its ecosystem includes more than 1,000 compatible extensions, but that does not mean every Magento extension works with Hyvä out of the box. Some extensions work natively, some are supported directly by their vendors, some require compatibility modules and others still need custom frontend work.
The Compatibility Checker can reduce some of the manual discovery involved in scoping a migration, but it does not replace vendor checks or staging tests.
Default Theme 1.4.6: incremental but important
Hyvä Theme 1.4.6 was released on 12 May 2026.
The functional changes in this release were in the hyva-themes/magento2-theme-module package and focused on compatibility with Magento 2.4.9 and PHP 8.5.
Hyvä’s 1.4.6 upgrade documentation lists changes including:
-
a Symfony Console command-signature update for PHP 8.5 compatibility
-
a fix for null array-offset handling in the ReCaptcha view model
-
PHPUnit 12-compatible integration tests
The Default Theme and Default Theme CSP packages were also tagged 1.4.6, but Hyvä documents them as having no functional changes in that release.
Tailwind CSS 4 support arrived earlier, with Hyvä Theme 1.4.0 in November 2025. That release also introduced changes including Design Tokens, BFCache support, stable Speculation Rules and View Transitions.
For merchants moving to Magento 2.4.9 and PHP 8.5, Theme 1.4.6 provided the relevant compatibility baseline at the time. Later Theme releases are now available, so merchants upgrading today should use Hyvä’s current release guidance.
The CSP variant deserves separate consideration.
Content Security Policy is increasingly important for eCommerce implementations, particularly around third-party scripts and payment experiences. However, using a CSP-compatible Theme package does not by itself make an entire Magento implementation compliant.
Third-party modules, custom JavaScript, payment integrations and Magento configuration can all affect the final CSP implementation.
Beyond the theme: Hyvä as a broader product ecosystem
What is notable about Hyvä’s development in 2026 is the expansion beyond the original Theme.
Looking across the ecosystem:
Hyvä Checkout continues to receive maintenance and integration updates across payment, shipping and marketing use cases.
Hyvä Admin is an open-source framework for building new Magento Admin grids. It should not be confused with the Hyvä Commerce Admin Dashboard, which provides configurable dashboard functionality within Hyvä Commerce.
Hyvä Enterprise provides compatibility and functionality for Adobe Commerce merchants, including areas such as B2B, Live Search, Product Recommendations, Loyalty Points and Gift Cards.
Hyvä announced on 1 June 2026 that, from 1 July, Enterprise would become an all-inclusive suite specifically for Adobe Commerce merchants, bringing together Hyvä Theme, Checkout, CMS, Edge, UI, Admin Theme and Dashboard, Image Editor, Media Optimisation and Menu Builder.
The announced pricing was €7,500 for the first year and €5,000 per year from the second year, at a fixed price per Adobe Commerce instance with unlimited storefronts, staging and development environments.
Before that change, Hyvä Enterprise was priced at €2,500 per year, with Hyvä Commerce available separately.
Hyvä UI provides reusable frontend components designed for Hyvä implementations, giving development teams a starting point for common interface patterns without replacing project-specific UX or accessibility work.
This breadth shows that Hyvä now covers more areas than the original storefront Theme. However, it is more useful to assess these products individually than to treat them as a single replacement for every part of the Magento or Adobe Commerce frontend ecosystem.
Practical implications for merchants
If you are already on Hyvä
Keep the Theme and related Hyvä packages within a tested update process.
Rather than upgrading solely because a new version exists, review the changelog, identify changes relevant to your implementation and regression-test the customer journeys and integrations affected by the update.
If you use a CSP-specific Theme variant, include custom and third-party scripts in that review.
Check your extension stack periodically against Hyvä’s compatibility resources and extension-vendor documentation. Compatibility can improve over time as vendors release native support or new compatibility modules become available.
If you are evaluating Hyvä
The Compatibility Checker can be a useful starting point, but it should be treated as one part of a broader audit.
Use it to identify modules with frontend files likely to need attention, then confirm:
-
whether the extension works natively with Hyvä
-
whether the vendor provides Hyvä support
-
whether a compatibility module exists
-
whether custom frontend work is still required
Validate the results in a representative staging environment.
Migration effort depends heavily on factors such as:
-
existing theme customisation
-
number and complexity of extensions
-
bespoke frontend JavaScript
-
checkout implementation
-
Page Builder customisations
-
tracking and marketing integrations
-
accessibility requirements
-
design scope
A compatibility tool can make the discovery process more structured, but it cannot produce a reliable migration timeline or budget on its own.
If you are an extension developer
Hyvä compatibility is increasingly relevant as more merchants and agencies use the Theme.
Whether a particular extension should support Hyvä, however, depends on its customer base and how much frontend functionality it provides.
Hyvä publishes documentation for making existing Magento modules compatible, and extension vendors can decide whether native Hyvä support or a separate compatibility module is the more appropriate approach.
The bigger picture
Hyvä’s ecosystem has expanded steadily beyond the original Theme.
The Compatibility Checker gives agencies and merchants another tool for migration discovery. Compatibility modules and vendor support cover a growing number of Magento extensions. Hyvä Checkout, UI, Commerce and Enterprise address different parts of the wider storefront and operational stack.
Other developments, including ElasticSuite compatibility and Hyvä’s internationalisation packages, also reduce some of the custom work required for particular implementations.
That does not mean every remaining compatibility question has disappeared.
For Magento merchants, the useful strategic question is not simply:
"Can we use Hyvä?" or: "When should we migrate?"
It is: "Does the Hyvä ecosystem support the extensions, integrations and operating requirements our store actually depends on?"
For some merchants, most of that support will already exist.
For others, important extensions or bespoke frontend functionality may still require additional compatibility work.
That is why extension auditing, staging and regression testing remain central to any Hyvä migration decision.
About On Tap
On Tap is a growth-focused eCommerce consultancy specialising in Magento and Hyvä implementations for international brands. From Hyvä migration scoping and extension compatibility audits to frontend performance optimisation and ongoing technical maintenance, On Tap helps merchants assess the practical implications of modern Magento frontend architecture.
If you are considering a Hyvä migration or want to understand how it fits your specific extension stack, get in touch.
