Servers & Token System
PNET Cloud Racks provides enterprise-grade virtual lab environments powered by high-performance servers. Each server type is based on the maximum RAM allocation available for your virtual networking lab.
How the Token System Works
Tokens are used to reserve server runtime hours. Every server type consumes a different number of tokens per hour based on the RAM allocated to the server.
The minimum booking duration is 1 hour. Tokens are consumed automatically according to the selected server type.
CPU and storage (HDD/SSD) requirements do not need to be manually selected. Our platform automatically allocates the required CPU cores and storage resources based on your lab topology.
| Server Type | Token Usage |
|---|---|
| 16GB Server | 1 Token per Hour |
| 32GB Server | 2 Tokens per Hour |
| 48GB Server | 3 Tokens per Hour |
| 64GB Server | 4 Tokens per Hour |
| 80GB Server | 5 Tokens per Hour |
| 96GB Server | 6 Tokens per Hour |
| 112GB Server | 7 Tokens per Hour |
| 128GB Server | 8 Tokens per Hour |
Practical Examples
Below are a few practical examples showing how the token system works with different server sizes and runtime durations.
Example 1 - Basic Lab Usage
A user selects a 16GB Server for a small networking lab. Since the 16GB Server consumes only 1 Token per Hour, purchasing 10 Tokens allows the lab to run for approximately 10 Hours.
Example 2 - High Performance Lab
A larger enterprise or cybersecurity lab may require an 80GB Server. This server consumes 5 Tokens per Hour, meaning that a balance of 10 Tokens allows the environment to run for approximately 2 Hours.
Example 3 - Switching to a Higher RAM Server
A user may initially start a lab using 10 Tokens a 16GB Server and run it for 4 Hours, consuming 4 Tokens. The remaining balance of 6 Tokens can later be used to switch to a 32GB Server, which consumes 2 Tokens per Hour. This allows the upgraded server to run for 3 Hours.
Example 4 - Switching to a Lower RAM Server
A user may also need to reduce server size based on his lab requirements. For example, 10 Tokens with a 96GB Server running for 1 Hour consumes 6 Tokens. The remaining 4 Tokens can then be used on a 32GB Server, which consumes only 2 Tokens per Hour, allowing the lab to run 2 Hours.
This flexible token system allows you to scale your lab environment up or down depending on your topology requirements while paying only for the server resources and runtime duration you actually use.
Token Calculator
Estimate the recommended server size and tokens required for your lab topology.