Limits
Every figure on this page is enforced by the platform. Where a limit depends on your plan, the plan column says so.
Builds
| Limit | Value | What happens |
|---|---|---|
| Duration | 20 minutes | The build is stopped and the deployment fails. A build that runs this long is stuck — a working storefront build finishes in single-digit minutes. |
| Retries | none | A failed build is not retried. Fix the cause and deploy again. |
| CPU | 7 vCPU, dedicated | The build has a node to itself. |
| Memory | 12 GiB | Node exits with a heap error. The build runs with --max-old-space-size=8192. |
| Project bundle | 250 MB | The deployment is refused with payload_too_large before the build starts. |
| Concurrent builds | 4 per platform | A fifth build waits. It is not queued on a node, so it costs nothing while it waits. |
| Log retention | 1 hour after the build ends | Read the logs through the deployment API before then. |
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. 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 | M | L | |
|---|---|---|---|
| CPU reserved | 0.5 vCPU | 1 vCPU | 1 vCPU |
| CPU ceiling | 2 vCPU | 2 vCPU | 2 vCPU |
| Memory reserved | 768 MiB | 768 MiB | 1536 MiB |
| Memory ceiling | 2 GiB | 2 GiB | 3 GiB |
| Writable disk | 1 GiB | 1 GiB | 2 GiB |
| Adds pods under load | no | yes | yes |
| Preview deployments awake at once | 5 | 5 | 10 |
S does not scale out. A spike makes an S storefront slower and never more expensive. M and L add pods up to a ceiling derived from your page-view allowance.
Every storefront runs at least 3 pods, so a single node failing never takes a storefront down.
Per request
| Limit | Value | What happens |
|---|---|---|
| Request timeout | 300 seconds | The gateway answers 504. |
| Rate limit | derived from your class and pod count | Excess requests get 429. It sits at roughly twice what your pods can serve, so ordinary traffic never reaches it. |
| Shutdown grace | 60 seconds | An in-flight request finishes while a pod is replaced. |
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. Persistent state belongs in your cache or in object storage, both of
which the platform provides.
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.
Preview deployments
Every deployment keeps a hostname of its own, and old deployments stay reachable for inspection. 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. Preview hostnames are never indexed.
Suspension
A suspended storefront keeps its hostnames and its images, answers every request with a holding page, and runs no pods. Nothing is deleted.
Laioutr Cloud
Laioutr Cloud is the built-in hosting and delivery environment for frontends created with Laioutr. It provides a ready-to-use infrastructure layer, so you can launch and operate your storefront without having to set up your own hosting, deployment pipelines, or runtime configuration.
Hyperscaler
While Laioutr Cloud provides a built-in default hosting environment, Laioutr is designed to remain fully extensible for teams with their own infrastructure and deployment requirements.