Map the automotive customer journey and you almost always get the same slide: awareness, research, c…
What Happened to Front-Commerce, Vue Storefront, and PWA Studio: The Magento Frontend Market in 2026
If you read a headless Magento guide in 2023, you almost certainly ran into the same three names: Front-Commerce, Vue Storefront, and Adobe PWA Studio. They anchored a conversation whose central question was simple: which frontend stack do you put in front of your Magento?
Three years on, none of the three is what it was. Two have moved from being a Magento frontend to being a backend-agnostic operating model, and one has moved into the second row at Adobe. This retrospective walks through each trajectory and ends on the question that matters more in 2026 than the stack choice did back then.
The starting point in 2023
The situation was the same for every Magento team: the Luma theme delivered structurally weak Core Web Vitals on mobile, and the question was what to replace it with. The answers fell into three camps. Front-Commerce as a commercial PWA frontend layer with a Magento focus. Vue Storefront as an open-source storefront starter with a large community. PWA Studio as Adobe's own React stack, the option with the vendor's seal on it.
All three were debated as frontend technology: React or Vue, which component base, how mature the GraphQL binding was. The vocabulary of that debate was stack vocabulary.
Front-Commerce: from Magento PWA layer to frontend service
Front-Commerce is an active company and today positions itself on its own homepage as frontend-as-a-service for eCommerce. The meaningful change since 2023 is not technical, it is the order of the arguments. Magento no longer leads. It appears as one of several supported backends alongside Salesforce Commerce Cloud, BigCommerce, commercetools, and Shopify. The dedicated Magento page still exists, but it is one entry point among several rather than the main story.
A "frontend for Magento" has become a "frontend for your commerce stack," with Magento as one connection. That says something about the market: a vendor perceived in 2023 as a Magento specialist now builds its business on backend independence.
Vue Storefront became Alokai
The most visible change of the three: Vue Storefront renamed itself Alokai in March 2024. Its own reasoning was explicit, that the product had outgrown the original Vue.js starter kit. React is supported on equal footing, and a framework name in the company name no longer matched the portfolio.
What runs under that name today is broader than a storefront project: a pre-built storefront with a backend-agnostic data layer, an orchestration layer between frontend, commerce backend, and third-party systems, managed hosting, and a monitoring dashboard. Compass was added on top, a storefront agent that handles product discovery and comparison inside the storefront UI. The self-description is also frontend as a service, the same category language Front-Commerce uses.
For Magento teams, the relevant observation is where the center of gravity sits: enterprise composable stacks. Magento connects, but it is not the audience the product is narrated around today.
PWA Studio: from Adobe's answer to the second row
The third trajectory is the clearest. PWA Studio has not been discontinued and still receives maintenance, but Adobe's storefront narrative for new projects now runs through Edge Delivery Services. New feature development happens there, not in the 2023 React stack.
That matches what we see in the DACH market: PWA Studio's community momentum has declined noticeably since 2024, while Hyvä, on Alpine.js and Tailwind, has become the de facto performance standard for Magento themes, with broad extension compatibility behind it. Teams that picked PWA Studio in 2023 are running a stack that works but is no longer the direction the vendor points to. We took the Adobe options apart in detail in Adobe Headless in 2026: Edge Delivery, PWA Studio, Custom Headless, or an FMP.
The pattern behind the three
Three vendors, three different routes, one shared pattern in three parts.
First, the category shifted from "frontend stack" to "operating model for the frontend." Neither Front-Commerce nor Alokai sells a framework starter anymore. Both sell a service that includes hosting, integrations, updates, and operations. That shift is exactly what the term Frontend as a Service describes, and the fact that two former stack vendors landed there independently is the strongest signal in this retrospective.
Second, backend specialization has moved out of the business model. The vendor most closely identified with Magento in 2023 now lists Magento among others. Anyone selling the frontend layer in 2026 sells it backend-agnostic, because a frontend investment tied to exactly one backend is concentration risk for the buyer.
Third, the vendor's own answer is not a safe bet. PWA Studio had the strongest argument of the three in 2023, namely that it came from the platform vendor. Three years later that is the argument worth the least, because the vendor's strategy moved. This is not a criticism of Adobe, it is the normal motion of a product portfolio. For a merchant's frontend planning it is still the most expensive of the three paths if you did not plan for it.
What this means for Magento teams in 2026
The 2023 question was: which frontend stack fits our Magento? The question this retrospective points to is: how much of our frontend investment survives a change of direction we do not control?
That covers three changes at once. The platform vendor can move its storefront strategy, see PWA Studio. The frontend vendor can move its focus, see Alokai's shift in target audience. And your own company can change the backend, which comes up regularly across the Magento base given version end-of-life pressure and B2B requirements.
In all three cases, the same thing decides how expensive the change gets: whether the frontend hangs off a theme's rendering engine, off a framework starter, or off an API contract. For a stocktake of the options available today and the terms attached to them, What Is a Magento Frontend? is the right entry point.
Our take
The most honest sentence about these three years is that the market changed the question rather than improving the answer. The 2023 technology debate, React versus Vue versus Luma, is largely settled. What remains is an operating question, which is precisely why the category two of the three vendors now place themselves in is called frontend as a service.
Laioutr sits in the same movement with a different emphasis: we build the frontend layer as a management layer, where marketing and engineering work on the same component base, and we connect Magento through its GraphQL API rather than through the theme layer. A Composable Headless Frontend built that way survives a theme change and a backend change, because its contract is the API. If you want to keep frontend quality measurable while you do it, the criteria live under Performance and Core Web Vitals, and the Magento-specific path is covered on Headless Frontend for Magento 2.
Frequently asked questions
Can I still use Front-Commerce or Alokai for Magento in 2026? Yes. Both continue to support Magento. What changed is not technical feasibility but priority: for both vendors, Magento is one backend among several rather than the focus the product is planned around. That matters for roadmap questions and support expectations.
Do I have to move off PWA Studio? Not in the short term. Maintenance and compatibility updates continue. The planning question is different: if you have substantial frontend work ahead in the next 24 months anyway, you should not invest it into a stack where the vendor's feature development no longer happens.
Does that make Hyvä the safe path? Hyvä is the current performance standard for Magento themes and a solid choice if the storefront is going to stay a Magento theme. The coupling stays a theme coupling, though: a backend change or a second backend in the portfolio puts the frontend back on the table. That is exactly the case a decoupled frontend layer addresses.
What is the difference between frontend as a service and a frontend management platform? Frontend as a service describes the operating model: the frontend arrives as a service including hosting, integrations, and updates, instead of a project you build and run yourself. A frontend management platform describes what sits inside that service: a layer where marketing and engineering operate the same component base, not just a delivery tier.
Next steps
If you are running a frontend decision from the 2023 wave and re-evaluating it, book a 30-minute demo. We will walk through your current stack and show which part of it would survive a theme or backend change.
More from the Laioutr platform
About the author: Marcel Thiesies is Co-Founder of Laioutr and works with Magento teams on frontend decisions meant to outlast a vendor roadmap.