Shopware Frontends vs. Laioutr: Which Frontend Is Right?
If you want to run Shopware headless, you have two main paths: Shopware Frontends — Shopware's official open-source headless frontend project on Nuxt 3 — or a Frontend Management Platform like Laioutr. Both work with Shopware. Both have their place. But they're built for different teams, and that's why the decision is less a technology question and more a team question.
This post compares the two along six dimensions and ends with a decision matrix.
What Shopware Frontends is and what it is not
Shopware Frontends is Shopware's official open-source headless frontend project, built on Nuxt 3 / Vue 3, with a collection of composables that engineers use to connect to the Shopware Store API. Deployment runs on Vercel, Netlify, your own infrastructure or comparable hosting platforms.
Frontends is a tool for Vue/Nuxt engineers. If you write code, you get a solid foundation. If you don't write code, you get nothing.
What Laioutr is and what it is not
Laioutr is a Frontend Management Platform not a library, not a framework, but a complete platform with a visual page builder (Studio), 70+ pre-built ecommerce components, themes, app integrations and globally distributed EU hosting. A storefront is a configuration of components, not a stack of code files and engineers can still extend at the code level when they need to.
Laioutr is a tool for cross-functional teams: marketing, design and engineering work on the same platform. And unlike Frontends, Laioutr isn't tied to Shopware, Shopify, commercetools and other backends are equally supported.
Six comparison dimensions
1. Who can actually use it?
Frontends requires Vue 3 and Nuxt 3 knowledge, plus understanding of composables and API state management. Marketing teams are out. Laioutr targets marketing and design teams just as much as engineering through the visual builder as well as the code API.
2. Time-to-launch
A Shopware Frontends storefront from zero to live takes months in practice, because everything is built code-first. With Laioutr and one of our themes, a first storefront ships in weeks, depending on branding depth.
3. Hosting and deployment
Frontends has to be hosted and deployed separately Vercel, Netlify, your own server or own infrastructure. Laioutr Cloud is included in the plan, with global EU CDN distribution and automated deployment.
4. Platform lock-in
Frontends only works with Shopware as the backend. If you ever consider switching backends, you'd rebuild the frontend from scratch. Laioutr is backend-agnostic Shopware, Shopify, commercetools and others all work, and the frontend stays the same.
5. Performance and EU compliance
Frontends ships a good code baseline, but Lighthouse 100 performance, EU Accessibility Act compliance and WCAG 3.0 are the team's responsibility. Laioutr components target Lighthouse 100 by design and cover WCAG 3.0, EN 301 549 and Germany's BFSG out of the box directly relevant for any store selling into the EU after 2025.
6. Pricing model
Frontends itself is open source and free of license cost — costs come from around it: engineering capacity, hosting setup, component build-out, ongoing maintenance. Laioutr is SaaS with transparent plans; hosting, components and editor are included. The full ten-dimension table sits on our Headless for Shopware hub page.
Which team fits which solution?
Shopware Frontends is the right pick when …
- Your team has at least three Vue/Nuxt engineers
- You're building exactly one Shopware storefront, with no plan for multi-brand or backend changes
- You want to code every design decision yourself
- Platform lock-in to Shopware is strategically fine for you
Classic use case: a DTC brand with an in-house engineering team that wants pixel-level control over everything and treats the open-source nature as a strategic advantage.
Laioutr is the right pick when …
- Marketing should build pages independently
- You need to ship fast weeks, not months
- You're serving more than one brand or market
- You want to keep backend flexibility open
- You need to launch BFSG / WCAG 3.0 compliant without running a separate accessibility audit
Classic use case: a mid-market or enterprise Shopware store that needs to multiply marketing output without doubling the engineering team.
When does it make sense to switch from Frontends to Laioutr?
We typically see the move in two situations:
First when the Vue team that originally built the Frontends storefront thins out or leaves the company. Suddenly the frontend has no owner. With Laioutr, marketing and design teams take over day-to-day operations.
Second when the multi-market or multi-brand strategy becomes concrete and the greenfield Frontends build doesn't scale with it.
Bottom line: tooling follows team setup
Frontends vs. Laioutr is rarely a tech question. It's a team question. If you have the team Frontends demands, take Frontends Frontends is a solid open-source project. If you don't have it or don't want to build it, you'll move faster, more predictably and with less risk on a Frontend Management Platform.
If you're not sure which scenario applies to you, let's talk. We'll run the comparison live against your actual setup including an honest recommendation if Frontends turns out to be the better path.
