Veil Edge
Prepared network profile with the 10 Gbps mitigation allocation, anomaly detection and latency tuning. Validate its relationship to protection already included in the plan.
Give web applications, containers or a private tunnel two AMD EPYC virtual CPUs, 4 GB of ECC memory and 60 GB of NVMe storage. Root access on KVM, a 1 Gbps port and 3 TB of monthly transfer provide more room than the entry configuration without moving to dedicated hardware.
The exact allocation behind Umbra 2.
The tools and services included in this configuration.
Two AMD EPYC virtual CPUs and 4 GB ECC memory
60 GB NVMe storage
10 Gbps network mitigation tier
Full root access on KVM
Network details, software choices and the destinations compatible with this exact plan.
Prices, destinations and checkout details for this exact configuration.
Base prices in USD: $30.40 for one month; $155.04 for twelve months; $273.60 for twenty-four months. Longer-term monthly figures are equivalents. Selected extras are added separately to the full cycle total.
Umbra 2 lists these compatible destinations: Iceland · Switzerland · Netherlands · Romania · Moldova · Bulgaria · Russia · Panama. Choose from this plan’s own destination selector when configuring your order.
The listed choices for Umbra 2 are: Ubuntu · Debian · AlmaLinux · Rocky · Fedora · Whonix. Review the configuration notes for image, licence and compatibility restrictions.
Choose BTC, ETH, SOL, LTC, native TRX, USDT ERC-20, USDT TRC-20 or USDC ERC-20 after signing in. The server retrieves a USD market rate and creates a quote valid for 25 minutes. Match both the asset and network. Payment verification and service delivery are separate steps.
Review the full specifications, configuration notes and service objectives. Location, software, licence and optional-service restrictions belong to this exact configuration; a payment confirmation is separate from service delivery.
Practical details for Umbra 2, from setup to the choices ahead.
Open the knowledge centreThese are prepared service specifications. Infrastructure, licences and optional services require validation before a live launch.
Umbra 2 is a prepared OmbraHost configuration in the Virtual servers catalogue. Compute: 2 vCPU (AMD EPYC); Memory: 4 GB DDR4 ECC; Storage: 60 GB NVMe SSD; Transfer: 3 TB / month; Port: 1 Gbps. Read the full selected billing-cycle total separately. These are specifications, not measured performance or a provisioned service.
Umbra 2's prepared region list is Iceland, Switzerland, Netherlands, Romania, Moldova, Bulgaria, Russia, Panama. The configurator uses this exact list; catalogue compatibility does not establish live stock or reserve infrastructure.
The published templates are Ubuntu, Debian, AlmaLinux, Rocky, Fedora, Whonix. A custom image request needs review and does not add unsupported choices to the standard selector.
Back up the application and database, verify disk growth and recovery access, and confirm restart requirements. For Umbra 2, rely on the schedule expressly confirmed for this tier; a snapshot is not an independent backup.
The prepared Umbra range contains five KVM Linux VPS configurations with root access, from 1 to 16 vCPU, 2 to 32 GB RAM and 25 to 480 GB NVMe. Each lists eight compatible regions. The image, transfer allowance and snapshot inclusion belong to the exact plan; the local checkout creates no server.
KVM provides an independent guest kernel and root access. Kernel modules and containers remain subject to the selected image and enabled host capabilities.
The catalogue lists Ubuntu, Debian, AlmaLinux, Rocky, Fedora and Whonix. Custom ISO requests need eligibility checks; Windows belongs to the RDP catalogue.
The prepared specification includes one IPv4 address and IPv6. Additional IPv4 and larger IPv6 allocations require technical approval; they are not selectable live add-ons.
Umbra 4 includes a weekly snapshot; Umbra 8 includes daily snapshots. Verify the selected plan rather than assuming every tier includes the same schedule.
The intended upgrade path expands CPU, memory and disk. A restart or migration may be required; changing infrastructure class needs a separate transfer plan.
Docker and Podman use the guest kernel. Nested virtual machines require separately confirmed virtualisation support; running a container does not establish nested KVM availability.