Skip to main content
Square Cloud implements container-based resource limits to ensure isolation, stability, and fair distribution of infrastructure across applications.

​
Minimum Resource Requirements

Each project hosted on the Square Cloud Platform has specific minimum resource requirements to ensure optimal performance:
  • Bots: Minimum of 256 MB RAM required.
  • Websites: Minimum of 512 MB RAM required.
  • Cache Databases: Minimum of 512 MB RAM required.
  • General Databases: Minimum of 1 GB RAM required.

​
Why do RAM minimums exist?

Containers have mandatory operational overhead: language runtime, OS libraries, and network buffers. Below 256 MB, the kernel’s OOM Killer tends to terminate processes during boot or garbage collection, making the application inviable. Technical implications:
  • Each container consumes 1 dynamic IPv4 and NVMe storage IOPS
  • Minimum allocations prevent resource fragmentation (noisy neighbor effect)
  • Daily snapshot formula: (Total RAM / 256) * 2 (approximate; the exact per-plan allowance may be lower on higher tiers)
Impact Data: After implementing the 256 MB minimum limit, application stability increased drastically, reducing the crash rate due to OOM (Out of Memory) by 97.7%.

​
CPU allocation

Short answer: CPU is allocated based on configured RAM. Increasing RAM typically grants more vCPUs.

​
Rules

​
Single vCPU plans

Applications on 1 vCPU plans receive full capacity without throttling.

​
Multicore plans (≥2 vCPU)

  • Performance floor: applications with ≥512 MB RAM receive at least 2 vCPUs.
  • Proportional scaling:
    • Hobby (≤2 vCPU): +1 vCPU per 512 MB RAM
    • Standard / Pro / Enterprise: +1 vCPU per 1 GB (1024 MB) RAM

​
Examples

Throttling and safety limits The system enforces the plan vCPU limit and applies leveling to keep distribution fair. Short-term elasticity may grant extra vCPUs during spikes but is not guaranteed. Prohibited CPU uses:
  • Cryptocurrency mining
  • Unrestricted, intensive ML workloads without authorization
  • Deliberate resource abuse
Violations result in LACK_OF_CPU status and immediate suspension.

​
Network limits

Bandwidth scales with RAM: +50 Mbps per 256 MB RAM. For requirements above 2000 Mbps contact support.

​
Storage limits

All projects receive 10 GB NVMe storage by default. Characteristics:
  • Enterprise-grade NVMe
  • Persistent across deploys and restarts
  • High IOPS and throughput

​
Limit exceeded statuses

​
LACK_OF_RAM

When: application exceeds allocated RAM or kernel signals OOM. Action: process is terminated immediately to protect host stability. How to fix:
  1. Find memory leaks with profilers (Node.js: --inspect, Python: memory_profiler).
  2. Reduce in-memory caches or move caches to Redis.
  3. Increase allocated RAM in the control panel.

​
LACK_OF_CPU

When: sustained CPU usage exceeds reasonable limits for the allocation. Action: process terminated with status LACK_OF_CPU. How to fix:
  1. Profile CPU hotspots (Node.js: 0x, Python: cProfile).
  2. Optimize hot loops, DB queries and I/O-bound operations.
  3. Increase RAM to obtain more vCPUs (see CPU allocation table).
  4. Offload heavy work to asynchronous workers or batch jobs.
Trade-off: increasing RAM to gain CPU raises costs. Measure whether code optimization is cheaper than scaling up.