Intel TDX on the OpenMetal XL v5: Active Out of the Box

Q: Does the OpenMetal XL v5 support Intel TDX out of the box?

Yes — the OpenMetal XL v5 ships with Intel TDX active by default because the server’s 1024 GB DDR5-6400 configuration meets Intel’s RAM threshold for trust domain allocation without any customer upgrade.

Schedule a Consultation

Intel TDX requires a specific RAM configuration to activate trust domains. The XL v5 ships with 1 TB of RAM (16x 64 GB RDIMMs at one DIMM per channel, populating 16 of its 32 DIMM slots), which satisfies that threshold at deploy time. Unlike the Large v5 (which requires a RAM upgrade to enable TDX) or the Medium v5 (which can be upgraded to TDX-eligible), the XL v5 lands with TDX already on — no reconfiguration, no scheduled maintenance window, no second deploy.

Intel SGX is also active by default on the XL v5, providing process-level enclave isolation alongside TDX’s whole-VM trust domains. TME-MK (multi-key memory encryption) is active across the platform regardless of whether a workload runs inside a TD. Together, these give XL v5 customers a layered confidential computing posture from day one: SGX for small high-value secrets like signing keys, TDX for full guest-OS isolation, and TME-MK as a baseline AES-encrypted memory layer for everything else.

The Granite Rapids platform on the XL v5 also improves TEE performance over earlier generations. AMX, AVX-512, AES-NI, and DL Boost are all available inside trust domains, so confidential inference, confidential analytics, and confidential database workloads run at performance levels closer to bare metal than was practical on earlier TDX implementations. Customers running regulated financial workloads, healthcare PHI, sovereign cloud, or multi-tenant SaaS isolation use cases can launch attested trust domains on day one — configuration guidance is in the OpenMetal SGX/TDX enablement guide.

—-