---
title: "Academy Article"
canonical_url: "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr"
locale: en
meta:
  "og:title": "Academy Article"
---

[Go to home](https://academy.laioutr.com/en)

- [Getting started](https://academy.laioutr.com/en/bereiche/getting-started)

- [Account and first project](https://academy.laioutr.com/en/leitfaeden/account-and-first-project)

- [How data flows in Laioutr](https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr)

# How data flows in Laioutr

Studio defines how a page is built, and Orchestr fetches the data for it on the server from connected systems such as shop, CMS or ERP and combines it into one unified data model.

## Before you start

<dl>

<dt>Duration</dt>
<dd>5 min</dd></dl>

Last reviewed on October 15, 2026

A Laioutr storefront works with two kinds of data. **Static project data** such as page structure, sections, blocks, texts and settings is created in Studio and Cockpit. On publishing, Studio writes it into the project configuration from which the storefront is built.

**Dynamic data** such as products, prices, categories, search results or CMS content stays in the connected systems. Apps connect these systems, and Orchestr is the data layer in between. Orchestr first asks which entries a page needs and then loads only the parts a section actually shows, for example name, image and price for a product tile.

Several sources can be combined: master data from the shop, prices from the ERP, recommendations from a search service. Everything runs on the server, credentials never reach the browser, and results are cached. When a company changes its shop system, the app is replaced; pages and sections stay.

## Step by step

1. 1 ### Step 1: Studio describes the page

   Studio defines which sections and blocks a page has and which data a section shows, for example the products of a category.
2. 2 ### Step 2: Publishing creates the configuration

   **Publish** turns the Studio state into the project configuration, and the storefront is built and delivered.
3. 3 ### Step 3: Orchestr loads the data

   When a page is requested, Orchestr queries the connected systems through the installed apps and loads only the data parts needed.
4. 4 ### Step 4: The storefront shows the result

   Sections receive uniformly prepared data, regardless of the system it comes from.

## Frequently asked questions

Does Laioutr copy the product catalogue?

No. Products and prices stay in the shop or ERP system. Orchestr loads them on the server when needed and only caches results to deliver pages quickly.

What happens when the shop system changes?

The app for the old system is replaced by the app for the new one. Because sections work with the unified data model, pages and layouts stay as they are.

Are credentials visible in the browser?

No. Orchestr runs on the server only. API keys for shop, ERP or CMS are stored encrypted in Cockpit and never sent to the browser.

## Related

- [Enter credentials and test the connection](https://academy.laioutr.com/en/artikel/enter-credentials-and-test-the-connection)5 min

  App credentials are entered per environment under Configuration, checked with Test connection and stored with Save settings. They take effect with the next deployment.
- [Fill sections with shop data](https://academy.laioutr.com/en/artikel/fill-sections-with-shop-data)7 min

  Sections with a data field show products, categories or posts from connected systems. The team picks a data query in Studio, sets input, limit and sorting, and Orchestr delivers the data at render time.
- [Performance: caching and Orchestr](https://academy.laioutr.com/en/artikel/performance-caching-and-orchestr)6 min

  Laioutr speeds up storefronts with three cache layers: the Orchestr entity cache on the server, the HTTP cache at the edge and a store in the browser. Together they keep repeated requests from putting load on backends.
- [Orchestr: entities, queries, actions and resolvers](https://academy.laioutr.com/en/artikel/orchestr-entities-queries-actions-and-resolvers)8 min

  Orchestr is Laioutr's data layer and runs server-side in the Nuxt server. Queries return entity IDs, component resolvers load the data for them, actions perform changes, and tokens form the contract between frontend, Orchestr and apps.
- [Find, install and configure apps](https://academy.laioutr.com/en/artikel/find-install-and-configure-apps)6 min

  Apps are listed in the Cockpit catalogue under Apps, installed per environment and set up under Configuration. The storefront uses them from the next deployment onwards.

## Learn it in a lesson

- [What apps deliver and where they are configured](https://academy.laioutr.com/en/lektionen/foundations-what-apps-deliver)9 min
- [Organisation, project and environments](https://academy.laioutr.com/en/lektionen/foundations-organisation-project-environments)10 min
- [Orchestr: entities, queries, actions](https://academy.laioutr.com/en/lektionen/developer-orchestr-and-data-queries)14 min
- [How data flows in Laioutr](https://academy.laioutr.com/en/lektionen/go-live-how-data-flows)6 min
- [Understand the architecture](https://academy.laioutr.com/en/lektionen/developer-architecture)10 min

## [Account and first project](https://academy.laioutr.com/en/leitfaeden/account-and-first-project)

Search this guide

1. [Laioutr at a glance: organisation, project, environments](https://academy.laioutr.com/en/artikel/laioutr-at-a-glance-organisation-project-environments)4 min
2. [Sign up and create an organisation](https://academy.laioutr.com/en/artikel/sign-up-and-create-an-organisation)3 min
3. [Create the first project](https://academy.laioutr.com/en/artikel/create-the-first-project)5 min
4. [How data flows in Laioutr](https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr)5 min
5. [From sign-up to a live storefront without help](https://academy.laioutr.com/en/artikel/from-sign-up-to-a-live-storefront-without-help)12 min
6. [Start a project from a Blueprint](https://academy.laioutr.com/en/artikel/start-a-project-from-a-blueprint)5 min

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://academy.laioutr.com/#website",
      "@type": "WebSite",
      "inLanguage": "en",
      "name": "Default",
      "url": "https://academy.laioutr.com/",
      "translationOfWork": {
        "@id": "https://academy.laioutr.com/#website"
      }
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#webpage",
      "name": "Academy Article",
      "url": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr",
      "@type": [
        "WebPage",
        "FAQPage"
      ],
      "breadcrumb": {
        "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#breadcrumb"
      },
      "isPartOf": {
        "@id": "https://academy.laioutr.com/#website"
      },
      "mainEntity": [
        {
          "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#/schema/question/1"
        },
        {
          "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#/schema/question/2"
        },
        {
          "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#/schema/question/3"
        }
      ],
      "potentialAction": [
        {
          "@type": "ReadAction",
          "target": [
            "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr"
          ]
        }
      ]
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#breadcrumb",
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "name": "Home",
          "item": "https://academy.laioutr.com/en",
          "position": 1
        },
        {
          "@type": "ListItem",
          "name": "Getting started",
          "item": "https://academy.laioutr.com/en/bereiche/getting-started",
          "position": 2
        },
        {
          "@type": "ListItem",
          "name": "Account and first project",
          "item": "https://academy.laioutr.com/en/leitfaeden/account-and-first-project",
          "position": 3
        },
        {
          "@type": "ListItem",
          "name": "How data flows in Laioutr",
          "item": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr",
          "position": 4
        }
      ]
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#/schema/question/1",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does Laioutr copy the product catalogue?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>No. Products and prices stay in the shop or ERP system. Orchestr loads them on the server when needed and only caches results to deliver pages quickly.</p>"
      }
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#/schema/question/2",
      "@type": "Question",
      "inLanguage": "en",
      "name": "What happens when the shop system changes?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>The app for the old system is replaced by the app for the new one. Because sections work with the unified data model, pages and layouts stay as they are.</p>"
      }
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/how-data-flows-in-laioutr#/schema/question/3",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Are credentials visible in the browser?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>No. Orchestr runs on the server only. API keys for shop, ERP or CMS are stored encrypted in Cockpit and never sent to the browser.</p>"
      }
    }
  ]
}
```