Confidential Computing for AI Training: How to Protect Models and Data on Bare Metal

Training AI models often involves sensitive data and valuable intellectual property. Whether you’re building proprietary machine learning models or analyzing confidential datasets, keeping that information secure throughout the training process is essential. Confidential computing protects data at every stage—when stored, in transit, and during processing.

This post explores how you can use confidential computing—specifically Intel TDX and bare metal infrastructure—to secure AI training workloads. If you already know the basics, check out OpenMetal’s blog on practical deployments or on balancing security and speed.

Why AI Models and Training Data Need Protection

AI models are incredibly valuable—often reflecting years of development and unique intellectual property. When businesses train these models, they often rely on proprietary data that might include sensitive personal information, competitive insights, or financial details. This type of data attracts attackers, which is why teams must protect it throughout the entire AI lifecycle.

Even if encryption is used during storage or transmission, a major gap remains: what happens when the data is being processed? In traditional virtualized environments, it’s possible for insiders or misconfigured systems to expose active memory. That’s where confidential computing plays a key role—protecting the training process itself.

How Confidential Computing Helps

Confidential computing creates a trusted execution environment (TEE) around the workload. This isolates it from the rest of the system—even the hypervisor and root users. With Intel TDX, which is supported by OpenMetal’s infrastructure, you can run secure virtual machines that shield your AI models and data while in use.

This is especially important for training large language models, recommendation systems, or predictive algorithms that rely on confidential or high-value data. By using TEEs, organizations gain confidence that the data will remain protected throughout the process—even if they’re deploying in a shared or multi-tenant environment.

What You Need for Confidential Computing in AI Training

To successfully run confidential computing workloads for AI training, your infrastructure must meet several key requirements—starting with the right hardware. At the foundation are Intel 5th Gen Xeon CPUs with Intel Trust Domain Extensions (TDX). These processors enable hardware-based memory encryption and ensure that sensitive data used in training models stays protected, even while in use.

At OpenMetal, both our XL V4 and XXL V4 bare metal servers are equipped with TDX-capable CPUs. This gives you the ability to isolate memory and workloads at the hardware level, which is essential for truly confidential computing environments.

Once you have the hardware in place, you’ll need a way to create secure virtual machines. Using hypervisors like KVM or QEMU, which are compatible with Intel TDX, you can launch TDX-enabled VMs that keep data fully isolated from the host system and other tenants.

AI workloads also generate and process huge volumes of data, so fast, secure storage is a must. With encrypted NVMe storage, OpenMetal ensures your training data stays protected while delivering high-speed performance—even in cases of drive loss or unauthorized access.

For those who require GPU acceleration during training, OpenMetal offers H100 GPUs that can be attached to TDX-enabled virtual machines using PCIe passthrough—but this configuration is available only on the XXL V4 bare metal server. This server provides the right balance of compute power, memory capacity, and hardware support to run both Intel TDX and GPU passthrough simultaneously.

This setup handles demanding AI workloads like deep learning exceptionally well, delivering both security and performance at scale.

Lastly, network isolation is critical—especially for customers dealing with compliance or privacy regulations. OpenMetal provides dedicated VLANs to separate your traffic from other workloads, helping to reduce risk and maintain a clean, segmented network environment.

Example Use Case

An OpenMetal customer in the blockchain space provides a helpful comparison. Their platform manages validator workloads and real-time transaction indexing. While they’re not training AI models, their infrastructure has similar security and performance needs: consistent compute, strict data separation, and hardware-level trust.

They use OpenMetal’s XL V4 servers with Intel TDX to launch secure VMs, isolate data with VLAN segmentation, and use encrypted volumes for sensitive blockchain metadata. The same environment is ideal for AI teams training proprietary models, especially if those models support financial, medical, or compliance-focused products.

Final Thoughts

Confidential computing is no longer experimental—it’s ready for production. If you’re training AI models with proprietary data, using Intel TDX on OpenMetal’s bare metal servers gives you the security and performance you need. If you’re ready to adopt confidential computing for AI training, OpenMetal’s Intel TDX-enabled infrastructure gives you a secure foundation to begin.

Contact us to learn how to start building your confidential AI training environment today.

Read More on the OpenMetal Blog

Utilization Is a Tenancy Decision: Why Sustained MFU Lives Below the Kernel

On latency-bound inference, the Model FLOPs Utilization your optimization stack can actually hold is capped by who else shares the box, not by the kernel that runs on it. Sustained

The Real Cost Math Behind Self-Hosted GitHub Actions Runners

We work through the actual cost crossover between GitHub-hosted Actions runners and self-hosted runners on dedicated bare metal, using GitHub’s current 2026 rates, correct a common misconception about a self-hosted runner fee that never took effect, and cover what a self-hosted build pipeline needs beyond just cheaper compute.

Comparing OpenMetal, Hetzner, and OVHcloud for Proxmox VE Hosting

We compare three dedicated server providers commonly considered for Proxmox VE hosting, OpenMetal, Hetzner, and OVHcloud, across real hardware specs, current pricing, storage architecture, and support model, so you can match the provider to your actual workload rather than just the sticker price.

Infrastructure for Post-Quantum Cryptography and Crypto-Agility

We look at why post-quantum cryptography has moved from a research topic to a binding compliance deadline, why “harvest now, decrypt later” makes this an infrastructure problem today rather than a future one, and why crypto-agile key management needs hardware you control directly.

Infrastructure for GENIUS Act Stablecoin Reserve and Redemption Systems

We look at what the GENIUS Act actually requires of payment stablecoin issuers, why reserve tracking, redemption, and transaction monitoring systems need dedicated and auditable infrastructure rather than shared platforms, and where that requirement does and doesn’t touch broader blockchain infrastructure.

What US CLOUD Act Jurisdiction Means for Your Singapore Infrastructure

We answer a specific legal question that general Singapore sovereignty content doesn’t: whether US CLOUD Act jurisdiction reaches infrastructure physically hosted in Singapore, how that’s separate from Singapore’s own PDPA framework, and what that means if you’re evaluating a US-owned infrastructure provider for APAC deployment.

Self-Hosting an AI Agent Code Execution Sandbox on Bare Metal

We explain why AI agents that execute code need microVM-level isolation, why that isolation requires direct hardware access that public cloud VMs can’t provide, and how self-hosting a Firecracker or Kata sandbox on dedicated bare metal compares to managed platforms like E2B on cost and control.

Running Confidential Computing Workloads in the EU in Amsterdam

We explain what Intel TDX confidential computing actually protects, confirm which hardware configuration delivers it in our Amsterdam data center today, and walk through why pairing TDX with EU data residency matters for regulated workloads.