Send a brief
Menu

What is Hyvä Themes?

Hyvä Themes is a complete Magento 2 frontend rebuild on Tailwind CSS 3.4 + Alpine.js 3.x, designed as a drop-in replacement for Magento’s default Luma theme. Released in 2020 by Hyvä, licensed at $1-2k one-time per project. Delivers Lighthouse 95+, ~85% smaller JS bundle, and 8-25% documented conversion lift over Luma.

Send a brief WhatsApp first
  • Released 2020 by Hyvä
  • Stack Tailwind CSS 3.4 + Alpine.js 3.x
  • License $1-2k one-time per project

Five things Hyvä actually changes under the hood

Hyvä is not a re-skin. It is a frontend stack rewrite that swaps Luma's 2015 toolkit for the 2024 web. Here is what that means concretely.

  1. 01Replaces the Luma JS stack wholesale

    Hyvä rips out jQuery 2.2, RequireJS, KnockoutJS and Magento UI Components, the entire Luma frontend stack, and replaces it with two libraries: Tailwind CSS 3.4 (utility classes, no LESS cascade) and Alpine.js 3.x (3 KB reactive sprinkles). Net result is ~85% less JavaScript shipped to the browser, ~70 KB total Hyvä payload vs ~450 KB Luma payload.

  2. 02Server-renders HTML, sprinkles Alpine for interactivity

    Unlike PWA Studio (full SPA, React on top of GraphQL), Hyvä is a server-rendered theme. Magento renders the HTML on the PHP side as it always has; Alpine handles small interactive bits: drawers, modals, mini-cart toggles, quantity steppers. No SPA, no client-side router, no hydration cost. Magewire (Hyvä’s Livewire port) handles richer state when needed without leaving server-rendered land.

  3. 03Hyvä Compatibility Module bridges Luma extensions

    The biggest concern with any Magento frontend rebuild is "what about my paid extensions?" Hyvä ships a free Compatibility Module that wraps most marketplace extensions (built for Luma) so they render inside a Hyvä theme without code changes. As of 2026, ~80% of major paid Magento extensions are either natively Hyvä-compatible or covered by the Compat Module: manual port effort is minimal.

  4. 04Hyvä Checkout is a separate $1k product

    Theme and checkout are decoupled. Hyvä Themes ships with the storefront catalogue (PLP, PDP, header, footer, mini-cart) but uses Magento’s default Luma checkout out of the box. To get the full performance win you also buy Hyvä Checkout, a separate one-time license that replaces the slow Magento checkout with an Alpine + Magewire equivalent. Most stores see ~50% of their conversion lift from the checkout swap alone.

  5. 05Compatible with Magento 2.4.4+ Open Source and Adobe Commerce

    Hyvä works on every supported Magento version from 2.4.4 onwards, on both Magento Open Source (free) and Adobe Commerce (Pro / Cloud). It is not a fork of Magento: it is a theme + module package that drops into a normal Magento install. You keep the same admin, same product attributes, same pricing rules, same B2B structure. Only the storefront rendering layer changes.

Four situations where Hyvä is the obvious answer

Hyvä isn't universally correct, but in 2026 these four scenarios are unambiguous wins.

  • New Magento builds in 2026

    Adobe’s own 2025 keynote recommended Hyvä as the default starting point for new Magento storefronts. Building new on Luma in 2026 is opt-in regret: you pay the migration cost later anyway. Pick Hyvä on day one and ship a fast site from launch.

  • Existing Luma stores below Lighthouse 60

    If your current Luma store is sub-60 on mobile Lighthouse, fixing performance inside Luma hits a hard ceiling around 70, beyond that you fight the framework. Hyvä migration takes Lighthouse from 30-50 to 95+ on the same hardware, same database, same product catalogue. The conversion lift typically pays for the migration in 3-6 months.

  • Fashion, electronics, B2B: conversion-led stores

    Sectors where mobile UX directly drives revenue benefit most. Fashion (impulse buying, image-heavy PLPs), electronics (long PDPs, rich attribute filters), B2B (large catalogues, complex configurators) all see the steepest conversion lift after Hyvä migration. If conversion rate is a tracked KPI and mobile is over 50% of traffic, Hyvä is the highest-ROI frontend investment available.

  • Performance-critical peak season (Diwali, BFCM)

    Stores running Diwali, Black Friday / Cyber Monday, or back-to-school promotions cannot afford a sub-1s LCP failure under traffic load. Hyvä’s ~70 KB JS bundle and server-rendered HTML mean origin servers spend less CPU per request, edge caching works better, and mid-tier Android devices on 4G stay responsive when desktop traffic spikes 10x. Migrate before, not during, peak.

Three traps that turn a Hyvä migration into a project rescue

