We handle the migration together with your team: existing storefront components (Vue/Nuxt or React), Storefront UI customizations, middleware configurations, and backend connectors are assessed and carried over. In most cases we resolve the custom-build portions of Alokai projects with native Laioutr means, and the rest runs as an app in the Laioutr App Store. Thanks to themes and the UI library, most of the original setup falls away, so most migrations go productive in a few weeks.

Yes. commercetools is one of 19+ pre-integrated backends in Laioutr. Just as Alokai builds on commercetools via connectors, Laioutr connects natively, without a separate connector repository and without its own middleware configuration. You keep your commerce stack and only swap out the frontend layer.

Storefront UI is a component library for developers, building blocks assembled in code. Laioutr Studio is a full-fledged visual page builder for marketing teams. With Alokai, developers build the page structures and marketing only maintains content. With Laioutr, marketing and content teams work directly in Studio via drag-and-drop, with no dev ticket and no deploy cycle.

Standard replatformings on an established backend (Shopify, Shopware, commercetools, Adobe Commerce, etc.) go productive with Laioutr in four to eight weeks. Alokai projects are set up as software development undertakings and typically run four to nine months, because your developers build the storefront themselves with Storefront UI, middleware, and connectors.

Laioutr hosts on Laioutr Cloud (EU, Frankfurt, GDPR-compliant), on Vercel, or in your own hosting environment (Bring Your Own Hosting), as you prefer. We offer WCAG 3.0 Ready, a DPA on request, and EU data residency, which matters for regulated industries (DORA, financial services, public sector). Alokai Cloud is available but isn't primarily tailored to the DACH compliance context.

Yes. Laioutr is built natively for multi-brand and multi-market scenarios: central management, granular roles, and up to unlimited projects and domains on the Enterprise plan. Alokai supports multi-site setups, but mostly as a custom implementation in the middleware, with the corresponding development and maintenance effort.

We publish our plans transparently on our pricing page. Three plans (Growth / Pro / Enterprise) cover everything from a single storefront to a global brand portfolio. Alokai is formally free under the open-source model, but the real costs arise via Vue/React development, DevOps, and Alokai Cloud add-ons. For the Enterprise edition, Alokai only provides pricing via a sales quote, so a direct list-price comparison is only possible after an individual quote request.

On the Pro plan you get guaranteed response SLAs, and on the Enterprise plan a dedicated Customer Success Manager on top. Slack Connect, direct founder contact, and German-language support are unique in the DACH market. Alokai offers community support for the open-source edition and enterprise support for the paid edition, both without a dedicated DACH team.

Yes. Our Switch Program supports brands moving away from an existing frontend platform: an architecture workshop, a migration plan, theme adaptation to your design system, and hands-on guidance through to go-live are standard. Specifically for Alokai projects, we assess which custom components can be moved directly into Laioutr Studio and which live on as an app in the Laioutr App Store.

Reusable components, design tokens, and content can be carried over into Laioutr. The Laioutr UI library lets you map your existing design system, whether you worked with Storefront UI in Vue/Nuxt or in the React variant. Custom logic from your Alokai middleware is assessed in the migration workshop: we handle most of it with native Laioutr means, and the rest runs as an app in the Laioutr App Store.