Hyva Adobe Commerce theme development, built for speed.

Hyvä is a product suite for Magento 2 and Adobe Commerce. It started as a frontend theme and today it also covers the checkout, content management and the admin panel. On Adobe Commerce it replaces the default Luma theme layer while the Magento backend stays where it is.

Hyvä Themes say the name comes from the Finnish language and literally means good, and also desirable and advisable. It is often written without the umlaut, so a search for Hyva Adobe Commerce and a search for Hyvä Adobe Commerce mean the same thing.

Hyvä Themes state that the Hyvä Theme is now entirely open source and free, available on GitHub and via free license keys, under the OSL and AFL license. The Hyvä theme free of charge is the starting point; the design, build and compatibility work on top of it is what you are paying an agency for.

Tailwind CSS and Alpine.js. Hyvä's own technical vision says it keeps what it considers great in Magento — layout XML, blocks, view models and phtml — and got rid of Knockout, RequireJS and jQuery. That smaller tech stack is where most of the frontend performance comes from.

Through Composer. Hyvä's documentation installs the default theme package with Composer and then runs bin/magento setup:upgrade to register the new modules against a Magento installation. Installing Hyvä on a staging copy first is how we keep a live online store untouched while the build runs.

Hyvä's documentation lists Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7, 2.4.7-p1 or higher, on PHP 8.1, 8.2, 8.3 or 8.4, and notes that Hyvä no longer supports PHP 7.4. The Tailwind compiler needs Node.js 20 or higher on development environments.

Yes. Hyvä runs on Magento Open Source as well as Adobe Commerce. Hyvä Commerce is the vendor's all-in-one suite aimed at Magento Open Source, bringing the theme, the checkout, Hyvä CMS and the Hyvä UI component library together, so the UI components come from one place.

Hyvä Enterprise is the vendor's Adobe Commerce edition of the suite, described on their site as Adobe Commerce without the complexity. Hyvä Enterprise brings Adobe Commerce features such as the B2B Suite, Live Search, Product Recommendations, Loyalty Points and Gift Cards onto the Hyvä front end. In practice Hyvä Enterprise combines the Hyvä theme layer with capabilities you already license from Adobe. Access to Hyvä Enterprise is arranged with Hyvä Themes directly, not through us.

Hyvä Enterprise lists the Adobe Commerce B2B Suite among the features it supports. Whether your own B2B behavior carries across — customer groups, shared catalogs, requisition lists, negotiated quotes — is a per-module question we answer in the compatibility audit rather than with a blanket yes.

Not automatically. Hyvä has compatibility modules for many third party extensions, and anything without one needs its front end rebuilt. Seamless integration is not a default setting: we inventory every extension on your Magento store and mark it compatible, portable or rebuild before anyone quotes a Hyvä migration.

Not always. You can run the Hyvä theme and keep your current checkout, or move to Hyvä Checkout so the whole flow is Hyvä compatible. Which one fits depends on the payment, tax and shipping modules your online store already relies on, and on how customized the present checkout is.

It is a different trade-off, not a better one. A headless PWA decouples the storefront and adds a separate front-end application to run and staff; Hyvä keeps server-rendered Magento and replaces the theme layer. We size both against your roadmap and your team before recommending either.

Adobe Edge Delivery Services is one of Adobe's own storefront options for Adobe Commerce. Adobe's documentation describes Commerce storefronts powered by Edge Delivery Services, PWA Studio or headless implementations working with the same drop-ins and APIs. It is a different path from Hyvä, which is a Magento-native theme layer built by Hyvä Themes rather than by Adobe.

No. Hyvä removes a large part of the front-end JavaScript that weighs down a Luma theme, but passing Core Web Vitals also depends on hosting, images, third-party tags and backend response times. We measure your field data first and say what strong Core Web Vitals will actually take on your stack.

It removes friction, and nobody honest will promise speed alone will increase conversions. Storefront speed is one input; catalog, pricing, merchandising and trust do the selling. We report website speed and conversion rates side by side after launch so you can see which one moved.

Indirectly at best. Google states that Core Web Vitals are used by its ranking systems, while also saying Search seeks the most relevant content even when the page experience is sub-par. Treat higher search engine rankings as a possible effect of improved performance, not as the reason to migrate.

It depends on the extension inventory and how much custom front-end code sits on your current theme. The accelerator ranges on this page are what we plan against; the compatibility audit is what turns a range into a date you can hold us to.

Hyvä Themes provide free access to community support on their Slack and online documentation for developers. Our own Hyvä support and updates cover the storefront we built: version and security updates, new features, monitoring and continuous performance optimization as your business grows.

Yes, if your developers have only worked on Luma. The learning curve is mostly Tailwind CSS and Alpine.js; the Magento layout XML, blocks and phtml they already know stay in place, which is why most in-house teams pick Hyvä up faster than a headless rebuild.

Less front-end code generally means less to maintain, but maintenance cost tracks how many custom modules you carry, how often you take Magento security releases, and how much of the theme is bespoke. Ask any agency for that picture across two years, not just the build.

Yes. CMS pages, blocks and content carry over in a Hyvä migration; what changes is the markup they render into. Hyvä CMS is available in the suite if you want a visual editor with live preview, and all the features your merchandising team uses today get checked off before go-live.

Magento merchants keep the admin they already know, because Hyvä changes the storefront rather than the back office, and the Hyvä suite also includes an admin theme. Day to day the user experience stays user friendly for the people running promotions, pricing and catalog.

Access to a staging environment, a current list of extensions and themes, and someone who can decide on scope. We agree on the extension inventory and the definition of done in writing before development starts, so nothing about the Hyvä theme development scope is discovered halfway through.

It speeds up the front end. Hyvä does not optimize the backend, so slow catalog queries, a cold cache or an undersized server still show up in your website's performance. We profile both layers before quoting, and say plainly when the bottleneck is not the theme.

Hyvä Themes state the license will be valid for one Adobe Commerce installation, with unlimited domains and storeviews. A single Adobe Commerce installation with unlimited domains and storeviews therefore sits under one license. The commercial terms come from Hyvä Themes, not from us, and we do not publish license figures on a web page.

Yes. Hyvä Themes publish the Hyvä Theme under the OSL and AFL license, available on GitHub and via free license keys, with online documentation. A free theme license changes what you budget for: the software stops being the line item and the build, the compatibility work and the testing become the cost.

By shipping less, and by documenting the habits that keep it that way. Hyvä's own performance guidance asks you to lazy-load every image not visible on first paint, set explicit width and height on every image, serve WebP or AVIF where possible, replace animated GIFs with video elements, defer third-party scripts until user interaction, and delay Alpine components until they approach the viewport. None of that is magic and all of it is checkable.

Four things: which of your extensions have compatibility modules and which need a front-end rebuild, how customized your current checkout is, whether your own team can carry Tailwind CSS and Alpine.js after handover, and what your field Core Web Vitals look like today. Choose from evidence about your store, not from a demo score on someone else's site.

When the storefront is already fast, when the roadmap for the next two quarters is backend and integration work, or when the front end was custom-built recently and still converts. A theme rebuild is a large change and should be justified by measured problems, not by the age of the code.

You do. The Hyvä theme is open source under the OSL and AFL license, and the custom theme built on top of it is delivered into your repository. We agree on code ownership, branch strategy and handover in writing before development starts.