Frontend options for Hygraph: starter, custom build or page builder

Hygraph is a headless CMS: GraphQL-native, with content federation across sources. It delivers content through its GraphQL-native content API, but it does not ship a finished, production-ready frontend. Building that frontend is a separate decision, and a visual page builder is one of the routes for Hygraph.

What Hygraph gives you

Hygraph manages your content model, editorial workflow and localization, and exposes everything through its GraphQL-native content API. What it does not give you is a ready storefront: layout, components and page logic are yours to build.

The frontend question

Every Hygraph project faces the same choice. Four options are established:

• Official starter or example: great to learn, you keep building the production frontend
• Community framework: active, but no official product and no enterprise support net
• Custom build (Next.js or Nuxt): full control, six to twelve months plus maintenance
• Visual page builder: components, hosting and a visual editor in the platform, live in weeks

Laioutr as the frontend layer for Hygraph

Laioutr reads your Hygraph content through its GraphQL-native content API and renders it as a fast frontend, with 70+ components, EU hosting and Core Web Vitals by default. Hygraph stays your content backend; Laioutr delivers the frontend. The same pattern works across CMS platforms, see for example the Page Builder for TYPO3.

FAQ

Does Laioutr replace Hygraph? No. Hygraph stays the content backend; Laioutr is the frontend layer on top.

How does Laioutr connect to Hygraph? Through its GraphQL-native content API, plus project-specific queries for custom logic.

More on the category: what a Frontend Management Platform is, or the Laioutr home page.