Core 48 Max
Core 48 Max doubles the memory and brings two 15.36 TB NVMe drives to the 48-core EPYC. It is the package for a multi-terabyte Postgres or ClickHouse, for Elasticsearch clusters that have outgrown their heap, or for memory-hungry analytics that used to need a dozen cloud nodes.
No setup fee. Monthly billing, three-month minimum, then cancel with 30 days notice. Delivery within 48 hours.
- Processor
- AMD EPYC 9454P
- Cores
- 48 cores / 96 threads
- Memory
- 512 GB DDR5 ECC
- Storage
- 2 × 15.36 TB NVMe (mirrored)
- Network
- 10 Gbit, 20 TB included
- Response
- Engineer within 30 min
Datasheet
Exact configuration as delivered. Variants within a series are quoted individually.
- Processor
- AMD EPYC 9454P, 48 cores / 96 threads, Zen 4
- Memory
- 512 GB DDR5 ECC registered
- Storage
- 2 × 15.36 TB NVMe SSD, datacentre edition, software mirror (RAID 1)
- Usable capacity
- about 14 TB after mirroring and filesystem overhead
- Network
- 10 Gbit uplink, 20 TB outbound per month included, then €1 per TB
- Addresses
- 1 IPv4 and a /64 IPv6 block; private VLAN
- Location
- Germany (Falkenstein or Nuremberg) or Finland (Helsinki)
- Operating system
- Ubuntu LTS, Debian or Rocky Linux, hardened to the Infraexa baseline
- Database tuning
- Postgres, MySQL and ClickHouse memory and I/O profiles applied and reviewed quarterly
- Backups
- Nightly encrypted snapshots to a second site, 30-day retention; point-in-time recovery for Postgres on request
- Incident response
- Critical issues answered by an engineer within 30 minutes, around the clock
What Core 48 Max is for.
Workloads this configuration has been sized for, and what it adds beyond the standard layer.
Best for
- Postgres or MySQL beyond 2 TB
- ClickHouse and analytics warehouses
- Elasticsearch and OpenSearch clusters
- Redis or in-memory caches at scale
Included beyond the standard layer
- Point-in-time recovery for Postgres on request
Included with every package.
Nothing on this list is an upsell.
Guides for this kind of server.
Dedicated servers vs cloud for a SaaS with a €20,000 monthly bill
A worked migration of a typical SaaS from hyperscaler instances, managed database and egress to a few dedicated servers, with the before-and-after numbers.
Read the guideSizing a dedicated server for Postgres: cores, memory, NVMe
How to pick memory, storage and CPU for production Postgres on dedicated hardware, and why one 48-core NVMe server replaces a lot of managed database spend.
Read the guideOther packages.
- Core 48Core
48 Zen 4 cores, 256 GB and fast NVMe for your main application tier.
- CPU
- 48 cores / 96 threads
- Memory
- 256 GB DDR5 ECC
- Storage
- 2 × 3.84 TB NVMe (mirrored)
€2,540per month - Store 300Store
308 TB of raw disk behind 15 TB of NVMe cache, run as object or block storage.
- CPU
- 32 cores / 64 threads
- Memory
- 256 GB DDR4 ECC
- Storage
- 14 × 22 TB HDD + 2 × 7.68 TB NVMe
€3,290per month - Enterprise 48Enterprise
Core 48 compute in an enterprise chassis with redundant power and four hot-swap NVMe bays.
- CPU
- 48 cores / 96 threads
- Memory
- 256 GB DDR5 ECC
- Storage
- 4 × 3.84 TB NVMe (hot-swap)
€3,860per month - Accel 96Accel
A 96 GB Blackwell GPU with 512 GB of system memory, ready for inference day one.
- CPU
- 24 cores / 48 threads
- Memory
- 512 GB DDR5 ECC
- GPU
- NVIDIA RTX PRO 6000 Blackwell, 96 GB
€6,780per month - Cluster 3Cluster
Three 48-core nodes on a private network with highly available Kubernetes and Postgres.
- CPU
- 144 cores / 288 threads total
- Memory
- 384 GB DDR5 ECC total
- Storage
- 6 × 1.92 TB NVMe total
€9,850per month
Ready to run Core 48 Max? Tell us about the workload.
A quote within one business day. €4,120 per month with everything included, no setup fee.