Skip to content
ClickHouse

ClickHouse on bare metal. Nothing between the query and the disk.

ClickHouse is built to saturate hardware: every core, every NVMe lane. On shared cloud instances, that means throttling and unpredictable tail latency. You run ClickHouse, we run the servers and the network under it.

Why bare metal

What ClickHouse gets from the whole machine

  • Full NVMe throughput

    Wide analytical scans read gigabytes per second from disk. Local NVMe RAID with no virtualization layer and no shared storage backend. The I/O ceiling is the hardware itself.

  • Same query, same time

    No noisy neighbors, no CPU steal time, no burst credits running out mid-query. Unshared cores mean the same query takes the same time at 3 AM and at the daily peak.

  • Replication without a transfer bill

    You pay a flat monthly rate for an unshared uplink at the speed you choose, with unmetered traffic across it. Replicating between regions uses that uplink, so it never shows up as a per-GB line on the invoice.

Recommended setup

What we’d put under your ClickHouse.

Four starting points from our engineers’ guide. Your account manager sizes the exact config with you.

Our engineers’ advice: one shard and two replicas, three if the data is critical. Scale up before you shard.

Recommended configuration

ClickHouse starting configurations

Dev / POC
AMD EPYC 4245P, 6 Cores 32–64 GB RAM, 1–2 TB SSD, 1 Gbps
Internal BI
AMD EPYC 9355, 32 Cores 64–256 GB RAM, 4–10 TB SSD, 1 Gbps
Warehouse
AMD EPYC 9555, 64 Cores 256–512 GB RAM, 10–30 TB SSD, 10 Gbps
Telemetry
AMD EPYC 9754, 128 Cores 256–512 GB RAM, 10–30 TB SSD, 10 Gbps or more
Read the full guide How to pick the right server for ClickHouse
From the blog

What we learned running ClickHouse ourselves

Part 1 Hardware 8 min read

How to pick the right server for ClickHouse

Part 2 Hardware 8 min read

How to tune performance settings in ClickHouse for large data loads

Underneath it all

The part you don’t have to build

A network we run ourselves

330+ Tbps network, 50 Tbps private backbone, zero packet loss. Traffic between your ClickHouse nodes across locations never fights for capacity.

67 global locations

Put nodes where your users and data are. Same hardware standard and same service quality in every location, on 6 continents.

Engineers who know the hardware

A named account manager and real-time Slack access to engineers: sizing, routing requests, 3 AM hardware swaps. 24/7, no ticket queue.

Run ClickHouse on hardware nobody else touches.

Start with one node or move a whole cluster over. Flat monthly pricing, no commitment, engineers on Slack from day one.

2,693 servers in stockSame‑day deliveryNo commitment