Skip to main content
Every application you deploy on Virtus Cloud runs inside a resource-constrained container, and understanding those boundaries up front helps you choose the right plan and architect your project for stable, long-term performance. This page documents all current platform limits and explains the reasoning behind each constraint so you can make informed decisions about your deployment.

Minimum RAM Requirements

Virtus Cloud enforces minimum RAM allocations per project type to guarantee baseline stability. Insufficient memory leads to application crashes, poor response times, and degraded user experience — especially during traffic spikes. The minimums below reflect the typical footprint of each application category:

Bots

256 MB minimum RAM. Suitable for lightweight Discord or Telegram bots with moderate command sets.

Websites & APIs

512 MB minimum RAM. Required to handle concurrent HTTP connections and framework overhead.

Cache Databases

512 MB minimum RAM. Ensures stable in-memory key-value store operations (e.g., Redis-compatible).

General Databases

1 GB minimum RAM. Required to manage query processing, indexing, and connection pooling reliably.
While Virtus Cloud supports plans with up to 1 TB of RAM, the maximum RAM allocation per individual application is 32 GB. If your workload requires more than 32 GB, contact the support team to discuss custom configurations.

CPU Allocation Logic

CPU allocation follows a dynamic model designed to maximize efficiency across the platform while protecting shared infrastructure from runaway processes. The logic works as follows:
If your plan’s default CPU allocation is 1 vCPU, your application receives the full vCPU without any reduction.
CPU is set to the maximum of either half the default allocation or 1 vCPU, whichever is higher. This prevents very small containers from receiving zero effective compute.
CPU is set to exactly half of the default allocation. This range is considered transitional and receives a proportional reduction.
Applications with 2 GB or more of RAM receive the full default CPU allocation without any division. At this scale, the platform considers your workload to be production-grade.
This strategy balances fair resource distribution across all tenants while ensuring that larger, higher-priority applications get the compute they need. Cryptocurrency mining and similar CPU-intensive abuse workloads are explicitly prohibited and will trigger the LACK_OF_CPU shutdown.

Network Speed Limits

Network throughput scales linearly with your RAM allocation at a rate of +50 Mbps per additional 256 MB of RAM. This design ties bandwidth to the size of your workload, ensuring that high-traffic applications receive proportionally more network capacity.
RAM AllocationNetwork Speed
256 MB50 Mbps
512 MB100 Mbps
1024 MB200 Mbps
2048 MB400 Mbps
4096 MB800 Mbps
8192 MB1600 Mbps
10240 MB2000 Mbps
If your application requires network speeds above 2000 Mbps, contact the support team to discuss your requirements.

Storage Limits

Each project — regardless of type or plan — is allocated a fixed storage quota:
  • All projects: 10 GB of persistent storage per project.
This quota covers your application files, logs, and any data written at runtime. Files that Virtus Cloud automatically removes during deployment (such as node_modules, .git, and .venv) do not count against your quota. See the Files Automatically Removed During Deployment page for the full list.

Service Enforcement Policies

Virtus Cloud monitors resource consumption in real time. When an application breaches a limit, the platform shuts it down automatically to protect the stability of neighboring applications on the same infrastructure.
If your application consumes more RAM than the value specified in your virtuscloud.app config file, it is flagged for a LACK_OF_RAM violation and shut down immediately. To resolve this, increase the MEMORY value in your config file or upgrade to a higher plan.See the LACK_OF_RAM troubleshooting guide for step-by-step resolution.
If your application sustains CPU usage beyond its allocated processing limit, it is flagged for a LACK_OF_CPU violation and shut down. Common causes include infinite loops, inefficient algorithms under load, and cryptocurrency mining — which is explicitly prohibited on the platform.See the LACK_OF_CPU troubleshooting guide for step-by-step resolution.
Hosting applications that mine cryptocurrencies or perform other sustained CPU-abuse workloads is a direct violation of the Virtus Cloud Terms of Service and will result in immediate application termination and potential account suspension.