More speed and design freedom for your TYPO3 – with Laioutr
Feel free to contact one of our partners for your e-commerce frontend built on Laioutr.
5/5
OMR Reviews
70+
Frontend components
Lighthouse 100
Performance from day one
Made in EU
GDPR-compliant, server location in Germany
100% Match
What does a page builder for TYPO3 mean?
TYPO3 is a powerful enterprise CMS: content, editorial workflows, permissions, multi-site and multilingualism are its strengths. What's often missing is a modern, visual frontend that marketing and editorial teams can operate without Fluid templating. That's exactly where Laioutr comes in: as a visual page builder and frontend layer that reads your TYPO3 content via the content API (TYPO3 Headless) and renders it in a fast website. TYPO3 stays your system, Laioutr delivers the frontend.
1. The backend stays TYPO3
TYPO3 keeps managing content, the page tree, permissions, editorial workflows, multi-site and translations. You use the TYPO3 backend and your established processes unchanged – with all your extensions and workflows.
2. The frontend is selected
For the frontend you have several options: classic Fluid/TypoScript, a headless setup (EXT:headless) with your own frontend, a custom build – or a page builder like Laioutr. Each option has its pros and cons.
3. Content flows via the content API in real time
No data duplication, no sync conflicts. Laioutr reads your TYPO3 content via the headless/content API (JSON) and renders it – including multilingualism and multi-site.
100% Match
What frontend options do you have for Saleor?
With Fluid, TypoScript and the headless extension, TYPO3 provides the building blocks but no ready-made, visually operable frontend product for non-developers. That puts the frontend question on the table for every TYPO3 project. Four options are established.
1. Fluid & TypoScript (classic)
The classic TYPO3 route: templates in Fluid, configuration via TypoScript. Full integration, but every layout change goes through development. A good fit for stable pages with rare changes or when your team is deep in TYPO3.
2. TYPO3 Headless (EXT:headless) with your own frontend
The headless extension exposes TYPO3 content as a JSON API. You build the decoupled frontend yourself – maximum freedom, but the design system, components and maintenance are on you. 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 TYPO3 content API itself. A good fit if frontend engineering is your strategic core competency.
4. Laioutr Page Builder
Visual page builder and frontend platform with 70+ components, EU hosting and a TYPO3 connection. Fastest time-to-launch, lowest learning curve, marketing and editorial build pages themselves. A good fit if you want to go live quickly without a custom-build investment.
100% Match
What you build with Laioutr on TYPO3
Laioutr is built for TYPO3 setups that need to change and scale fast – from corporate websites to multi-site portfolios to campaign landing pages with heavy editorial volume.
Multichannel storefronts on a single Saleor backend
TYPO3 excels at multi-site: 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 blocks – without a Fluid template and without a developer ticket. Content comes from TYPO3, the layout is created in the page builder.
Multilingual websites
TYPO3 manages translations and language trees, Laioutr renders them consistently. Languages, layouts and content are controllable per site, compatible with the TYPO3 language concept.
Public sector & accessibility
Public authorities and institutions rely on TYPO3. Laioutr delivers the accessible frontend to match – WCAG- and BFSG-compliant, GDPR-compliant with hosting in the EU.
Relaunch without touching the backend config
Renew your existing TYPO3 frontend without touching the page tree, permissions or editorial processes. Phased migration with a clear rollback plan.
New TYPO3 projects live fast
New TYPO3 project, fresh start. With Laioutr themes and the UI library it goes live in weeks, instead of investing months in a custom build.
Laioutr vs. building the frontend yourself
The honest comparison
With Fluid, TypoScript and the headless extension, TYPO3 provides the building blocks but no ready-made, visually operable frontend product for non-developers. The most common frontend decision is therefore: a custom build (Next.js or Nuxt on the TYPO3 content API) or a page builder like Laioutr. The custom build gives maximum control but costs a six- to twelve-month build phase and ongoing maintenance. Laioutr delivers Studio, 70+ components and hosting in the plan, with full code extensibility for edge cases. Both connect to the same TYPO3.
Compare differences | Laioutr Page Builder | Eigenentwicklung (Next.js / Nuxt) |
|---|---|---|
Builder und Komponenten Was Sie aus der Box bekommen und was Sie selbst aufbauen müssen. | ||
Visueller Page Builder Drag-and-Drop-Editor für Marketing- und Redaktions-Teams. | Inklusive (Studio) Live-Preview, 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 |
Themes und Vorlagen Startpunkt für neue Websites ohne Greenfield-Aufwand. | Vorgefertigte Themes Sofort einsatzbereit, voll erweiterbar | Greenfield Designsystem komplett selbst aufbauen |
Hosting Wo das Frontend ausgeliefert wird und wer es betreibt. | Inklusive (EU-CDN) Laioutr Cloud, kein separater Deploy | Selbst hosten Vercel, AWS, eigene Infrastruktur |
Architektur und Compliance Wie flexibel die Plattform ist und was Sie regulatorisch mitbekommen. | ||
Backend-Flexibilität Welche CMS- und Commerce-Backends sich anbinden lassen. | Multi-Backend TYPO3, weitere CMS und Commerce-Systeme | Backend-spezifisch Code an TYPO3-Content-API gebunden, Wechsel teuer |
Performance und Core Web Vitals Wie viel Aufwand für Lighthouse-100-Niveau nötig ist. | Out of the box Lighthouse 100 als Default-Ziel | Manuelles Tuning Performance-Engineering durch 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 Serverstandort Wo Daten verarbeitet werden und welche EU-Verträge gelten. | EU und Deutschland EU-Standardvertrag, deutschsprachiger Support | Hosting-abhängig Je nachdem, wo Sie deployen |
Team und Wirtschaftlichkeit Wer mit der Plattform produktiv ist und was es Sie über die Zeit kostet. | ||
Lernkurve Wie schnell ein neues Teammitglied produktiv wird. | Niedrig Redaktion onboardet in Tagen | Hoch Fluid/TypoScript bzw. React/Vue plus TYPO3-Content-API |
Time-to-Launch Realistische Zeitspanne bis zum Live-Gang einer neuen Website. | Wochen Mit Themes und UI-Bibliothek | 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 Dev gemeinsam | Engineering-only Drei plus Frontend-Engineers |
Preismodell Wie sich Kosten zusammensetzen, Software plus Betrieb plus Entwicklung. | SaaS (planbar) Transparente Pläne, Hosting inklusive Preise ansehen | Engineering-Kosten Build plus dauerhafte Wartung |
All information is based on publicly available sources, experience from projects with DACH organisations and our own platform testing. As of: July 2026. TYPO3 features may have evolved since.
Custom build
When a custom build is the right choice
You have a dedicated frontend team with TYPO3 and content-API experience, at least three engineers. You are building exactly one TYPO3 frontend with highly specialised requirements. Frontend engineering is your strategic core competency. Typical case: a brand with its own engineering team and a pixel-level control ambition.
LAIOUTR
When Laioutr is the right choice
You want weeks instead of months to go-live, editorial and marketing should build pages independently, you run several TYPO3 sites or brands, you want to keep your TYPO3 and only modernise the frontend, and BFSG and WCAG must be solved without a separate audit. Typical case: an organisation that wants to modernise and scale its TYPO3 frontend without a double-digit engineering investment.
You don't have to do this alone. Our certified composable partners have delivered Saleor frontend projects with Laioutr, from greenfield setups to storefront-example migrations.
FAQ