commercetools Now Sells Core Commerce and Product Catalog as Standalone Modules: What That Means for…
Sylius Frontend Custom Build vs. Laioutr: Which Fits?
If you want to run Sylius headless, you have several frontend options. Unlike Shopify (Hydrogen) or commercetools (Frontastic), there's no official Sylius frontend product. The most common serious comparison question is therefore: custom build in Next.js or Nuxt, or a Frontend Management Platform like Laioutr.
Both work with Sylius Community and Plus. Both speak the Sylius API Platform. Both can do multi-channel and B2B. But they're built for different team setups, and that's why the decision is less a tech question than a team question.
This post compares the two along six dimensions and ends with a decision matrix.
What custom build is and what it is not
Custom build means: setting up a dedicated frontend project, typically with Next.js (React) or Nuxt (Vue), that talks to the Sylius API Platform. The team builds components from scratch, handles state management, integrates third-party systems, deploys themselves.
Custom build is the tool for mature engineering teams. If you have a seasoned React or Vue team with Symfony experience, you get maximum control. If you don't, you spend six to twelve months building a foundation that many FMPs already ship.
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 visual page builder (Studio), 70+ pre-built ecommerce components, themes, app integrations and globally distributed EU hosting.
Laioutr is a tool for cross-functional teams: marketing, design and engineering work on the same platform. Unlike a custom build, Laioutr is backend-agnostic, Sylius, Shopify, Shopware and other backends are equally supported.
Six comparison dimensions
1. Who can actually use it?
Custom build requires React or Vue knowledge plus Symfony and Sylius API understanding. 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
Custom build greenfield from zero to live typically takes six to twelve months, because everything is built in-house, from components to routing to hosting. With Laioutr and a theme, a first storefront ships in weeks.
3. Hosting and deployment
Custom build has to be hosted and deployed separately, typically on Vercel, AWS or own infrastructure. Laioutr Cloud is included in the plan, with global EU CDN distribution and automated deployment.
4. Backend flexibility
Custom build is typically built specifically for the Sylius API Platform. A later backend switch would require a major rebuild of the state layer and API integration. Laioutr is backend-agnostic, switching to Shopify, Shopware, commercetools or other backends means reconfiguring an API connection.
5. Performance and compliance
Custom build ships a good code baseline if the team does it right, but Lighthouse 100 performance, EU Accessibility Act compliance and WCAG 3.0 are own responsibility. Laioutr components target Lighthouse 100 and cover WCAG 3.0, EN 301 549 and BFSG out of the box.
6. Total cost of ownership
Custom build looks cheap because there are no license costs, but it costs a six- to twelve-month build phase plus ongoing maintenance by an internal team. Laioutr is SaaS with transparent plans, hosting, components and editor are bundled. TCO over 3 to 5 years is typically significantly below custom build. The full twelve-dimension table sits on our hub page.
Which team setup fits which solution?
Custom build is the right pick when …
- You have a dedicated React or Vue team with at least three engineers
- You have Symfony and Sylius API experience in-house
- You're building exactly one Sylius storefront, with no plan for multi-brand or backend changes
- You want to code every design decision yourself
- Frontend engineering is your strategic core competency
Classic use case: a DTC brand with an in-house engineering team that wants pixel-level control and treats the frontend as a competitive advantage.
Laioutr is the right pick when …
- Marketing should build pages independently
- You need weeks instead of months to go-live
- You serve multiple Sylius channels or brands
- You want backend optionality
- BFSG and WCAG 3.0 must be solved without a separate audit
- You don't have or don't want to build a dedicated React or Vue frontend team
Classic use case: a mid-market or enterprise Sylius store that needs to multiply marketing output without a six-figure engineering investment.
When does it make sense to switch from custom build to Laioutr?
We typically see the move in two situations:
First: when the React or Vue team that built the custom solution thins out or leaves the company. Suddenly the frontend has no owner, with high maintenance costs and documentation gaps.
Second: when the multi-brand or multi-market strategy becomes concrete and the monolithic custom build doesn't scale with it.
Bottom line: tooling follows team setup
The custom-build-vs.-Laioutr question is rarely a tech question. It's a team question. If you have the React or Vue team that builds and maintains a custom solution over years, take custom build, that's a valid strategy. If you don't have it, or don't want to build it, you'll be more predictable on an FMP.
If you're unsure, we'll run the comparison live against your Sylius setup, including a total cost of ownership calculation over 3 years.
Related resources: Composable Headless Frontend and Content Management.