CDN
Your storefront runs somewhere. Its media does not have to run in the same place. The Laioutr CDN is a managed store and delivery path for the images and video an editor picks in Studio, available on every hosting option: Laioutr Cloud, a hyperscaler, a native host, or your own server.
What it gives a project
- Its own bucket. Every project gets a dedicated object store. There is no shared namespace between projects, so isolation is a property of the infrastructure rather than of key-handling code.
- Its own delivery hostname. Assets are served from
{projectId}.cdn.laioutr.cloudby default. A branded hostname such ascdn.example.comcan be attached instead. - Transformations at the edge. Images are resized, re-encoded, and format-negotiated on request. Video is resized and posters are extracted from the same path.
- Long-lived edge and browser caching. A delivered object is cached immutably, so a repeat view costs no origin fetch.
- A media library in Studio. The CDN appears as a picker in Cockpit through the
@laioutr-app/cmsconnector, next to any other connected library. See Media and Media Library.
Enabling it
Open Integrations in Cockpit, enable Laioutr CMS, then redeploy the storefront. Provisioning creates the bucket, attaches the delivery hostname, issues the project key, and adds @laioutr-app/cms to the project's apps. The card shows the delivery host once it is live.
Pages
Webhook Configuration
Integrate your own hosting solution into Laioutr by setting up a webhook. Cockpit calls this webhook for every deployment-related action.
Video CDN
How the Laioutr CDN stores, transforms, and delivers video, what the upload envelope allows, and which seams let you put an adaptive-streaming provider behind the same storefront components.