No. Laioutr is explicitly built as a frontend layer for Hygraph brands. Your engineering and editorial teams keep working in Hygraph (schema builder, mutations, federation, releases, Studio). Laioutr handles rendering in the e-commerce storefront. Both systems stay in their respective roles and complement each other.

Laioutr connects natively to the Hygraph Content API via GraphQL. Schemas, references, federated sources, and asset service URLs are available in Laioutr Studio as content sources. Your marketing and editorial teams can embed Hygraph content directly into Laioutr layouts, including live preview and stage-specific content stages.

Hygraph Studio is optimized for schema modeling and content editing: schema builder, references, federated data sources, field-level permissions. Laioutr Studio is optimized for storefront composition: themes, page templates, product pages, and campaign layouts with embedded commerce components and native backend integrations. In practice, a brand team works in both tools, because they solve different jobs.

Hygraph alone is enough for setups where your engineering team builds and operates a custom frontend itself and where the GraphQL federation is the central value. Laioutr complements Hygraph when you (1) want a productive e-commerce storefront in weeks instead of months, (2) need native connectivity to commerce backends like Shopify, Shopware, commercetools, or Adobe Commerce as the render layer, or (3) want marketing teams to roll out storefront pages without a dev ticket.

Content Federation stays the core of your Hygraph investment. Federated sources are consumed in Laioutr just like native Hygraph content: via the GraphQL API. Laioutr rounds out the picture with the render layer and the native commerce backend integrations needed for storefront delivery (for example, cart, checkout, and real-time inventory).

Setups with an existing Hygraph account and an established backend (Shopify, Shopware, commercetools, Adobe Commerce) typically go productive with Laioutr in four to six weeks. The Hygraph content flows directly into the storefront via the native GraphQL connection, and the custom frontend build falls away entirely.

As a rule, no. Hygraph models are bound in Laioutr layouts as content components. In the migration workshop, we assess which models map 1:1 to Laioutr sections and which need small adjustments to render cleanly in storefront templates.

Reusable components, design tokens, and style guides can be carried over via the Laioutr UI library. Laioutr takes over the render logic itself, and the custom frontend stack can be scaled back or reduced to pure GraphQL consumers. Custom logic either moves into Laioutr layouts or as an app into the Laioutr App Store.

Both platforms come from Germany, host in the EU, and are GDPR-compliant. Laioutr hosts on Laioutr Cloud (EU, Frankfurt), on Vercel, or in your own hosting environment, as you prefer. Both systems provide a DPA. WCAG 3.0 Ready on the frontend layer is a Laioutr commitment, because Hygraph delegates delivery to the frontend.

Both systems are licensed separately: Hygraph according to your plans (Hobby, Growth, Scale, Enterprise), Laioutr according to Growth, Pro, or Enterprise. In the combined setup, you save the custom frontend build and the ongoing engineering costs for an in-house frontend, which is usually the biggest lever for Total Cost of Ownership.

Yes. Our onboarding is set up for Hygraph brands. An architecture workshop, mapping your Hygraph models and federated sources to Laioutr sections, a migration plan for the old custom frontend, and hands-on guidance through to go-live are standard.