---
title: "Page Builder for Sulu: Build Pages Visually | Laioutr"
canonical_url: "https://www.laioutr.com/en/page-builder-sulu-io"
locale: en
meta:
description: "Page builder for Sulu: Laioutr adds a visual editor and fast frontend to Sulu content. No Twig templating, accessible and GDPR-compliant."
"og:description": "Page builder for Sulu: Laioutr adds a visual editor and fast frontend to Sulu content. No Twig templating, accessible and GDPR-compliant."
"og:title": "Page Builder for Sulu: Build Pages Visually | Laioutr"
---
Sulu x Laioutr
# Page builder for Sulu: visual editor and fast frontend
Visual page building without Twig templating for every page
More speed and creative freedom for Sulu websites: Sulu stays the CMS, Laioutr delivers the page builder and frontend.
[Request a demo](https://www.laioutr.com/en/contact)
Partners support the implementation of Sulu frontends with Laioutr.
[](https://www.bestit.de/ "Best it") [](https://www.datrycs.com/ "datrycs") [](https://www.valantic.com/ "valantic")
5/5
OMR Reviews
70+
Frontend components
Lighthouse 100
Performance from day one
Made in EU
GDPR-compliant by default, EU hosting available
PAGE BUILDER FOR SULU
## What a page builder for Sulu does
Sulu is a powerful enterprise CMS built on Symfony: content, editorial workflows, permissions, webspaces (multi-site) and multilingual capabilities are its strengths. What is often missing is a modern, visual frontend that marketing and editorial teams can operate without Twig templating. This is where Laioutr comes in: as a visual page builder and frontend layer that reads Sulu content via the content API (SuluHeadlessBundle) and delivers it as a fast website. Sulu remains the leading system, Laioutr delivers the frontend. Laioutr is also an integrated headless CMS in its own right: content collections, Studio and frontend in one platform, for example for campaign content that should not live in Sulu.
[Book a strategy call](https://www.laioutr.com/en/contact)
### 1. The backend stays Sulu
Sulu continues to manage content, pages, snippets, permissions, editorial workflows, webspaces and translations. The Sulu admin and established processes stay unchanged, with all bundles and workflows.
### 2. Choose the frontend option
There are several options for the frontend: classic Twig templates, a headless setup (SuluHeadlessBundle) with a separate frontend, a custom build or a page builder like Laioutr. Each option has its pros and cons.
### 3. Content flows through the content API in real time
No data duplication, no sync conflicts. Laioutr reads Sulu content via the headless/content API (JSON) and renders it, including multilingual content and webspaces.
FRONTEND OPTIONS
## Which frontend options are there for Sulu?
With Twig, the Symfony foundation and the SuluHeadlessBundle, Sulu provides the building blocks, but no ready-made frontend product that non-developers can operate visually. That raises the frontend question in every Sulu project. Four options are well established.
[Book a strategy call](https://www.laioutr.com/en/contact)
### 1. Twig templates (classic)
The classic Sulu route: templates in Twig, configuration via Symfony. Full integration, but every layout change goes through development. A good fit for stable pages with rare changes or teams with deep Symfony expertise.
### 2. Sulu Headless (SuluHeadlessBundle) with a separate frontend
The headless bundle exposes Sulu content as a JSON API. The decoupled frontend is built in-house: maximum freedom, but the design system, components and maintenance stay with the internal team. A good fit with a suitable frontend team.
### 3. Custom build (Next.js or Nuxt)
Maximum control, highest effort: a six- to twelve-month build phase and ongoing maintenance by an in-house frontend team that connects the Sulu content API itself. A good fit when frontend engineering is a strategic core competency.
### 4. Laioutr Page Builder
Visual page builder and frontend platform with 70+ components and a Sulu connection, with EU cloud hosting available as an add-on. Fast time-to-launch, gentle learning curve, marketing and editorial teams build pages themselves. A good fit for a fast go-live without investing in a custom build.
USE CASES
## Use cases: Laioutr on Sulu
Laioutr is designed for Sulu setups that need to change and scale fast: from corporate websites to multi-webspace portfolios and campaign landing pages with high editorial volume.
[Book a strategy call](https://www.laioutr.com/en/contact)
### Multi-webspace and multi-domain on one Sulu
Sulu is strong at webspaces: several websites, brands and domains from one instance. Laioutr turns them into standalone frontends: one component pool, many brand presences, each with its own design.
### Campaign and landing pages without a ticket
Marketing builds landing pages visually from ready-made building blocks, without a Twig template and without a developer ticket. Content comes from Sulu, the layout is created in the page builder.
### Multilingual websites
Sulu manages translations and language versions, Laioutr delivers them consistently. Languages, layouts and content can be controlled per webspace and are compatible with the Sulu language concept.
### Content-driven sites and large-scale editorial work
Sulu manages structured content, snippets and editorial processes. Laioutr delivers them as a fast frontend, a good fit for content-heavy sites with many editors.
### Relaunch without touching the backend configuration
Renewing an existing Sulu frontend without touching webspaces, permissions or editorial processes. Phased migration with a clear rollback plan.
### New Sulu projects live fast
New Sulu project, fresh start. With Blueprints, Themes and the UI library, the project goes live in weeks instead of months of custom development.
LAIOUTR OR CUSTOM BUILD
## Page builder for Sulu or custom build: the comparison
Both routes lead to a decoupled frontend on Sulu. A custom build (Next.js or Nuxt on the Sulu API) offers maximum control but requires a six- to twelve-month build phase and ongoing maintenance. Laioutr delivers Studio and 70+ components, with full code extensibility for special cases; Cloud/Edge Hosting is available as an add-on. The difference lies in time-to-launch, maintenance load and who can build pages.
Pricing Plans Comparison
| Compare differences | Laioutr Page Builder | Eigenentwicklung (Next.js / Nuxt) |
| --- | --- | --- |
| Laioutr Page Builder Eigenentwicklung (Next.js / Nuxt) |
| Builder und Komponenten Was ab Werk enthalten ist und was selbst aufgebaut werden muss. |
| Visueller Page Builder Drag-and-drop-Editor für Marketing- und Redaktions-Teams. | Enthalten (Studio) Live-Vorschau, komponentenbasiert | Nicht enthalten Eigenbau oder externes Tool |
| Frontend-Komponenten Vorgefertigte UI-Bausteine für Seiten, Landing- und Content-Pages. | 70+ Komponenten Design-Token-basiert, anpassbar | Selbst aufbauen Komplette UI-Bibliothek selbst entwickeln |
| Blueprints und Themes Startpunkt für neue Websites ohne Greenfield-Aufwand. | Blueprints und Themes Start-Sites je Branche plus Design-Themes, voll erweiterbar | Greenfield Designsystem komplett selbst aufbauen |
| Hosting Wo das Frontend ausgeliefert wird und wer es betreibt. | Add-on: Cloud/Edge Hosting EU-Hosting verfügbar, kein separater Deploy | Selbst hosten Vercel, AWS, eigene Infrastruktur |
| Architektur und Compliance Wie flexibel die Plattform ist und was regulatorisch abgedeckt ist. |
| Backend-Flexibilität Welche CMS- und Commerce-Backends sich anbinden lassen. | Multi-Backend Sulu, weitere CMS und Commerce-Systeme | Backend-spezifisch Code an die Sulu-Content-API gebunden, Wechsel teuer |
| Performance und Core Web Vitals Wie viel Aufwand für Lighthouse-100-Niveau nötig ist. | Ab Werk Lighthouse 100 als Zielwert | Manuelles Tuning Performance-Engineering durch das Team |
| BFSG und WCAG 3.0 Konformität mit Barrierefreiheitsstärkungsgesetz und WCAG 3.0. | Im Standard WCAG 3.0, BFSG, EN 301 549 | Eigenverantwortung Audit separat erforderlich |
| Datenschutz und Hosting-Region Wo Daten verarbeitet werden und welche EU-Verträge gelten. | DSGVO-konform ab Werk EU-Hosting verfügbar, EU-Standardvertrag, deutschsprachiger Support | Hosting-abhängig Abhängig vom gewählten Hosting |
| Team und Wirtschaftlichkeit Wer mit der Plattform produktiv ist und was sie über die Zeit kostet. |
| Lernkurve Wie schnell ein neues Teammitglied produktiv wird. | Niedrig Redaktion ist in Tagen eingearbeitet | Hoch Twig/Symfony bzw. React/Vue plus Sulu-Content-API |
| Time-to-Launch Realistische Zeitspanne bis zum Live-Gang einer neuen Website. | Pilot in 14 Tagen Pilot meist innerhalb von 14 Tagen live, Migration im Median unter 14 Tagen, Founder-begleitet ohne Aufpreis | Monate Sechs- bis zwölfmonatige Build-Phase |
| Ideales Team-Setup Wer mit der Plattform arbeiten kann und wer arbeiten muss. | Cross-funktional Marketing, Redaktion, Design und Entwicklung gemeinsam | Engineering-only Drei oder mehr Frontend-Engineers |
| Preismodell Wie sich Kosten zusammensetzen: Software, Betrieb und Entwicklung. | [SaaS (planbar) Transparente Pläne, Hosting als Add-on](https://www.laioutr.com/de/pricing) [Preise ansehen](https://www.laioutr.com/de/pricing) | Engineering-Kosten Build plus dauerhafte Wartung |
*Comparison based on a typical mid-market setup, publicly available information and our own platform tests. As of July 2026. The exact scope depends on the specific Sulu project and its requirements; Sulu features may have evolved since.*
CUSTOM BUILD
### When a custom build is the right choice
A dedicated frontend team with Sulu, Symfony and content API experience is in place, at least three engineers. Exactly one Sulu frontend with highly specialized requirements is being built. Frontend engineering is a strategic core competency. The classic case: a brand with its own engineering team and a demand for pixel-level control.
LAIOUTR
### When Laioutr is the right choice
Go-live in weeks instead of months, editorial and marketing teams build pages on their own, several sites or brands run on Sulu, Sulu should stay and only the frontend is modernized, and BFSG and WCAG must be covered without a separate audit. The classic case: an organization that wants to modernize and scale its Sulu frontend without a large engineering investment.
BLUEPRINTS
## Start with a Blueprint instead of from scratch
Blueprints are pre-composed starter sites for each industry, instantly customizable and matched to the Sulu setup: a starting point for a faster go-live.
[View Blueprints](https://www.laioutr.com/en/blueprints)
UI PREVIEW
## What can be built with Laioutr on Sulu
Home pages, landing pages, campaign pages, content pages, blogs, career and product pages and more.
[Explore the UI preview](https://preview.laioutr.com/)
Support for implementation: certified composable partners deliver frontend projects with Laioutr, from greenfield setups to relaunches of existing Sulu websites.
[](https://www.bestit.de/ "Best it") [](https://www.datrycs.com/ "datrycs") [](https://www.valantic.com/ "valantic")
FAQ
## Frequently asked questions about the page builder for Sulu
Does Laioutr work with Sulu (webspaces and multilingual)?
Yes. Laioutr reads Sulu content via the headless/content API (SuluHeadlessBundle) and supports multiple webspaces, domains and multilingual setups, provided the corresponding API endpoints are available.
How does Laioutr differ from a custom build with Next.js or Nuxt?
A custom build typically takes six to twelve months of engineering plus ongoing maintenance by an in-house frontend team. Laioutr delivers Studio and 70+ components ready to use, with Cloud/Edge Hosting available as an add-on. Time-to-launch drops from months to weeks, and the total cost of ownership is typically well below.
How does Laioutr differ from classic Twig templates?
Twig is the classic developer route: every layout change goes through development. Laioutr delivers a visual builder, ready-made components, Themes and Blueprints, so marketing and editorial teams can build pages themselves, without a ticket for every change.
How does Laioutr connect to Sulu?
Laioutr connects via the Sulu headless/content API (SuluHeadlessBundle, JSON). Standard content (pages, snippets, navigation, translations) is supported, plus project-specific endpoints for custom logic.
Does Laioutr work with multiple webspaces?
Yes. Sulu webspaces are treated as standalone frontends in Laioutr. Layouts, content, languages and domains can be configured separately per site, in line with the Sulu webspace concept.
Can editorial workflows and permissions from Sulu still be used?
Yes. Editorial workflows, permissions and approvals remain in Sulu. Laioutr renders the approved content, and governance stays entirely in Sulu.
Sulu already has an API with the headless bundle, so why Laioutr?
Precisely because Sulu exposes content as an API, the frontend question remains open: Sulu delivers the data, but not the finished, visually operable frontend. Laioutr builds on this content API and makes the frontend operable for marketing, editorial and development teams together, without separate frontend development.
How long does implementation with Laioutr take?
A pilot is usually live within 14 days, and migration takes less than 14 days at the median. Founder-led migration is standard, not an extra charge. With several webspaces or complex requirements, the timeframe depends on the scope.
What does Laioutr cost compared to a custom build?
Laioutr works with transparent SaaS plans based on traffic and features. The total cost of ownership is typically below that of a custom build, because Studio, components and editor are part of the platform and no separate frontend team is needed. Cloud/Edge Hosting is available as an add-on and is not included in the license.
Can the backend be switched later without rebuilding the frontend?
Yes. Laioutr is backend-agnostic. If another system is added alongside Sulu later, such as a commerce backend, it is connected via an API instead of rebuilding the frontend.
Is the solution BFSG- and GDPR-compliant?
Yes. Laioutr is GDPR-compliant by default, EU hosting is available, further regions on request (US, APAC), and regional data residency is possible. In addition, there is an EU standard contract and German-language support. WCAG and the BFSG (German Accessibility Strengthening Act, binding since 2025) are covered by default: compliance is built in, not bolted on.
What happens to existing Sulu bundles?
Backend bundles (editorial, permissions, import, workflows) remain unchanged. Frontend-oriented features are typically replaced by Laioutr components or pre-integrated apps. The bundle stack is reviewed in the migration audit.
Is Laioutr itself also a CMS?
Yes. Laioutr is also an integrated headless CMS: content collections, Studio and frontend in one platform. With Sulu in place, Laioutr acts as the visual page builder and frontend, while Sulu remains the leading CMS. Content that should not be maintained in Sulu, for example for campaigns, can be managed directly in Laioutr.
## Latest insights from the Laioutr blog
[View all insights](https://www.laioutr.com/en/blogs/insights)
[Frontend options for Sulu: from CMS to live storefront
Sulu is a Symfony-based CMS you can run headless: it delivers content through the SuluHeadlessBundle…](https://www.laioutr.com/en/blog/sulu-frontend-options)
READ MORE
## More on page builders and headless CMS
### Visual page builder
How Laioutr works as a visual page builder with any CMS and commerce backend.
[More on the visual page builder](https://www.laioutr.com/en/composable-visual-page-builder)
### Headless CMS
Laioutr as an integrated headless CMS: content collections, Studio and frontend in one platform.
[More on the headless CMS](https://www.laioutr.com/en/headless-cms)
### Laioutr and existing CMS
How Laioutr works together with an existing content management system.
[More on CMS systems](https://www.laioutr.com/en/system/content-management-system-cms)
### Page builder for TYPO3
Visual editor and frontend for TYPO3, built on Laioutr.
[More on the page builder for TYPO3](https://www.laioutr.com/en/page-builder-typo3)
### Page builder for Contao
Visual editor and frontend for Contao, built on Laioutr.
[More on the page builder for Contao](https://www.laioutr.com/en/page-builder-contao)
QUESTIONS LEFT?
## Rethinking the Sulu frontend with the Laioutr page builder
30 minutes with the Laioutr team: see Laioutr live on the existing Sulu setup and get answers on integration, performance and pricing.
[Request a demo](https://www.laioutr.com/en/contact)
## Structured Data
```json
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.laioutr.com/#identity",
"name": "Laioutr",
"legalName": "Laioutr GmbH",
"url": "https://www.laioutr.com/",
"logo": {
"@type": "ImageObject",
"url": "https://www.laioutr.com/laioutr-logo.png",
"width": 400,
"height": 400
},
"email": "info@laioutr.com",
"telephone": "+49 30 75435715",
"address": {
"@type": "PostalAddress",
"streetAddress": "Münchweilersteig 5",
"postalCode": "12559",
"addressLocality": "Berlin",
"addressCountry": "DE"
},
"vatID": "DE450905846",
"sameAs": [
"https://www.linkedin.com/company/laioutr",
"https://www.youtube.com/@Laioutr",
"https://x.com/laioutr"
]
},
{
"@type": "WebSite",
"@id": "https://www.laioutr.com/en/#website",
"url": "https://www.laioutr.com/en/",
"name": "Laioutr",
"inLanguage": "en",
"publisher": {
"@id": "https://www.laioutr.com/#identity"
}
},
{
"@type": [
"WebPage",
"FAQPage"
],
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#webpage",
"url": "https://www.laioutr.com/en/page-builder-sulu-io",
"name": "Page Builder for Sulu: Build Pages Visually | Laioutr",
"description": "Page builder for Sulu: Laioutr adds a visual editor and fast frontend to Sulu content. No Twig templating, accessible and GDPR-compliant.",
"inLanguage": "en",
"isPartOf": {
"@id": "https://www.laioutr.com/en/#website"
},
"breadcrumb": {
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#breadcrumb"
},
"primaryImageOfPage": {
"@type": "ImageObject",
"url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmph2kcotbp8i08mh59ozh4ba"
},
"mainEntity": [
{
"@type": "Question",
"name": "Does Laioutr work with Sulu (webspaces and multilingual)?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr reads Sulu content via the headless/content API (SuluHeadlessBundle) and supports multiple webspaces, domains and multilingual setups, provided the corresponding API endpoints are available."
}
},
{
"@type": "Question",
"name": "How does Laioutr differ from a custom build with Next.js or Nuxt?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A custom build typically takes six to twelve months of engineering plus ongoing maintenance by an in-house frontend team. Laioutr delivers Studio and 70+ components ready to use, with Cloud/Edge Hosting available as an add-on. Time-to-launch drops from months to weeks, and the total cost of ownership is typically well below."
}
},
{
"@type": "Question",
"name": "How does Laioutr differ from classic Twig templates?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Twig is the classic developer route: every layout change goes through development. Laioutr delivers a visual builder, ready-made components, Themes and Blueprints, so marketing and editorial teams can build pages themselves, without a ticket for every change."
}
},
{
"@type": "Question",
"name": "How does Laioutr connect to Sulu?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Laioutr connects via the Sulu headless/content API (SuluHeadlessBundle, JSON). Standard content (pages, snippets, navigation, translations) is supported, plus project-specific endpoints for custom logic."
}
},
{
"@type": "Question",
"name": "Does Laioutr work with multiple webspaces?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Sulu webspaces are treated as standalone frontends in Laioutr. Layouts, content, languages and domains can be configured separately per site, in line with the Sulu webspace concept."
}
},
{
"@type": "Question",
"name": "Can editorial workflows and permissions from Sulu still be used?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Editorial workflows, permissions and approvals remain in Sulu. Laioutr renders the approved content, and governance stays entirely in Sulu."
}
},
{
"@type": "Question",
"name": "Sulu already has an API with the headless bundle, so why Laioutr?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Precisely because Sulu exposes content as an API, the frontend question remains open: Sulu delivers the data, but not the finished, visually operable frontend. Laioutr builds on this content API and makes the frontend operable for marketing, editorial and development teams together, without separate frontend development."
}
},
{
"@type": "Question",
"name": "How long does implementation with Laioutr take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A pilot is usually live within 14 days, and migration takes less than 14 days at the median. Founder-led migration is standard, not an extra charge. With several webspaces or complex requirements, the timeframe depends on the scope."
}
},
{
"@type": "Question",
"name": "What does Laioutr cost compared to a custom build?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Laioutr works with transparent SaaS plans based on traffic and features. The total cost of ownership is typically below that of a custom build, because Studio, components and editor are part of the platform and no separate frontend team is needed. Cloud/Edge Hosting is available as an add-on and is not included in the license."
}
},
{
"@type": "Question",
"name": "Can the backend be switched later without rebuilding the frontend?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr is backend-agnostic. If another system is added alongside Sulu later, such as a commerce backend, it is connected via an API instead of rebuilding the frontend."
}
},
{
"@type": "Question",
"name": "Is the solution BFSG- and GDPR-compliant?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr is GDPR-compliant by default, EU hosting is available, further regions on request (US, APAC), and regional data residency is possible. In addition, there is an EU standard contract and German-language support. WCAG and the BFSG (German Accessibility Strengthening Act, binding since 2025) are covered by default: compliance is built in, not bolted on."
}
},
{
"@type": "Question",
"name": "What happens to existing Sulu bundles?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Backend bundles (editorial, permissions, import, workflows) remain unchanged. Frontend-oriented features are typically replaced by Laioutr components or pre-integrated apps. The bundle stack is reviewed in the migration audit."
}
},
{
"@type": "Question",
"name": "Is Laioutr itself also a CMS?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr is also an integrated headless CMS: content collections, Studio and frontend in one platform. With Sulu in place, Laioutr acts as the visual page builder and frontend, while Sulu remains the leading CMS. Content that should not be maintained in Sulu, for example for campaigns, can be managed directly in Laioutr."
}
}
]
},
{
"@type": "BreadcrumbList",
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Laioutr",
"item": "https://www.laioutr.com/en/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Page Builder for Sulu: Build Pages Visually"
}
]
}
]
}
```
```json
{
"@context": "https://schema.org",
"@graph": [
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#webpage",
"description": "Page builder for Sulu: Laioutr adds a visual editor and fast frontend to Sulu content. No Twig templating, accessible and GDPR-compliant.",
"name": "Page Builder for Sulu: Build Pages Visually | Laioutr",
"url": "https://www.laioutr.com/en/page-builder-sulu-io",
"@type": [
"WebPage",
"FAQPage"
],
"mainEntity": [
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/1"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/2"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/3"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/4"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/5"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/6"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/7"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/8"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/9"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/10"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/11"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/12"
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/13"
}
]
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/1",
"@type": "Question",
"inLanguage": "en",
"name": "Does Laioutr work with Sulu (webspaces and multilingual)?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr reads Sulu content via the headless/content API (SuluHeadlessBundle) and supports multiple webspaces, domains and multilingual setups, provided the corresponding API endpoints are available.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/2",
"@type": "Question",
"inLanguage": "en",
"name": "How does Laioutr differ from a custom build with Next.js or Nuxt?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A custom build typically takes six to twelve months of engineering plus ongoing maintenance by an in-house frontend team. Laioutr delivers Studio and 70+ components ready to use, with Cloud/Edge Hosting available as an add-on. Time-to-launch drops from months to weeks, and the total cost of ownership is typically well below.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/3",
"@type": "Question",
"inLanguage": "en",
"name": "How does Laioutr differ from classic Twig templates?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Twig is the classic developer route: every layout change goes through development. Laioutr delivers a visual builder, ready-made components, Themes and Blueprints, so marketing and editorial teams can build pages themselves, without a ticket for every change.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/4",
"@type": "Question",
"inLanguage": "en",
"name": "How does Laioutr connect to Sulu?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Laioutr connects via the Sulu headless/content API (SuluHeadlessBundle, JSON). Standard content (pages, snippets, navigation, translations) is supported, plus project-specific endpoints for custom logic.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/5",
"@type": "Question",
"inLanguage": "en",
"name": "Does Laioutr work with multiple webspaces?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Sulu webspaces are treated as standalone frontends in Laioutr. Layouts, content, languages and domains can be configured separately per site, in line with the Sulu webspace concept.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/6",
"@type": "Question",
"inLanguage": "en",
"name": "Can editorial workflows and permissions from Sulu still be used?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Editorial workflows, permissions and approvals remain in Sulu. Laioutr renders the approved content, and governance stays entirely in Sulu.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/7",
"@type": "Question",
"inLanguage": "en",
"name": "Sulu already has an API with the headless bundle, so why Laioutr?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Precisely because Sulu exposes content as an API, the frontend question remains open: Sulu delivers the data, but not the finished, visually operable frontend. Laioutr builds on this content API and makes the frontend operable for marketing, editorial and development teams together, without separate frontend development.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/8",
"@type": "Question",
"inLanguage": "en",
"name": "How long does implementation with Laioutr take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A pilot is usually live within 14 days, and migration takes less than 14 days at the median. Founder-led migration is standard, not an extra charge. With several webspaces or complex requirements, the timeframe depends on the scope.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/9",
"@type": "Question",
"inLanguage": "en",
"name": "What does Laioutr cost compared to a custom build?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Laioutr works with transparent SaaS plans based on traffic and features. The total cost of ownership is typically below that of a custom build, because Studio, components and editor are part of the platform and no separate frontend team is needed. Cloud/Edge Hosting is available as an add-on and is not included in the license.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/10",
"@type": "Question",
"inLanguage": "en",
"name": "Can the backend be switched later without rebuilding the frontend?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr is backend-agnostic. If another system is added alongside Sulu later, such as a commerce backend, it is connected via an API instead of rebuilding the frontend.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/11",
"@type": "Question",
"inLanguage": "en",
"name": "Is the solution BFSG- and GDPR-compliant?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr is GDPR-compliant by default, EU hosting is available, further regions on request (US, APAC), and regional data residency is possible. In addition, there is an EU standard contract and German-language support. WCAG and the BFSG (German Accessibility Strengthening Act, binding since 2025) are covered by default: compliance is built in, not bolted on.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/12",
"@type": "Question",
"inLanguage": "en",
"name": "What happens to existing Sulu bundles?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Backend bundles (editorial, permissions, import, workflows) remain unchanged. Frontend-oriented features are typically replaced by Laioutr components or pre-integrated apps. The bundle stack is reviewed in the migration audit.
"
}
},
{
"@id": "https://www.laioutr.com/en/page-builder-sulu-io#/schema/question/13",
"@type": "Question",
"inLanguage": "en",
"name": "Is Laioutr itself also a CMS?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Laioutr is also an integrated headless CMS: content collections, Studio and frontend in one platform. With Sulu in place, Laioutr acts as the visual page builder and frontend, while Sulu remains the leading CMS. Content that should not be maintained in Sulu, for example for campaigns, can be managed directly in Laioutr.
"
}
}
]
}
```