Shopify and Vercel are rebuilding Hydrogen as an open, runtime-agnostic foundation. Hydrogen now dep…
Magento 2 headless vs. Hyvä: A decision guide for the DACH Mittelstand
When your Magento 2 shop's Luma theme sits at a 5-second mobile LCP, the frontend question is on the table. For many mid-market teams in DACH it boils down to two paths: migrate to Hyvä or decouple the frontend. This guide is not a philosophical debate but a practical walkthrough of how a small team actually decides.
The starting point is almost always the same: limited frontend capacity, a fixed budget, a marketing team that wants landing pages without an engineering ticket, and, since 2025, an accessibility obligation. That reality - not the theoretical ideal - decides which path holds up.
The mid-market starting point
A typical DACH mid-market shop does 5 to 100 million euros in online revenue, runs on Magento 2.4.7 or 2.4.8, and is looked after by an agency or a small in-house team. Magento frontend specialists are scarce, so any decision that permanently ties up your own capacity is strategic, not just technical.
Three factors dominate the choice: time-to-market (how fast does a modern frontend go live?), total cost of ownership (what does it cost over three years, not only at launch?), and compliance (accessibility under the BFSG and GDPR-compliant hosting). Teams that weigh only launch cost usually miscalculate on operations.
What Hyvä does well
Hyvä is a solid, community-driven answer to the Luma problem. Its Alpine.js and Tailwind stack delivers fast Core Web Vitals, stays tightly coupled to Magento, and is backed by more than 1000 compatible extensions. For teams with Magento know-how in-house that want to stay monolithic, it is a realistic, well-documented path.
The cost is effort and coupling. Depending on your custom-module stack, a Hyvä migration runs 6 weeks to 8 months, and the team needs Tailwind and Alpine skills to make custom modules and checkout tweaks compatible. You get exactly one theme, tightly interlocked with the Magento renderer, so every patch keeps the frontend inside the test-and-deploy cycle.
Where the decoupled path holds up
A decoupled frontend sits on the Magento GraphQL API and separates presentation from the backend renderer. The appeal for a lean team is not architectural elegance but the division of labour: Magento stays the commerce engine, and the frontend becomes a swappable layer.
The catch with classic do-it-yourself headless: a self-built frontend (say, with PWA Studio) permanently ties up exactly the frontend capacity the mid-market lacks. This is where an operated Frontend Management Platform (FMP) comes in. It delivers the decoupled frontend as a managed layer - Studio editor for marketing, accessibility out of the box, EU hosting - and takes the maintenance burden off the team. You consume the frontend layer as a service instead of building a frontend team.
The honest cost drivers (TCO)
Launch is rarely the expensive part. Over three years the effort comes from operations: patch testing, extension upkeep, frontend development, and recurring landing-page work.
With Hyvä you carry licence plus implementation (typically 30,000 to 150,000 euros), then ongoing frontend upkeep and a theme fork for every multi-brand presence. On the decoupled path via FMP the line item shifts: no frontend build, no separate theme forks, multi-brand on one UI library, in exchange for a subscription. The honest question: what share of your frontend cost is operations, not launch? For Magento shops that is typically 30 to 50 percent, exactly the part an operated layer consolidates.
Accessibility and GDPR: the DACH obligation
Since June 2025, the German Barrierefreiheitsstärkungsgesetz (BFSG) applies. For B2C shops, WCAG-conformant accessibility is no longer optional. The Luma theme is not conformant out of the box, and a theme migration does not close the accessibility gap automatically either - it needs its own audit-and-patch sprint of 4 to 8 weeks.
For a small team, that is real lost time. A frontend layer that ships accessibility out of the box takes that sprint off the plan. The same logic applies to hosting: GDPR-compliant EU hosting should be a default, not a configuration project. In DACH, both are hard selection criteria.
Decision checklist
Work through these six questions honestly. If the answers cluster on the right, that argues for the decoupled, operated path.
- Frontend capacity: Do you have a frontend team with Tailwind/Alpine skills (Hyvä), or is frontend capacity your bottleneck (FMP)?
- Time-to-market: Can you plan for a 6-to-8-month migration (Hyvä), or do you need a modern frontend in weeks (FMP)?
- Marketing autonomy: Is the limited page builder enough (Hyvä), or should marketing build landing pages without engineering (Studio editor)?
- Accessibility: Can you carry a separate accessibility sprint (Hyvä), or do you need it out of the box (FMP)?
- Multi-brand: One presence (Hyvä theme), or several brands on one UI library (FMP)?
- Replatforming optionality: Are you sure you will stay on Magento (Hyvä), or do you want to swap the backend later without rebuilding the frontend (decoupled)?
There is no universal answer. Hyvä fits teams with Magento frontend depth and a monolithic preference. The decoupled, operated path fits teams whose bottleneck is capacity, time-to-market, and compliance.
Next steps
Before you commit, run the three-year TCO calculation - operations, the accessibility sprint, and multi-brand upkeep included. If your bottleneck is frontend capacity, look at how an operated frontend layer for Magento 2 resolves the trilemma of Luma, Hyvä, and self-build.
More from the platform
Marcel Thiesies, Co-Founder at Laioutr
All data is based on publicly available information, insights from sales conversations with DACH e-commerce brands, and our own platform testing. As of July 2026. Hyvä and Magento features may have evolved since.