Web3 Use Case: Blockchain Infrastructure on Bare Metal and Ceph Storage

Updated on May 23, 2025 by Jen Royle-Jones

Web3 Use Case Running Blockchain Infrastructure on Bare Metal and Ceph Storage

Running blockchain infrastructure on bare metal and Ceph storage gives development teams more control, performance, and cost efficiency—especially when scaling storage-heavy Web3 applications.

In this use case, a Web3 team building a decentralized storage and data availability protocol needed an infrastructure partner that could deliver low-cost, high-throughput storage without sacrificing flexibility. They chose OpenMetal’s bare metal servers and Ceph storage clusters to meet their performance needs and reduce costs per terabyte across their architecture.

The Infrastructure Challenge

The team behind the decentralized storage protocol needed a cost-effective way to build and scale blockchain infrastructure on bare metal and Ceph storage that could handle large binary datasets (‘blobs’) of data across a distributed network. Their goal was to achieve the lowest cost per TB possible while maintaining performance and redundancy. Traditional cloud solutions were either too expensive or didn’t offer the flexibility and bare metal control they required.
They also wanted to scale easily and maintain consistency across deployments. That meant choosing infrastructure that could grow with them without introducing new operational overhead or sacrificing data availability.

Example Infrastructure Architecture for Storage Workloads

To support their storage layer, the team deployed a cluster of five OpenMetal Ceph-based storage servers:

  • Four Large v3 storage servers: Intel Xeon Silver 4314, 256GB RAM, 216TB HDD, 1.6TB NVMe SSD
  • One Large v1 storage server: Intel Xeon Silver 4210R, 128GB RAM, 144TB HDD, 4TB NVMe SSD

This combination of storage nodes provided both high-capacity spinning disks for large-scale data storage and NVMe SSDs for fast I/O operations. The NVMe tier supports rapid blob access and indexing while the HDDs handle durable, large-scale blob persistence. Together, the setup gave the team flexibility to support different performance tiers for storage-intensive Web3 workloads.

The Large v3 servers were chosen for their balance of memory, disk, and IOPS throughput—making them ideal for distributed object storage systems like Ceph. With 256GB of RAM, each node had enough memory to support large write buffers and caching layers that improve cluster responsiveness under load.

The Large v1 server  was used to diversify and extend the cluster’s storage capacity with cost-effective high-density storage.

All systems were deployed within the same region to maximize cluster consistency and simplify internal replication logic. This ensured faster intra-cluster communication and made performance tuning easier for the development team.

Benefits Delivered by OpenMetal

  • Significantly reduced cost per terabyte of storage
  • High throughput object storage for blob-heavy use cases
  • Full control over infrastructure with single-tenant hardware
  • Ability to scale storage capacity with consistent performance
  • Responsive support and easy onboarding for bare metal Ceph environments

Summary and Takeaway

By working with OpenMetal, the team brought their decentralized storage product online while meeting strict cost goals. They achieved a lower per-terabyte cost than with previous vendors—without giving up control or flexibility. Running five Ceph storage servers gave them the throughput and redundancy needed to support storage replication, availability, and performance. With dedicated hardware and OpenMetal’s responsive support, they avoided the complexities of managing multiple cloud environments.

Learn more about how teams are using blockchain workloads on bare metal to go beyond cryptocurrency applications.

About OpenMetal

OpenMetal provides innovative private cloud infrastructure tailored for businesses looking for greater autonomy, security, and control over their cloud environments. Leveraging OpenStack technology, OpenMetal delivers a flexible, cost-effective alternative to public hyperscalers, enabling organizations to host mission-critical applications and data with unparalleled efficiency and privacy.

Read More on the OpenMetal Blog

Why MEV Block Building Infrastructure Is Moving to TDX Bare Metal

The operator trust problem in MEV block building has a hardware solution. This article explains why Intel TDX has become the substrate of choice for confidential block building, and what bare metal adds that cloud TDX doesn’t.

OpenMetal XL v5 vs XL v4 — Same 64 Cores, Different Generation: How to Choose

OpenMetal XL v5 vs XL v4: same 64 cores, but v5 adds 33% memory bandwidth, more PCIe lanes and drive bays, and CPU-side AI; v4 keeps more L3 cache.

What HIPAA Requires from the Infrastructure Running Your Healthcare AI Workloads

Healthcare AI workloads carry the same HIPAA obligations as any system touching PHI. This article covers what the 2026 Security Rule update requires from AI infrastructure, why vector embeddings count as PHI, and how dedicated private cloud simplifies the compliance documentation burden.

How the H200 Is Built for Memory-Bound AI Workloads

The H200 is a memory upgrade on the Hopper architecture, not a new compute platform. This article covers why bandwidth matters as much as VRAM capacity, where the 141GB floor changes what fits on a single GPU, and how the NVL PCIe variant differs from the SXM5 for dedicated private infrastructure.

Why 96GB VRAM Changes the Economics of Private LLM Inference

The RTX PRO 6000’s 96GB VRAM fits 70B models at FP8 on a single card with real KV cache headroom. This article covers what that unlocks, how dedicated fixed-cost GPU infrastructure compares structurally to cloud rental, and where the H200 is the better choice.

OpenMetal GPU Clusters — Dedicated Multi-GPU Infrastructure for AI Training and Inference

OpenMetal GPU clusters: dedicated single-tenant multi-GPU infrastructure. All-RP6000, all-H200, or mixed on a private 40 Gbps mesh, fixed monthly pricing.

When Managed Kubernetes Gets Expensive Enough to Justify Running Your Own

The control plane fee is the smallest part of your managed Kubernetes bill. This article breaks down what EKS, GKE, and AKS actually charge across egress, storage, cross-zone transfer, and multi-cluster overhead, and where self-managed on dedicated bare metal makes the math work better.

What DORA’s ICT Concentration Risk Requirements Mean for EU Financial Infrastructure

DORA has been in force since January 2025, and the third-party ICT risk requirements are where infrastructure decisions land hardest. This article breaks down what Articles 28–30 require, why hyperscaler concentration is now a documented regulatory problem, and how private cloud in the EU changes the risk picture.