Hyvä Development for Magento 2
I build and migrate Magento 2 frontends with Hyvä. Not as one service among twenty. It is most of what I do, every week, on shops that take real orders.
I’m an independent Magento developer based in Tyrol, Austria, building online shops since 1999 and specialized in Hyvä, working with merchants across the DACH region and beyond. You work directly with me. There is no project manager, no junior bench, no handover document that loses half the context.
Book a call or send me the problem.
Why merchants move to Hyvä
Luma, Magento’s default frontend, was built in 2015 on technology that was already dated then. Every Luma shop carries the same baggage: RequireJS, Knockout, layered JavaScript that makes mobile pages slow no matter how much you optimize around it.
Hyvä replaces that stack with Tailwind CSS and Alpine.js. Less JavaScript, fewer requests, pages that pass Core Web Vitals without tricks. The difference isn’t cosmetic. Load time is revenue. I’ve written up the actual math: for a shop doing €300k a year, a slow mobile frontend costs €30,000 to €50,000 annually.
If you’re weighing the decision, read Hyvä vs Luma first. Short version: in 2026, new builds on Luma are technical debt from day one.
What I do
Luma to Hyvä migration. The full path: theme audit, module compatibility map, child theme setup, template migration, checkout, testing, launch. Migrations run alongside your live shop. The old frontend keeps selling until the new one is ready.
New Hyvä builds. Magento 2 projects that start on Hyvä from the first commit. Tailwind design tokens, Alpine components, CMS components your content team can actually use.
Hyvä Checkout. Implementation and customization, including payment integrations. I maintain a public fix for the Mollie + Hyvä Checkout redirect problem because I hit it in production before there was an answer to google.
Module compatibility. Third-party modules that ship without Hyvä support: I make them work. Strategic decision included. Port, replace, or drop. Many modules turn out to be solving problems Hyvä no longer has.
Ongoing development. For shops already on Hyvä: features, performance work, upgrades, and the unglamorous maintenance that keeps a storefront fast two years after launch.
Production work, not demos
My first Hyvä migration shipped in November 2020, with the agency Diglin in Zürich, for a computer supplier. Since then:
Kaufhaus der Berge. Multi-store Magento 2.4.7 shop (DE/EN/IT) on Hyvä: custom checkout with Mollie, Akeneo PIM integration, configurable product UX, GraphQL extensions. Ongoing development partner.
Multi-locale catalog migration. Luma to Hyvä on a catalog-heavy shop: child theme architecture, translation workflows across five locales, Playwright end-to-end test suite covering the critical purchase paths.
Open source. My Hyvä Cookie Consent module, GDPR-compliant consent with Google Consent Mode v2, CSP- and FPC-compatible, is publicly available and in use beyond my own projects. When I fix something generic, it goes on GitHub.
How I work
One developer, senior level, no overhead. You get my read on architecture decisions, my code, and my availability. Not a rotating team. Everything runs through version control, PHPStan, and automated tests before it touches your shop. I write down what I do and why, so you’re never locked in.
What I don’t do: design from a blank page, marketing campaigns, or full-service agency packages. If you need those, I’ll tell you, and I can usually point you to someone good.
I’m based in Itter, Tyrol. Most work is remote. For DACH clients I’m in your timezone, and on-site is an option when it actually helps.
Not sure where to start?
Hyvä Migration Assessment. A fixed-scope starting point: I audit your current theme and module stack, map every extension to port, replace, or drop, and give you a realistic effort estimate for the migration. You get a written report you can act on, with me or with anyone else.
Fixed price: €1,950. If you proceed with the migration with me within three months, the full amount is credited against the project.
Frequently asked questions
What does a Hyvä migration cost? It depends on the module stack more than the design. A shop with 15 well-chosen extensions migrates for a fraction of what a shop with 60 accumulated ones costs. That is exactly what the assessment answers, with numbers, before you commit to anything.
How long does a migration take? Three to six months for a typical shop, depending on what’s involved. The module stack and the amount of custom frontend work drive the difference. The shop stays live on Luma throughout. There is no downtime cutover.
Will my existing modules work with Hyvä? Some will, some need a compatibility layer, some should be replaced. The Hyvä ecosystem now covers most common needs natively, and a migration is the best moment to drop dead weight.
Is Hyvä worth it for a small shop? Usually yes, sometimes no. If your traffic is tiny and your shop earns little, the migration won’t pay for itself quickly. I’ll tell you that in the assessment rather than sell you a project.
Do you only work with clients in Austria? No. Most of my work is remote across DACH and Europe. Tyrol is where I am, not a service boundary.
Working with agencies: I also take Hyvä implementation work as a subcontractor, white-label or named. Get in touch.