---
title: "Academy Article"
canonical_url: "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house"
locale: en
meta:
"og:title": "Academy Article"
---
[Go to home](https://academy.laioutr.com/en)
- [Hosting and operations](https://academy.laioutr.com/en/bereiche/hosting-and-operations)
- [Deployment](https://academy.laioutr.com/en/leitfaeden/deployment)
- [Bring Your Own Server: host the storefront in-house](https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house)
In preparation
# Bring Your Own Server: host the storefront in-house
With Bring Your Own Server (BYOS) the storefront runs on in-house infrastructure or with a host of choice, while content, apps and deployments are still managed in Studio and Cockpit. Cockpit starts deployments through a webhook; the infrastructure builds, serves and reports the status back.
## Before you start
- Plan
- In-house hosting infrastructure or a hosting partner that runs it
- Role
- Permission to configure the project's hosting
- Duration
- 7 min
### Prerequisites
- A team or partner responsible for servers, builds and operations
- A webhook address reachable publicly over HTTPS
- Servers with Node.js and Redis for the storefront
Last reviewed on October 16, 2026
**Bring Your Own Server (BYOS)** is the hosting option for companies that want to run their storefront themselves: in their own data centre, their own cloud or with a host of their choice. Laioutr remains the central place for the frontend. Pages, content, apps and configuration are still maintained in Studio and Cockpit, and deployments are started and tracked in Cockpit. The storefront is built and served on the in-house infrastructure.
The connection runs through a webhook. For every deployment, Cockpit sends the project files to an address on the in-house infrastructure. There a pipeline builds the storefront, starts it and reports progress back, so Cockpit shows the status as usual. Depending on the setup, the in-house side also handles cancelling, promoting, rolling back and deleting deployments. Cockpit offers only the actions the infrastructure supports.
BYOS fits when internal DevOps standards, compliance rules, a fixed data location or existing monitoring require in-house operation. Operations are then the responsibility of the in-house team or the hosting partner: servers, scaling, caching, certificates, monitoring and backups. As a ready-made counterpart, Laioutr provides the BYOS Agent, which verifies webhooks and runs deploy scripts. Without in-house operations, Laioutr Cloud or a connected hyperscaler is the simpler choice.
## Step by step
1. 1 ### Step 1: Agree on operations
Agree with IT or the hosting partner who runs servers, builds, caching and monitoring, and which actions are needed: status updates, cancel, promote, roll back or delete.
2. 2 ### Step 2: Provide the counterpart
The operations team sets up a webhook address that is publicly reachable over HTTPS, for example with the Laioutr BYOS Agent, plus servers with Node.js and Redis for the storefront.
3. 3 ### Step 3: Connect custom hosting in Cockpit
Open **Hosting** in the project and choose custom hosting via webhook. Enter the address under **Webhook Endpoint URL** and select **Generate Signing Secret**.
4. 4 ### Step 4: Hand over the signing secret
Copy the secret, which starts with `whsec_`, and pass it securely to the operations team. The counterpart uses it to check that every request really comes from Cockpit.
5. 5 ### Step 5: Test and save the connection
Select **Test Connection**. Cockpit shows the counterpart's name and the supported actions. Finish with **Continue** and **Confirm & Save**.
6. 6 ### Step 6: Start the first deployment
Start a deployment under **Deployments** and follow its status. The in-house infrastructure builds the storefront and reports success or failure back.
## Check the result
The deployment changes to successful in Cockpit and shows the storefront address. The storefront is reachable on the own domain, and the Studio preview shows it. If the status stays unknown, the counterpart does not report status back.
## Frequently asked questions
What stays with Laioutr, and what is the in-house team's job?
Studio, Cockpit, apps, configuration and starting and tracking deployments stay with Laioutr. The in-house team or hosting partner is responsible for builds, servers, scaling, caching, certificates, domains, monitoring and backups.
Does this require programming?
Not necessarily. The Laioutr BYOS Agent receives the webhooks and runs deploy scripts; ready-made examples exist for Docker and PM2. Teams that want to connect an existing CI/CD pipeline build the counterpart themselves; the developer documentation describes the interface.
Why are actions such as roll back missing in Cockpit?
Cockpit shows only the actions the counterpart reports as supported when it connects. Once the in-house infrastructure supports and reports more actions, they appear in Cockpit.
What does the infrastructure need?
Node.js 22.12 or later with pnpm for builds and runtime, Redis 6 or later as cache, HTTPS, public reachability for the webhooks, and own domains. For health checks the storefront answers at `/api/frontend/health`.
## Related
- [Start and check a deployment](https://academy.laioutr.com/en/artikel/start-and-check-a-deployment)5 min
A deployment rebuilds the storefront of an environment and puts changes to apps, versions and configuration live. It is started in Cockpit under Deployments with Deploy; the status and build log show whether it worked.
- [Compare and roll back deployments](https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments)5 min
Every deployment has its own address, so two versions can be compared side by side. A rollback puts an already built earlier production deployment live again within seconds, without a new build.
- [Hosting and edge delivery](https://academy.laioutr.com/en/artikel/hosting-and-edge-delivery)4 min
Laioutr Cloud is the built-in hosting for storefronts made with Laioutr and delivers them through a global edge network with more than 100 locations. Alternatively, a storefront runs through hyperscaler adapters, native hosting partners or on a self-managed server.
- [Read storefront logs](https://academy.laioutr.com/en/artikel/read-storefront-logs)6 min
Under Logs, Cockpit shows what the storefront of each environment on Laioutr Cloud writes, plus an access log. Each line's level comes from the console method that was called, and a trace finds all lines of one request.
- [Vercel: deploy the storefront from Cockpit to Vercel](https://academy.laioutr.com/en/apps/vercel-deploy-the-storefront-from-cockpit)10 min
With the Vercel connection, Cockpit deploys the storefront directly into an existing Vercel project of the company. Project name, API token and team ID are stored under Hosting, Vercel; build and delivery run on Vercel.
## [Deployment](https://academy.laioutr.com/en/leitfaeden/deployment)
Search this guide
1. [Understanding the main, dev and stage environments](https://academy.laioutr.com/en/artikel/understanding-main-dev-and-stage-environments)5 min
2. [Start and check a deployment](https://academy.laioutr.com/en/artikel/start-and-check-a-deployment)5 min
3. [Compare and roll back deployments](https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments)5 min
4. [Read storefront logs](https://academy.laioutr.com/en/artikel/read-storefront-logs)6 min
5. [Bring Your Own Server: host the storefront in-house](https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house)7 min In preparation
## 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/bring-your-own-server-host-the-storefront-in-house#webpage",
"name": "Academy Article",
"url": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house",
"@type": [
"WebPage",
"FAQPage"
],
"breadcrumb": {
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#breadcrumb"
},
"isPartOf": {
"@id": "https://academy.laioutr.com/#website"
},
"mainEntity": [
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/1"
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/2"
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/3"
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/4"
}
],
"potentialAction": [
{
"@type": "ReadAction",
"target": [
"https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house"
]
}
]
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#breadcrumb",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"name": "Home",
"item": "https://academy.laioutr.com/en",
"position": 1
},
{
"@type": "ListItem",
"name": "Hosting and operations",
"item": "https://academy.laioutr.com/en/bereiche/hosting-and-operations",
"position": 2
},
{
"@type": "ListItem",
"name": "Deployment",
"item": "https://academy.laioutr.com/en/leitfaeden/deployment",
"position": 3
},
{
"@type": "ListItem",
"name": "Bring Your Own Server: host the storefront in-house",
"item": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house",
"position": 4
}
]
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/1",
"@type": "Question",
"inLanguage": "en",
"name": "What stays with Laioutr, and what is the in-house team's job?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Studio, Cockpit, apps, configuration and starting and tracking deployments stay with Laioutr. The in-house team or hosting partner is responsible for builds, servers, scaling, caching, certificates, domains, monitoring and backups.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/2",
"@type": "Question",
"inLanguage": "en",
"name": "Does this require programming?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Not necessarily. The Laioutr BYOS Agent receives the webhooks and runs deploy scripts; ready-made examples exist for Docker and PM2. Teams that want to connect an existing CI/CD pipeline build the counterpart themselves; the developer documentation describes the interface.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/3",
"@type": "Question",
"inLanguage": "en",
"name": "Why are actions such as roll back missing in Cockpit?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Cockpit shows only the actions the counterpart reports as supported when it connects. Once the in-house infrastructure supports and reports more actions, they appear in Cockpit.
"
}
},
{
"@id": "https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house#/schema/question/4",
"@type": "Question",
"inLanguage": "en",
"name": "What does the infrastructure need?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Node.js 22.12 or later with pnpm for builds and runtime, Redis 6 or later as cache, HTTPS, public reachability for the webhooks, and own domains. For health checks the storefront answers at /api/frontend/health.
"
}
}
]
}
```