Limits

Numeric limits and timeouts for serverlets, proxies, and DNS.

Technical limits and timeouts enforced by the platform. Most applications never hit these — they exist to keep the platform stable under load and to catch misbehaving configuration early.

Serverlet

LimitValue
Max instances per serverlet1,000
Max container image size3 GiB
Scale-to-zero cold start timeout20 seconds
Rolling update grace period10 seconds

If a serverlet with zero running instances receives a request, the proxy waits up to the cold start timeout for an instance to start before giving up and returning 504 Gateway Timeout. See Scaling to zero.

During a rolling update, an outgoing instance is given the grace period to finish in-flight requests before it’s stopped, regardless of whether it’s done.

Proxy

Request and response limits

LimitValue
Max request header size64 KB
Max response header size128 KB
Max size of a single header field32 KB
Max number of headers500

Timeouts

TimeoutValue
Connect timeout to backend10 seconds
Time waiting for backend to start responding30 seconds
Overall backend request timeout100 seconds
Idle connection timeout to backend90 seconds
Idle timeout on HTTP/3 (QUIC) connections30 seconds
Response write timeout30 seconds

Recursion

LimitValue
Max times a request can re-enter the platform3

A request can be forwarded back into the Futrou platform at most this many times before it’s rejected with 508 Loop Detected — this catches misconfigured proxies that end up routing to themselves, directly or indirectly. A proxy target that resolves back to the exact same instance already handling the request is blocked outright, regardless of this count.

Reserved headers

Request and response headers starting with Futrou- are reserved for platform use. Rules can’t add or modify a Futrou--prefixed header.

DNS

LimitValue
Max records per zone3,500
Max zone size2 MiB

Whichever of these two limits is reached first applies. See DNS for supported record types and zone management.

Last updated