SCAYLE is headless by design, so the frontend is a deliberate decision rather than a default. Teams building on SCAYLE typically weigh three paths: build on the SCAYLE Storefront SDK with your own Nuxt team, build a fully custom frontend on the Storefront API, or put a Frontend Management Platform (FMP) like Laioutr on top. Here is the honest comparison.

The starting point: SCAYLE is MACH and API-first

SCAYLE, the commerce engine built by ABOUT YOU and backed by Zalando, follows MACH principles: microservices, API-first, cloud-native and headless. The frontend talks to the backend through the REST Storefront API, which serves products, categories, campaigns, promotions, baskets and wishlists. Built-in PIM, checkout and order management stay in SCAYLE. The frontend layer is genuinely yours to choose.

Option 1: Build on the SCAYLE Storefront SDK

SCAYLE ships a Nuxt-based Storefront SDK: composables, an API layer and utilities for products, cart and authentication, plus caching, sessions and CMS hooks. It is the natural choice if you have a Nuxt engineering team.

The trade-off is that the SDK provides building blocks, not finished UI. You still design, build and maintain the component library, the page templates, performance budgets and accessibility yourself.

Option 2: Fully custom build on the Storefront API

A bespoke frontend on the REST Storefront API gives maximum control. The cost is a multi-month build, a dedicated frontend team and permanent ownership of hosting, upgrades, Core Web Vitals and accessibility. Sensible only when frontend engineering is a strategic core capability.

Option 3: Laioutr FMP on the SCAYLE Storefront API

Laioutr sits as a frontend layer on the existing Storefront API. The SCAYLE backend stays untouched. You get a visual editor, more than 70 prebuilt commerce components, EU hosting and a Lighthouse 100 target. Because Laioutr itself is built on Nuxt, it sits naturally alongside the SCAYLE stack.

The advantage is speed and predictability: no multi-month build, no component library to maintain, and marketing teams compose pages and campaigns without engineering tickets. WCAG 3.0 and BFSG are part of the platform baseline.

Side-by-side

• Time-to-launch: Storefront SDK = months of Nuxt work; Custom build = several months; Laioutr = weeks
• Year-1 TCO: SDK and Custom = engineering-heavy; Laioutr = predictable subscription
• Maintenance: SDK and Custom = your team; Laioutr = platform-operated
• Accessibility: SDK and Custom = your responsibility; Laioutr = WCAG 3.0 and BFSG in the standard
• Backend optionality: Custom = locked to SCAYLE; Laioutr = backend-agnostic across SCAYLE, commercetools, Shopify and more

When each option wins

The Storefront SDK or a custom build wins when you have a strong Nuxt or JavaScript team and pixel-level control is a strategic priority. Laioutr wins when you want weeks to go-live, marketing autonomy, built-in EU compliance and the freedom to keep backend options open.

FAQ

Does Laioutr replace the SCAYLE Storefront SDK?

It is an alternative frontend layer on the same Storefront API. You can build on the SDK, or use Laioutr instead for faster time-to-launch and no-code page composition.

Does the SCAYLE backend change?

No. Laioutr consumes the REST Storefront API. PIM, checkout, pricing and order management stay in SCAYLE.

How does pricing compare to building it ourselves?

Total cost of ownership is typically lower because hosting, components and the editor are included, and no separate frontend team is required. See pricing or book a strategy call.