Host vs. DPU offload calculator

See how many host CPU cores the proxy tier is eating, and what returning them to tenants is worth.

Every request that reaches a GPU passes through a proxy, load-balancing, and security tier first. Run that tier on the host and it consumes cores the tenant paid for. Run it on a DPU and those cores go back into the product. This calculator prices the difference — the same decision the industry calls host versus BlueField.

01: Your fleet

One host, core by core

Each cell is one core. Red: still consumed with a DPU in place. Amber: released by moving the tier off the host. Blue: tenant-facing either way.

  • Consumed either way: 2
  • Returned by the DPU: 10
  • Tenant cores: 52

More Info

On a bare-metal or dedicated lease, the host CPU is part of what the tenant is paying for. Every core the provider keeps for its own proxy, security, and telemetry stack is either inventory that cannot be sold or a spec that cannot be advertised—the host tax. Moving that data path onto a DPU returns those cores to the product.

Frequently asked questions

Where this leads

From AI factory math to AI factory control

Start with default assumptions—12 host cores for a software proxy versus just 2 with a DPU—or see the results by entering your own hardware measurements.