Every overrun Hyvä project I've been called in to rescue made one of these three mistakes early. Avoid them and the migration runs on schedule.

  • Skipping Hyvä Checkout

    A Hyvä theme on top of the stock Magento Luma checkout still ships ~250 KB of jQuery + KnockoutJS the moment a customer hits step one. You leave roughly half of the perf win on the table, and worse, the checkout is the page where slow JavaScript hurts conversion most. Always budget Hyvä Themes ($1-2k) plus Hyvä Checkout ($1k) together. Treat them as a single line item, not two separate decisions.

  • Migrating without an extension audit

    Most Luma stores carry 20-40 paid extensions accumulated over years. Migrating without first auditing each one against the Hyvä Compatibility Module ships you straight into broken PLPs and missing storefront features in week 6. Always inventory every extension on day one, classify each as native-Hyvä / Compat-Module / replace / drop, and lock the list before any theme work starts. The audit takes 3-5 days and saves weeks of rework.

  • Treating Hyvä as a UI refresh

    Hyvä is not a re-skin, it is a frontend stack rewrite. PHTML templates rewritten, LESS dropped for Tailwind, KnockoutJS replaced with Alpine, custom modules ported. Plan for 4-12 weeks of dev time depending on customisation depth, plus QA, plus a soft-launch window. Stores that scope it as a "theme swap" routinely overrun by 2-3x. Brief the project as a frontend rebuild, with a feature freeze on the Luma side for the duration.

Where Hyvä Themes sits in the wider Magento landscape

Five neighbour concepts most readers want to look at next. Click through for the full deep-dive.

See the serviceRead the comparison

Hyvä Themes: frequently asked questions

Is Hyvä Themes free?
No. Hyvä Themes is a one-time commercial license, typically $1,000, $2,000 per project depending on the variant (single-store, multi-store, agency). The license is perpetual: you pay once per major version, not per seat or per month. Hyvä Checkout is a separate $1,000 license. Compared with the conversion lift most stores see (8-25%), the license cost is recouped within the first few months of go-live.
Does Hyvä Themes work with Adobe Commerce?
Yes. Hyvä is fully compatible with both Magento Open Source and Adobe Commerce (formerly Magento Commerce) on versions 2.4.4 and above, including Adobe Commerce Cloud. You keep all the Adobe Commerce features, B2B, content staging, page builder, customer segments, and only the storefront rendering layer changes. The Hyvä Adobe Commerce license is sold at the same price as the Open Source license.
Can my Magento extensions still work?
Most of them, yes. Hyvä ships a free Compatibility Module that wraps Luma-only extensions so they render inside a Hyvä storefront. As of 2026, the vast majority of popular paid Magento extensions are either natively Hyvä-compatible (vendor ships Hyvä support out of the box) or covered by the Compat Module. The remaining ~10-20% need either a paid native port from the vendor, a manual port by your dev team, or a swap to a Hyvä-native equivalent. Always run a per-extension audit before migration.
Is Hyvä the same as headless Magento?
No. Hyvä is server-rendered, not headless. Magento renders the HTML on the PHP side, Hyvä uses Alpine.js for small client-side interactions. Headless Magento, typically PWA Studio with React on top of GraphQL, is a different architecture: separate frontend app talking to Magento purely through API. Hyvä is simpler, cheaper to maintain, and faster on most metrics. PWA Studio is more flexible if you need a single frontend across multiple backends or a native mobile app sharing logic with the web. For most Magento stores, Hyvä is the right answer.
Does Hyvä support B2B?
Yes. Hyvä works with Magento B2B (Adobe Commerce B2B module): company accounts, requisition lists, quote workflow, shared catalogues, negotiable quotes, all render in the Hyvä storefront. Some B2B-specific UI (the requisition list page, the quote request form) needs Hyvä-native templates if your team has heavily customised the Luma B2B views; the Compat Module covers the unmodified default views. B2B stores often see the biggest performance lift from Hyvä because they tend to have heavy PLPs and large catalogues where every kilobyte of JavaScript hurts.
How long does Hyvä migration take?
Typical range is 4 to 12 weeks for an existing Luma store, depending on customisation depth and extension count. Lightly customised stores (mostly default Luma + 5-10 extensions) can land in 4-6 weeks. Mid-complexity stores (custom theme + 15-25 extensions + custom B2B flows) take 6-10 weeks. Heavy stores (deeply customised theme + 30+ extensions + bespoke checkout / configurator logic) take 10-12 weeks plus a phased cutover. Brand-new builds on Hyvä are faster because there is no Luma legacy to port: usually 3-6 weeks for a standard store.

Want a Hyvä audit on your Magento store?

Send your storefront URL: I will run a Lighthouse + extension-compat audit and reply with a written migration plan, fixed-price quote, and earliest start date. 24-business-hour turnaround.

Send a briefWhatsApp