Orchestr connects your backend, whichever one it is, with your frontend components, from any library. One data layer instead of two systems, one data model instead of data islands. That's how composability stops being a claim and becomes code.
Why data integration eats up so much time today
Every new backend system means a new integration project: its own interfaces, its own data model, its own maintenance. Content teams and engineering end up running two software stacks in parallel, while every frontend library needs its own connections. The result: delays, duplicated work, and an architecture that gets more brittle with every new system.
Orchestr makes data integration part of the platform
Instead of treating data integration as a separate project, Laioutr builds it directly into the platform: Orchestr fetches data from your backend, whichever one it is, and makes it available in a type-safe way to every frontend component. No add-on system, no parallel stack, data integration is part of your frontend from day one.
How it works
From the request in the frontend to the finished component, in four steps.
Query
The component requests data via a slug, search term or filter. Orchestr translates that into a query.
Connect
A component resolver fetches the matching data from your backend, whichever system it runs on.
Link
Relationships between entities, like a product and its variants, are resolved and delivered alongside.
Deliver
The finished, type-safe response goes straight to your frontend component, from any library.
Every component knows what it needs
Component resolvers declare exactly which data they provide. The frontend only requests what a page actually needs, Orchestr skips the rest. No overfetching, no wasted API calls.
One layer instead of two systems
Hosting content and integrating data are not an either-or at Laioutr. Through Apps, our Nuxt modules, you connect your backend and manage your content in the same system, without running two software stacks in parallel.
Your data model or our canonical model
Use Laioutr's canonical data model for standard entities like product or category, or define your own schema for whatever makes your business distinct. Both run type-safely through the same layer.
Every component, from any library
Orchestr isn't tied to Laioutr components. Any frontend component, from any library, can consume the same data. That's how composability becomes real freedom of choice instead of vendor lock-in.
Tokens: the contract between frontend and backend
Every query, every link, every component is defined through a token, a clear contract between your frontend and the systems providing the data. That's how Orchestr always knows which app is responsible for which request, with no hard-wired integrations.
This is exactly the layer of abstraction where composability actually comes from: not just interchangeable UI building blocks, but clearly defined, reusable contracts between data and presentation.
Everything real composability needs
Query handlers
Fetch entities by slug, search term or filter, with pagination and sorting.
Link handlers
Resolve relationships between entities, like product to variant or category to product.
Component resolvers
Attach data from any system to any entity, without changing existing code.
Action handlers
Process mutations like cart changes or orders, type-safe and server-side.
Canonical data model
Standard entities like product, category or cart are predefined and ready to use.
Custom schema
Define new entities and components for whatever makes your business model distinct.
Three-level caching
Queries, links and component resolvers cache independently, for low latency without stale data.
Any frontend library
Whether it's Laioutr UI, your own component library or third-party components, Orchestr serves them all.
1 layer
for content and data
Any backend
without changing your architecture
Any library
for your frontend components
3 cache levels
for stable performance
Strategy call
Ready to turn your frontend into a control layer?
Show us your stack, your roadmap, your replatforming scenario, and we'll show you how Laioutr fits, what it costs, and how fast you go live.
"After 30 minutes, we knew Laioutr makes our replatforming feasible." - Daniel B., CEO, hygibox.de