COMPUTE
NODES.
Dedicated High-Frequency vCores. Unmanaged VDS infrastructure. Strictly enforced 1:1 allocation without overprovisioning.
BASE
NODE.
Deploying on Ryzen™ 7 9700X
-
vCores1x PINNED 1:1
-
Memory4GB DDR5
-
Storage40GB GEN4 NVMe
-
Network500 Mbps Unmetered
-
IP Addr1x IPv4 Dedicated
-
VirtualFull KVM Access
PRO
NODE.
Deploying on Ryzen™ 7 9700X
-
vCores2x PINNED 1:1
-
Memory8GB DDR5
-
Storage80GB GEN4 NVMe
-
Network500 Mbps Unmetered
-
IP Addr1x IPv4 Dedicated
-
VirtualFull KVM Access
CORE
NODE.
Deploying on Ryzen™ 7 9700X
-
vCores4x PINNED 1:1
-
Memory16GB DDR5
-
Storage160GB GEN4 NVMe
-
Network1 Gbps Unmetered
-
IP Addr1x IPv4 Dedicated
-
VirtualFull KVM Access
PINNED VCORES.
Many virtualized environments rely on hardware oversubscription. We map vCores 1:1 to physical capacity, pinning them directly to your instance. Your compute resources are entirely isolated. To maintain performance standards, deployments are suspended when a hypervisor reaches its strict physical capacity.
Clock Speed
5.0GHz+ BOOST
Memory Guard
DDR5 ECC
I/O Performance
GEN4 NVMe
Transit
UNMETERED
ADDONS.
We enforce strict utilization policies. Additional addresses require technical justification and are statically routed directly to your hardware interface. No NAT overhead.
Strictly mapped to the node interface.
SNAPSHOTS &
BACKUPS.
VirtFusion snapshot slots for manual or automated rollbacks. Retention is hard-capped on our end. For long-term archival, you will need to configure your own remote backups.
- 1 Backup Slot
- No Automation
- 2 Backup Slots
- No Automation
- 3 Backup Slots
- Scheduled Execution
- Setup Required in Panel
DDOS MITIGATION.
All servers are protected by a global filtering network. L3/L4 volumetric attacks are detected and mitigated automatically. We do not charge additional transit fees for mitigated traffic.
Capacity
17+ Tbps
Global Network
Activation
Automatic
Detection
Billing
Unmetered
Zero Overages
Protection
L3/L4
Mitigation
INTEGRITY RULES.
We do not sell more vCores than the hardware provides. When our clusters are full, deployment closes.
Your threads are pinned 1:1 to the instance. Code executes natively without waiting on shared virtualization queues.