Limits

Every figure on this page is enforced by the platform. Where a limit depends on your plan, the plan column says so.

Builds

A build runs on its own node, which is destroyed when the build ends. It reaches the internet the way a build does anywhere else — your own registry, a Git dependency, a postinstall script that fetches a prebuilt binary all work. It cannot reach anything inside the platform: no other tenant, no node, no metadata service.

Your environment variables are readable by everything that runs during the build, including the install scripts of every package you depend on. That is true of every build platform. Give a build only the credentials it needs.

Running storefronts

A size class fixes the shape of one pod. On M and L, how many pods you get follows from the page views your plan covers, so a larger plan on the same class means more pods, not bigger ones. S is one size whatever its page views: two pods, and a third under load.

On M and L, up to a few million page views a month the minimum of three pods already covers the traffic. Above it the count grows with your allowance.

S adds one pod under load, never more. A spike beyond three pods makes an S storefront slower and never more expensive. M and L add pods up to a ceiling derived from your page-view allowance.

An S storefront runs at least 2 pods, M and L at least 3, and the platform spreads them across separate machines wherever the cluster has machines to spread them over.

The JavaScript heap is 75 % of the memory ceiling; the rest is for Node itself. A storefront that outgrows it stops with JavaScript heap out of memory and restarts.

Environments

Every environment other than production runs as a storefront of its own, on the class Laioutr chooses for it. It has the pod of S, adds no pods under load, and keeps one preview awake at once. While nobody visits it runs no pod at all: after 5 minutes without a request it sleeps, and the next request waits for it to start — about 4 seconds. An environment whose pod cannot start answers like a preview beyond the awake cap: it waits about 60 seconds and then gets 504. Its hostname is never indexed. The class cannot be changed, and environments are part of your license rather than billed by page view.

Per request

Outgoing requests

Your storefront can reach any public address. Pods on one machine share its outgoing IP address, so an upstream API that limits requests per IP counts your storefront together with others on the same machine. A fixed outgoing address is not available yet.

Configuration

There are no runtime environment variables. Your project's configuration is built into the image, so changing a value means a new deployment.

Storage and state

Write only to /tmp, and only as a scratch space. The writable disk in the table above is the ceiling; a pod that exceeds it is evicted. Nothing written by a storefront survives a restart, and pods are replaced routinely. The platform provides no file storage, so keep files in a service of your own.

The shared cache is a cache. It is one instance shared by every storefront on the platform, so an entry can be evicted at any time to make room for new ones, yours or another storefront's, and how long an entry stays depends on their traffic as well as yours. The cache starts empty after a restart. Never keep state there that you cannot rebuild.

The shared cache has two size limits.

A storefront reaches the shared cache at LAIOUTR_CACHE_URL, and may use only the keys and channels under LAIOUTR_CACHE_PREFIX:

A storefront cannot create a load balancer, open a node port, or claim a disk. Those are billable resources, and the platform creates none of them on your behalf.

Hostnames

Every storefront gets a permanent hostname of the platform's own from the day it is created, <name>.laioutr.app, and that hostname serves production whether or not you have connected a domain. Laioutr assigns the name when the storefront is created and keeps it for good, also when the project is renamed. Once one of your own domains is canonical, the platform hostname answers X-Robots-Tag: noindex, so the two never compete for the same content in search results.

Preview deployments

Every deployment has a hostname of its own, <name>-<9 characters>.laioutr.app, for as long as it is kept. A deployment that is no longer kept answers with a not-found page.

Rotating your project's content preview token withdraws the production deployments you replaced at once: none of them can be made live again without a new build.

A preview that nobody visits scales to zero after 5 minutes and wakes on the next request, so the first request to a cold preview is slower. Beyond the number of previews awake at once in the table above, a request to another preview waits about 60 seconds and then gets 504, until one of the awake previews sleeps. A preview whose pod cannot start answers the same way. Preview hostnames are never indexed.

Password protection

A protected hostname that cannot be checked — for example while the platform's protection store is unreachable — answers 503 with Retry-After. It never falls back to serving the page unprotected. A delivery path under /webhooks/ is never checked, so it answers as usual even then; What stays reachable says which paths count and why. Password protection explains how to set it up.

Metrics

Your storefront's own metrics — the HTTP, Node.js runtime and Laioutr metrics it sends over OpenTelemetry — and a copy of its traffic and container metrics are kept per environment: production and each other environment of your project count separately. The platform keeps its own record for billing separately; nothing on this page changes what you are billed.

The copy of your traffic and container metrics counts against the same series, sample and label limits as your own metrics. The platform also adds labels to every series your storefront sends — tenant, deployment, service, job, instance, and the instrumentation scope's otel_scope_name and otel_scope_version — and the metric name counts as a label too, so at least 22 of the 30 labels are left for your own attributes.

Logs

Your storefront's own logs — what its pods and builds write — are kept per environment, and so is a copy of the access log for your hostnames. The visitor's IP address is not in that copy.

Traces

Your storefront's traces — the spans it sends over OpenTelemetry — are shown per environment: every span is filed under the environment that sent it, and each environment sees only its own. Not every request is traced: one in four is traced at all, and of those every failed request and one in five of the others are kept. A request that arrives with a trace context of its own follows that context's choice instead of the one in four.

Reading your traces in Cockpit

Each environment hosted on Laioutr Cloud has a Slow requests page, and a page for each trace.

What counts as a page view

Your plan's allowance counts page views: pages a visitor's browser renders.

• Every full page load, once the page has loaded — the first page of a visit, a reload, a new tab — and every navigation inside the storefront to a different path.
• Not a change of only the query or the hash — a filter, a sort, a tab — and not an error page or a page the browser restores from its back-forward cache.
• Not a client whose user agent names a known bot, and not a client that runs no page JavaScript, as most scrapers do not.

Your storefront reports each page view with a small request of its own, POST /api/frontend/cloud/view, so a page served from the edge cache counts too. A visitor whose blocker stops that request is not counted, which only ever lowers your count.

For a day on which the platform received no such request at all, such as from a storefront whose build does not send it, the day's page views are the HTML pages the platform served to clients that are not known bots.

Suspension

A suspended storefront keeps its hostnames and its images, answers every request with a holding page, and runs no pods. Nothing is deleted.