Fair use
The limits page lists what the platform enforces. This page lists what it does not enforce, but watches. Nothing here throttles or stops your storefront. Going beyond an allowance starts a conversation with us.
Never serve video from a storefront
A storefront must not serve video files, and large downloads must stay a small share of its traffic. Every storefront on Laioutr Cloud is delivered through one content delivery network, and that network's terms of service restrict video and a disproportionate share of large files for all of its customers at once. One storefront that serves video puts the delivery of every other storefront at risk.
Deliver video through a video service built for it and embed the player in your storefront. Product images, fonts and your build's own scripts and styles are not affected.
This is the one item on this page we act on within a working day.
Not permitted
Besides video, a storefront must not be used to mine cryptocurrency, to run a proxy or VPN, or as file storage for downloads unrelated to the shop.
Monthly allowances
| Per calendar month | S | M | L |
|---|---|---|---|
| Data sent from your storefront's servers | 2 TB | 5 TB | 12 TB |
| Video | none | none | none |
| Share of delivered data in responses over 10 MB | 10 % | 10 % | 10 % |
| Build minutes | 300 | 600 | 1,500 |
| Builds | 100 | 200 | 500 |
Data sent from your storefront's servers is what your pods send: rendered pages, API responses, and each static file the first time a delivery location requests it. Your build's scripts, styles and public images are cached at the edge, so a visitor's second request for them does not count. Traffic the edge serves from its cache has no allowance.
All traffic that reaches your storefront's servers counts, whatever sent it: visitors, search engine crawlers, AI agents and scrapers alike. If automated traffic drives your usage, we show you its share and help you limit it.
Page views and CPU are not in this table. Your plan already fixes them: an S storefront gets slower under a spike, and an M or L storefront stops adding pods at its ceiling. See running storefronts.
Requests have no allowance. We watch them for anomalies, such as a single client or a single path that dominates your traffic, and tell you when we see one.
When a storefront exceeds an allowance
- We see it first. We watch each storefront's usage against these allowances.
- We contact you with the numbers: which allowance, by how much, and what drives it.
- We look for a fix together. Most overruns have a cause that costs nothing to remove — a response that is not cached, a large file that belongs elsewhere, a crawler you did not expect.
- If the traffic is real and lasting, we talk about a larger size class or plan.
A storefront is never throttled, paused or deleted automatically for exceeding an allowance on this page.
Changes to this page
We can change an allowance on this page. If we lower one, we tell you in advance and say why.
Limits
Every limit Laioutr Cloud applies to a build and to a running storefront — what the value is, what happens when you reach it, and what to do about it.
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.