Limitations
Nexaa’s serverless containers are designed to provide flexibility, scalability, and performance for containerized applications. However, to ensure reliability and efficiency across all tenants, the platform enforces a number of resource constraints. This page outlines the current limitations for CPU, memory, and networking.
Resource Limits Overview
| Resource | Limit | Scope |
|---|---|---|
| Container vCPU | Minimum: 0.25 vCPU Maximum: 12 vCPU Increment under 1 vCPU: 0.25 Increment above 1 vCPU: 1 vCPU |
Per Container |
| Container Memory | Minimum: 0.5 GiB Maximum: 16 GiB Increment under 1 GiB: 0.5 GiB Increment above 1 GiB: 1 GiB |
Per Container |
| Ingress Traffic | HTTP and HTTPS are supported by default. TCP and UDP are also supported, but require a request to enable. | Per Container |
| Ephemeral Storage | A container has 5GB of internal storage | Per Container |
| Persistent Storage | Minimum: 1GB Maximum: 100GB |
Per Volume |
Notes
-
Soft limits The limits are soft and can be increased upon request. Please contact support to initiate the process.
-
Container Resource Granularity:
Under 1 vCPU or 1 GiB memory, resource increments are smaller to support lightweight workloads. Beyond these thresholds, resources are allocated in whole units for performance consistency.