Service status & availability Crypto-only billing · No-KYC signup

EPYC bare metal

EPYC 9354P dedicated server

A 32-core configuration with 384 GB DDR5 memory and paired NVMe, from $359 per thirty-day term.

ProcessorEPYC 9354P
Compute32c / 64t
Memory384 GB DDR5
Storage2×7.68 TB NVMe
Network10 Gbps unmetered
AddressingIPv4 /29 · IPv6 /64

What this configuration is suited to

EPYC 9354P balances dedicated compute with local NVMe. Choose it when predictable CPU scheduling, fixed transfer cost and direct control of the operating system matter more than minute-by-minute elasticity.

Included with the server

  • Unmetered network port
  • IPv4 /29 block
  • IPv6 /64 allocation
  • Full IPMI/KVM access
  • Baseline DDoS protection

Operating systems

Ubuntu, Debian, Rocky Linux, AlmaLinux, Windows Server, Proxmox VE, VMware ESXi, TrueNAS, pfSense, Custom ISO. Commercial software licenses are not included unless stated on an order.

Available locations

Run it in Dallas, Ashburn or Portland.

Provisioning estimates can vary by hardware availability. A final region check happens before the ledger is debited.

Before you choose

Where this configuration makes sense.

2 min guide

Choose more memory when it is the observed constraint

The EPYC 9354P offer is a candidate when the EPYC 7513 leaves too little memory headroom but additional cores are not the main requirement. Both list the same core count; the memory allocation and platform differ. That makes the comparison especially useful for memory-heavy services or a defined group of guests.

Measure the active working set and peak allocations rather than using installed data size as a substitute. Include host overhead, concurrent maintenance and expected growth. Extra memory should resolve a concrete requirement, not conceal an application leak or uncontrolled retention.

Understand the fewer, larger device layout

This configuration uses two large NVMe devices with 15.36 TB combined raw capacity. The EPYC 7513 reaches the same raw total with more devices. Equal raw capacity therefore does not mean an identical storage design or the same options for separating workloads.

Agree redundancy before installation. A two-device mirror leaves one device’s nominal capacity before overhead, while using both for data changes the failure exposure. Confirm drive characteristics and controller presentation if the application depends on a particular storage behavior.

Keep consolidation and recovery in the same budget

A larger memory allocation may let more workloads share one host, but each additional service also increases the amount that depends on that host. Identify recovery priorities and where critical services will run if the machine becomes unavailable.

Use the 10 Gbps port as a planning input, not a promised restore rate. Test the path to the backup location and the receiving system. The time to recover a larger consolidated environment can matter more than its quiet-period utilization.

Confirm required features and the next sizing step

The listing describes a DDR5 configuration. Confirm any mandatory installed memory feature, module arrangement or application qualification before ordering; do not infer the complete delivered specification from the processor family alone.

Stay with EPYC 7513 if its memory allocation is enough and its four-device layout better matches the design. Compare EPYC 9554 when both core and memory demand justify a larger host. Keep operating-system version, initial access, independent backup and migration requirements explicit whichever configuration wins.

Direct answers

Questions before you order

Does this have more cores than the EPYC 7513 offer?

The current offers list the same core count. The 9354P configuration changes the memory allocation and platform, and uses a different NVMe device arrangement.

Can I assume ECC is installed because this is EPYC?

Confirm that requirement for the exact rental. A CPU family or DDR5 label is not a substitute for a verified installed-memory specification.