What is Hyvä Commerce?, FAQs: 12 questions answered.

No, they are different products from the same company. Hyvä Theme is a free, open-source (OSL3) Tailwind + Alpine storefront frontend for Magento, released to free in November 2025. Hyvä Commerce is a paid commercial suite of admin, media, and CMS modules that sits on top of Magento Open Source. You can run Theme without Commerce, but most stores that buy Commerce also use Theme.

Hyvä doesn’t publish a public price, the license is sold direct from hyva.io and priced in bands by your annual GMV (typically €1M, €100M target band). Reach out to Hyvä or your Hyvä-certified partner for a quote. As a reference, the licence usually pays for itself within the first year of cancelling a Cloudinary / imgix subscription for a mid-market merchant.

The 1.2 release (May 2026) moves two flagship modules from beta to general availability: the Admin Dashboard (with Launchpad, Checklist, Links & Text widgets, and a Hyvä CMS Scheduled Releases overview) and the Media Optimisation suite (automatic WebP + AVIF conversion, configurable resizing, CLI tools for batch operations). Both have been hardened through months of merchant testing before this release.

For most SMB and mid-market stores, yes. Media Optimisation runs on your own server: it converts uploaded images to WebP and AVIF, resizes to admin-configurable max dimensions, and serves the right format per browser, no external service, no per-image cost, no bandwidth fees. The trade-offs vs Cloudinary are: (a) you handle the compute, (b) no on-the-fly URL transforms, (c) no DAM features. For a typical product-catalogue use case, those don’t matter.

No, the framework is designed to coexist. You can enable Hyvä’s dashboard, the default Magento one, or both. Existing third-party admin extensions (Mageplaza, Amasty, custom Adobe Commerce Analytics widgets) keep working unchanged. The new dashboard appears as an additional choice in the admin landing-page configuration, not a forced replacement.

Hyvä Commerce 1.2 supports Magento Open Source 2.4.7 and later (including the latest 2.4.9, released 12 May 2026). PHP 8.3, 8.4, or 8.5 is required. For Adobe Commerce, you need Hyvä Enterprise instead, that’s the compat tier that adds Adobe’s B2B suite, customer segments, and content staging features that Open Source doesn’t ship.

Yes. Media Optimisation ships CLI tools specifically for that. Point the worker at your pub/media directory, set concurrency (usually 4-8 workers on a typical 4-vCPU VPS), and let it run overnight. A 50,000-image catalogue typically finishes in 6-10 hours. The originals are preserved, WebP/AVIF derivatives are generated alongside, so you can roll back per-image if quality issues arise.

Hyvä Commerce emits a <picture> element with the AVIF source, a WebP fallback, and the original JPEG/PNG as the universal fallback. Modern Chrome, Firefox, Edge, and Safari 16+ all support AVIF. Older Safari and obscure browsers serve WebP (supported in every major browser since 2020). The ultimate fallback (~0.1% of traffic) still gets the original. No JavaScript needed.

Technically yes, the Admin Dashboard and Media Optimisation modules don’t depend on the Hyvä Theme storefront. You can install Hyvä Commerce on a Magento store running the default Luma theme. In practice, almost every Hyvä Commerce store also runs Hyvä Theme, because once you’ve adopted Hyvä’s tooling on the admin side you usually also benefit from the storefront performance gains.

For a typical SMB / mid-market merchant on Magento Open Source: 2-3 weeks end-to-end. That breaks down as 1 day audit, 1-2 days install + configure, 0.5 day Media Optimisation config, 1 day + overnight catalogue migration, and 1 week of post-launch stabilisation before cancelling the old CDN. Stores with heavy custom admin extensions or complex CMS layouts add 1-2 weeks for compat work.

No. Hyvä Theme became fully open-source (OSL3 + AFL3) in November 2025, but Hyvä Commerce remains a closed-source commercial product. Source code is available to license holders for review, customisation, and forking within your team, you just can’t redistribute it. This is the standard model for paid Magento extensions.

You probably don’t need Commerce if: (a) your store is under €1M GMV, (b) you don’t pay for an image CDN today, (c) you’re happy with the default Magento admin, and (d) you don’t use Hyvä CMS. You probably do need Commerce if: you pay > $1,000/yr for Cloudinary/imgix/Cloudflare Images, your content team complains about the Magento admin, or you want Scheduled Releases for marketing campaigns. The break-even is usually around €5M GMV.