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.
$4.75per month
Virtual serversYOUR CONFIGURATION / IN FULL
Umbra 4A space of your own.
Balance four AMD EPYC virtual CPUs and 8 GB of ECC memory with 120 GB of NVMe storage for several services or a growing application. This KVM configuration includes a weekly snapshot, 6 TB of monthly transfer on a 1 Gbps port and a 20 Gbps network mitigation tier.
8 compatible destinationsCrypto checkoutTailored before you order
01 / RESOURCES
Every resource, in focus.
The exact allocation behind Umbra 4.
- Compute
- 4 vCPU (AMD EPYC)
- Memory
- 8 GB DDR4 ECC
- Storage
- 120 GB NVMe SSD
- Transfer
- 6 TB / month
- DDoS protection
- 20 Gbps
- IPv4
- 1 included
02 / INCLUSIONS
More than the numbers.
The tools and services included in this configuration.
Four virtual CPUs and 8 GB ECC memory
20 Gbps network mitigation tier
Included weekly snapshot
Full root access on KVM
03 / YOUR ENVIRONMENT
The right foundation.
Network details, software choices and the destinations compatible with this exact plan.
The details behind your configuration
- Network port
- 1 Gbps
- Platform
- KVM
- IPv6
- /64 subnet
- Availability target
- 99.9%
Operating system options
Compatible deployment destinations
Configuration notes
- Custom x86-64 ISO installation is a separately reviewed request; the standard selector retains the listed images
- Docker and Podman use the selected guest kernel
- Nested virtualisation requires host-capability approval
- Larger /56 or /48 IPv6 allocations may be requested without an additional allocation fee, subject to technical approval
- Custom kernel modules depend on the selected guest kernel and its configuration
Service objectives
ProvisioningWithin five minutes after payment confirmation
Target in the prepared service specification; server delivery is tracked separately from payment confirmation.
YOUR PLAN / CLEAR ANSWERS
Before you choose.
Prices, destinations and checkout details for this exact configuration.
What is the complete billing-period price?
Base prices in USD: $60.80 for one month; $310.08 for twelve months; $547.20 for twenty-four months. Longer-term monthly figures are equivalents. Selected extras are added separately to the full cycle total.
Which destinations are compatible with this configuration?
Umbra 4 lists these compatible destinations: Iceland · Switzerland · Netherlands · Romania · Moldova · Bulgaria · Russia · Panama. Choose from this plan’s own destination selector when configuring your order.
Which software or operating-system choices are listed?
The listed choices for Umbra 4 are: Ubuntu · Debian · AlmaLinux · Rocky · Fedora · Whonix. Review the configuration notes for image, licence and compatibility restrictions.
How does cryptocurrency checkout work?
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.
What should I check before choosing this plan?
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.
A LITTLE MORE CLARITYKnow your
Know your
configuration.
Practical details for Umbra 4, 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.
VIRTUAL SERVERS / IN DETAIL11 useful answers
What does Umbra 4 specify?+
Umbra 4 is a prepared OmbraHost configuration in the Virtual servers catalogue. Compute: 4 vCPU (AMD EPYC); Memory: 8 GB DDR4 ECC; Storage: 120 GB NVMe SSD; Transfer: 6 TB / month; Port: 1 Gbps. Read the full selected billing-cycle total separately. These are specifications, not measured performance or a provisioned service.
Which locations are eligible?+
Umbra 4'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.
Which templates are listed?+
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.
What should I check before an upgrade?+
Back up the application and database, verify disk growth and recovery access, and confirm restart requirements. For Umbra 4, rely on a weekly snapshot; a snapshot is not an independent backup.
What is an OmbraHost Linux VPS?+
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.
Why choose KVM?+
KVM provides an independent guest kernel and root access. Kernel modules and containers remain subject to the selected image and enabled host capabilities.
Which images can I select?+
The catalogue lists Ubuntu, Debian, AlmaLinux, Rocky, Fedora and Whonix. Custom ISO requests need eligibility checks; Windows belongs to the RDP catalogue.
How are addresses allocated?+
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.
Which snapshots are included?+
Umbra 4 includes a weekly snapshot; Umbra 8 includes daily snapshots. Verify the selected plan rather than assuming every tier includes the same schedule.
Can the server grow?+
The intended upgrade path expands CPU, memory and disk. A restart or migration may be required; changing infrastructure class needs a separate transfer plan.
Can it run containers?+
Docker and Podman use the guest kernel. Nested virtual machines require separately confirmed virtualisation support; running a container does not establish nested KVM availability.