About Backend Compute Limitations

Studio Two backend code runs in a managed backend infrastructure. To maintain platform stability and consistent response times, Wix enforces fixed resource allocations and runtime limits for backend execution.

Understanding these constraints lets you build resilient backend logic and choose the right architecture for compute-heavy or long-running tasks.

Note: These limits apply to all Studio Two sites, whether free or premium.

The following table summarizes the resource limits for all Studio Two sites:

LimitValueDescription
Instance allocation1 per data centerFixed single instance per data center with no auto-scaling.
CPU300 millicoresGuaranteed CPU per instance.
Memory400 MBMaximum RAM per instance.
Request timeout60 secondsMaximum runtime per HTTP request or backend call.
Instance uptime5 minutesWix recycles the instance after reaching this limit.

Instance allocation

Studio Two sites run a maximum of 1 backend instance per data center. Scaling is fixed, not dynamic.

To handle high-concurrency workloads effectively, minimize blocking operations and maximize use of asynchronous patterns in your code.

CPU

Each instance has 0.3 CPU cores reserved. If your code consistently exceeds this allocation, the platform throttles execution, which may reduce request throughput.

To avoid throttling, offload heavy computation to external processing pipelines where possible.

Memory

Each instance has a maximum of 400 MB of RAM. Attempting to buffer large data, read large files directly into memory, or maintain large in-memory caches can result in out-of-memory crashes.

To keep your memory usage under the 400 MB limit:

  • Stream data instead of loading it all at once.
  • Clear unneeded variable references promptly.

Request timeouts

HTTP endpoint handlers and other backend code have a maximum execution time of 60 seconds. If a request exceeds this limit, the platform aborts the request and returns a 504 gateway timeout error to the client.

To avoid timeouts, break large tasks into smaller units or delegate long-running work to external services.

The monitoring dashboard also displays failed requests.

Instance uptime

Individual instances have a maximum continuous uptime of 5 minutes. After reaching this limit, the infrastructure gracefully recycles the instance.

Because instances are periodically recycled, don't store state in global JavaScript variables or other local node memory. Use a persistent storage solution such as Wix Data or an external database instead.

Last updated: 2 November 2026

Did this help?