How to Deploy Confidential Computing Workloads on OpenMetal Infrastructure

Confidential computing workloads on bare metal is a new approach to protecting sensitive data—not just when it’s stored or transmitted, but while it’s actively being used. With growing security concerns and stricter data regulations, more organizations are asking how to make this a practical part of their infrastructure.

In this blog, we’ll break down how you can use OpenMetal’s bare metal servers to support confidential workloads using Intel TDX. Whether you’re working with protected health data, training machine learning models, or handling financial transactions, OpenMetal gives you the tools and control to keep it secure.

For a broader look at the technology, see our overview on Confidential Computing Benefits and Use Cases.

What You Need for Confidential Computing Workloads

To build a confidential computing environment, you’ll need:

  • Hardware-level security features like Intel TDX (Trust Domain Extensions)
  • Trusted Execution Environments (TEEs) that isolate data in memory
  • Operating systems and hypervisors that support those features
  • Full control over the hardware and how it’s configured

Note: Intel® Software Guard Extensions (SGX), Intel® Trust Domain Extensions (TDX), AMD® SEV, and Arm® TrustZone are examples of hardware-based TEEs.

Why OpenMetal Is a Fit for Confidential Computing Workloads

OpenMetal gives teams the flexibility and access they need to deploy secure workloads:

  • Bare Metal Control: Full access to physical servers without shared tenants
  • Intel 5th Gen CPUs with TDX: Available on our Medium V4, Large V4, XL V4, and XXL V4 bare metal configurations. You can also add H100 GPUs to XXL V4 servers for workloads that need acceleration.
  • GPU Support via PCIe Passthrough: You can attach the H100 to Intel TDX-enabled VMs using PCIe passthrough.
  • Fast, Isolated Networking: Redundant 10Gbps with VLAN segmentation
  • Encrypted Storage: Attach encrypted volumes to workloads as needed
  • Open APIs and CLI: Automate secure deployments

A Practical Guide to Deploying Confidential Workloads on OpenMetal

  1. Choose Intel TDX-Ready Hardware: Use OpenMetal’s Medium, Large, XL, or XXL configurations featuring 5th Gen Intel CPUs and optional H100 GPUs on the XXL. These servers come configured to launch TDX-enabled virtual machines.
  2. Deploy Virtual Machines with Intel TDX: Launch TDX-enabled VMs on supported nodes. These VMs benefit from memory and execution isolation from other workloads and the hypervisor.
  3. Attach GPUs with PCIe Passthrough (Optional): If your workload requires a GPU, the H100 can be passed through directly to your TDX-enabled VM using PCIe passthrough. This enables GPU acceleration while keeping CPU and memory data isolated.
  4. Secure Storage and Networking: Use encrypted volumes and VLAN-based network isolation to strengthen your setup. These security layers support the integrity and protection of your environment.
  5. Monitor and Validate: Deploy internal tools or third-party solutions to validate the state of your confidential computing environment. Monitoring configurations and access helps ensure ongoing protection and compliance.

Common Use Cases

  • Healthcare: Analyze PHI while maintaining HIPAA compliance
  • AI/ML: Protect training data and proprietary models
  • Finance: Run encrypted models for fraud detection or trading
  • Web3/Crypto: Safeguard wallet data and blockchain metadata from exposure

 

Final Thoughts 

Confidential computing workloads are already making an impact across real-world production environments. OpenMetal provides a reliable path to deploying secure infrastructure through Intel TDX-enabled hardware and GPU passthrough capabilities.

If you’re ready to explore confidential computing, contact our team to get started.

Read More on the OpenMetal Blog

Why DePIN Compute Networks Require Bare Metal Infrastructure To Function Correctly

Render Network, Akash, io.net, and Gensyn nodes fail on AWS because virtualization breaks hardware attestation. DePIN protocols need cryptographic proof of physical GPUs and hypervisors mask the identities protocols verify. This guide covers why bare metal works, real operator economics, and setup.

When Self Hosting Vector Databases Becomes Cheaper Than SaaS

AI startups hit sticker shock when Pinecone bills jump from $50 to $3,000/month. This analysis reveals the exact tipping point where self-hosting vector databases on OpenMetal becomes cheaper than SaaS. Includes cost comparisons, migration guides for Qdrant/Weaviate/Milvus, and real ROI timelines.

How to Choose Between OpenMetal’s Five Hardware Generations for Hosted Private Cloud and Bare Metal Deployments

OpenMetal offers five hardware generations across hosted private cloud and bare metal deployments. This guide breaks down the specs, performance differences, and use cases for each generation from V1’s foundation infrastructure to V4’s latest enterprise hardware, helping you choose the right configuration for development, production, or hybrid workloads.

How to Build a Confidential RAG Pipeline That Guarantees Data Privacy

Overcome the trust barrier in enterprise AI. This guide details how to deploy vector databases within Intel TDX Trust Domains on OpenMetal. Learn how Gen 5 hardware isolation and private networking allow you to run RAG pipelines on sensitive data while keeping it inaccessible to the provider.

Why Running Cilium with eBPF on Bare Metal Outperforms Virtualized Overlay Networks

Are overlay networks killing your Kubernetes performance? Discover why running Cilium on OpenMetal bare metal outperforms virtualized clouds. We provide a technical guide on switching to Direct Routing, configuring Jumbo Frames, and leveraging dedicated hardware to maximize eBPF efficiency.

Benchmarking Intel Xeon Gen 5 Performance for High Density Workloads

Maximize density with 5th Gen Intel Xeon. We benchmark OpenMetal’s Large V4 servers to reveal 21% better compute, 14x faster AI inference via AMX, and secure confidential computing with TDX. Eliminate the GPU tax and future-proof I/O.

Why Hyperscalers Won’t Let You Build an Email Service on Their Infrastructure

Hyperscalers like AWS and GCP block custom email services, pushing you to their metered APIs. Learn why this conflict of interest hurts your business and how to build a scalable, high-volume email platform on OpenMetal’s dedicated hardware with BYOIP, private networking, and no sending limits.

Why Enterprise Workloads Need BYOIP Support That Hyperscalers Can’t Provide

Hyperscalers lock you in by owning your IP addresses. Moving infrastructure means updating firewall rules, losing email reputation, and coordinating DNS changes across partners. BYOIP gives you control over your network identity. Learn why this matters for multi-region, hybrid, and enterprise workloads.