An AMD EPYC foundation for your Swiss server stack. Choose the network variant, memory and storage around parallel applications, virtual environments or data-heavy services that fit the listed hardware.
An AMD EPYC 7452 dedicated configuration with 64 GB of DDR4 memory and a 1 TB NVMe drive. A 10 Gbps port is paired with a 100 TB traffic allowance.
Move to a 25 Gbps port while keeping a 100 TB traffic allowance. The dedicated AMD EPYC 7452 platform includes 64 GB of DDR4 memory and a 1 TB NVMe drive.
The 10 Gbps EPYC configuration with unmetered traffic, using an AMD EPYC 7452 processor, 64 GB of DDR4 memory and 1 TB of NVMe storage.
The broadest EPYC network allocation combines a 25 Gbps port with unmetered traffic. Its hardware specification includes an AMD EPYC 7452 processor, 64 GB of DDR4 memory and a 1 TB NVMe drive.
Compare the listed specifications and base prices. Final availability, delivery and applicable tax are confirmed on your quote. Illustrations are conceptual.
Understand what makes this service family useful.
The range lists an EPYC 7452 processor foundation. Check application support and workload behaviour when comparing it with the Intel server families.
The EPYC plans list NVMe primary storage. Additional drive selections have their own descriptions and should be reviewed separately.
Compare port speed and metered or unmetered traffic combinations. Choose the transfer model that suits the application rather than selecting speed alone.
Select the listed RAM upgrades, address allocation and operating environment. Optional hosting licences remain distinct from the physical resources.
Run a workload that can distribute useful work across the processor, after checking its actual CPU and memory needs.
Evaluate the listed hypervisor options for a private environment with deliberate resource allocation and restricted administration.
Combine primary NVMe storage with a suitable network variant for applications that process and move significant datasets.
Software uses processor resources in different ways. A service with one busy thread and a batch job with many independent tasks may favour different configurations. Compare your application's compatibility and measured behaviour against the listed EPYC platform instead of relying on a generic performance claim.
The EPYC base plans list NVMe storage, but the amount of data you can serve also depends on the application, network and traffic model. Review the port and allowance together. Additional-drive choices can expand capacity; their labels identify the storage being added.
A dedicated server can support several applications or virtual environments, each with its own access needs. Decide who handles the host, guest systems, software and backups. A Swiss location and no-KYC order flow sit alongside these controls, while secure operation depends on how you configure the stack.
For virtualisation, databases, scientific processing or business applications, verify the software against the EPYC model and the selected memory and storage layout. The physical-server plan lists five IPs; confirm root or administrator credentials, recovery-console access, IPv6 and network protection before delivery. Hardware stock, reinstall methods and later upgrades need a specific operator-approved procedure.
Available choices depend on the selected configuration. See included selections and option prices in the configurator.
Specific answers for this service family.
Compare the network port and traffic model in the table. Review all specifications and options before choosing, even when the base CPU and storage appear similar.
The primary storage is listed as NVMe. Read the separate additional-drive labels; they may specify SSD storage without describing it as NVMe.
No universal benchmark is claimed. The benefit depends on software compatibility, parallelism and the workload's CPU, memory and storage limits.
Yes. The Metal families include Intel configurations. Compare the complete hardware, network and software requirements rather than choosing only by processor brand.
Verify the selected hypervisor's requirements, plan resource allocation and secure host administration. Include guest backups and recovery procedures before running production services.
No. The EPYC specification describes a CPU platform. Accelerated workloads need a separately listed GPU and compatible software; compare Tensor if an accelerator is part of the requirement.
Confirm root or administrator credentials and a secured IPMI or equivalent console. Bare-metal hardware does not itself verify a delivered remote-management workflow.
The plans list five IPs and optional additional blocks. Confirm IPv6 allocation and baseline network protection separately before relying on them.
They require operator validation for the actual server. Review image support, disk compatibility and any maintenance window; a listed configuration does not establish current stock or instant reinstalls.
Understand what a physical machine changes, what it does not change, and when it becomes a useful step for your workload.
Read the guideSeparate network reachability, authentication and privilege, then verify a recovery route before tightening remote access.
Read the guideSecure administration, expose only required services and establish updates and recovery without locking yourself out.
Read the guideChoose your resources. Keep control of your identity.