The Hyvä Alternative for Non-Magento Backends

You looked at Hyvä, liked what you saw, and then hit the one line that ends the evaluation: it only runs on Magento. If your backend is Shopware, commercetools, or anything else, Hyvä is not an option, and the question shifts. You are no longer asking "which Magento theme," you are asking "what gives me a Hyvä-class frontend when Magento is not in the picture." This post answers that directly.

What Hyvä actually is

Hyvä is a modern theme for Magento 2 and Adobe Commerce. It replaces the heavy default Luma frontend with a leaner stack built on Tailwind CSS and Alpine.js, strips out most of the legacy JavaScript, and gives Magento shops much better Core Web Vitals and a saner developer experience. For a team that is staying on Magento, it is a strong, well-supported choice, and we say that plainly.

The important detail for you is architectural: Hyvä is a theme inside Magento. It renders through Magento's PHP layer and is coupled to Magento's templating and module system. That coupling is exactly why it performs well on Magento, and exactly why it does not travel. There is no Hyvä for Shopware and no Hyvä for commercetools, because a Magento theme is not a portable frontend.

What you were really evaluating

Strip away the Magento part and look at what attracted you to Hyvä in the first place. It was a short list: a fast storefront with good Core Web Vitals, a modern component-based build instead of legacy template sprawl, and a frontend a team can actually work in without fighting the platform. None of those qualities are Magento-specific. They are properties of a well-built frontend layer, and they are available regardless of which commerce backend you run.

That reframing matters, because it means the answer for a non-Magento shop is not "find a theme like Hyvä for my platform." It is "decouple the frontend from the backend, and run a modern frontend layer on top of whatever commerce engine you already have."

The equivalent when your backend is not Magento

A composable, headless frontend gives you the qualities you wanted from Hyvä without tying them to a single backend. Instead of a theme living inside the commerce platform, the frontend becomes its own layer, talking to the backend over its API. Laioutr's Frontend Management is that layer: one modern storefront that connects to Shopware, commercetools, Adobe Commerce, Magento, and 50+ other backends, without you replatforming the commerce engine underneath.

Concretely, that means the things Hyvä gives Magento shops are delivered here as platform properties, not as a per-backend port:

• Core Web Vitals built into the layer, not bolted on. Median LCP across live Laioutr frontends is 1.2 seconds (Q2 2026 field data).
• A component library and content model that marketers and developers share, so page changes do not require a backend release.
• WCAG 3.0-ready components and EU hosting with a DPA available by default.

• Which backends?. Hyvä: Magento 2 / Adobe Commerce only. Decoupled frontend with Laioutr: Shopware, commercetools, Adobe Commerce, Magento, 50+.
• Where does the frontend live?. Hyvä: Theme inside Magento's PHP layer. Decoupled frontend with Laioutr: Its own layer, connected over the backend API.
• Multi-backend or multi-brand?. Hyvä: Single Magento store. Decoupled frontend with Laioutr: Multiple backends and brands from one frontend.
• Marketer editing. Hyvä: Via Magento admin and dev tickets. Decoupled frontend with Laioutr: Visual editing in a shared component model.
• Replatform the backend to adopt it?. Hyvä: N/A (you are already on Magento). Decoupled frontend with Laioutr: No, the backend stays where it is.

What this looks like on Shopware and commercetools

If you are on Shopware, the frontend connects through Shopware's Store API, and you get a modern storefront without waiting on the Shopware template layer or a full headless rebuild. The details of that pairing live on our Shopware frontend page.

If you are on commercetools, you already have an API-first backend with no first-party frontend by design, which is precisely the gap a frontend layer fills. Laioutr talks to the commercetools API directly and gives you the storefront that composable stack was always meant to have. See the commercetools frontend page for how that fits together.

In both cases the pattern is the same one that made Hyvä attractive: a fast, modern, maintainable frontend. The difference is that it is not welded to one backend.

What you keep and what you gain

You keep the outcome you were chasing: a quick, clean storefront that hits Core Web Vitals and that your team can iterate on. You gain backend independence. Because the frontend is a separate layer, a future backend change does not force a frontend rebuild, and one frontend can serve several backends or brands at once. That last point is the scenario we go deep on in when Hyvä is not enough for multi-backend and multi-brand, and if you want the head-to-head framing for Magento teams specifically, Hyvä vs. headless vs. FMP lays out the trade-offs.

This operating model is what we mean by Frontend as a Service: the frontend is hosted, operable, and portable, on top of whatever commerce backend you already run.

Getting started

1. Confirm your backend exposes an API (Shopware Store API, commercetools API, and so on). Almost all modern backends do.
2. Map the storefront surfaces you care about first: home, PLP, PDP, and content pages.
3. Connect Laioutr to the backend and compose those pages from the existing component library, no theme fork required.
4. Measure Core Web Vitals against your current frontend before you switch traffic.

FAQ

Is there a version of Hyvä for Shopware or commercetools? No. Hyvä is a Magento theme and does not exist for other backends. The equivalent for a non-Magento shop is a decoupled frontend layer that connects to your backend over its API.

Do I have to replatform my backend to get a modern frontend? No. A decoupled frontend runs on top of your current backend. Your commerce engine, data, and integrations stay where they are.

Will I get the same Core Web Vitals Hyvä is known for? Yes, and independent of backend. Performance is a property of the frontend layer here, with a median LCP of 1.2 seconds across live Laioutr frontends.

We are on Magento today. Is this still relevant? Yes, especially if you run more than one backend or brand, or expect to change backends later. A decoupled frontend keeps that option open.

Next step

Want to see a Hyvä-class frontend running on your backend? Talk to the Laioutr team and we will map the first storefront surface together.