How to bill ASIC and GPU mining colocation: committed kW, all-in rated draw and metered pass-through compared with worked examples, plus deposits, crypto payments, curtailment credits and where FluxBilling fits.
Mario Marin9 min readMining hosting billing software invoices ASIC and GPU colocation by the kilowatt or by the machine, adds power costs, takes deposits and crypto payments, and credits curtailment or downtime. Check first whether a system meters kWh itself. FluxBilling does not; it bills committed kW or a fixed per-machine price, and metered power goes on invoice lines you add.
This guide is for operators who host other people’s miners: how the pricing models work, what the billing system has to handle around them, and an honest account of where FluxBilling fits and where it does not.
A mining hosting contract is usually built from three pieces: a power price, a hosting fee and the rules for when power is not delivered. They combine into four common models:
The table runs one example machine through three of them. The figures are illustrative, not market prices: a machine rated at 3.5 kW over a 30-day month of 720 hours.
| Model (example) | Calculation | Monthly invoice |
|---|---|---|
| All-in $0.075/kWh on rated draw | 3.5 kW × 720 h = 2,520 kWh × $0.075 | $189.00 |
| Committed kW at $55/kW/month | 3.5 kW × $55 | $192.50 |
| Metered pass-through | 2,400 kWh measured × $0.05 + $60.00 hosting fee | $180.00 |
The models differ most when the machine draws less than its rating, is curtailed, or is switched off. Rated-draw and committed-kW billing leave that risk with the customer; metered billing moves it to you, in exchange for needing per-circuit or per-outlet measurement you can defend in a dispute. Our deeper comparison is power billing: kW commit vs metered.
Space, cross-connects and remote hands are billed much as in any colocation business; see billing colocation space, power and cross-connects.
Most billing disputes in mining hosting are contract gaps, not software bugs. Put these in writing before the first machine is racked:
Write the formula into the contract, then apply it the same way every month. A common shape is a pro-rata credit: hours without power divided by hours in the month, times the power part of the invoice. As an example, 36 hours of curtailment in a 720-hour month is 5%, so a machine billed $189.00 receives a $9.45 credit.
Two choices to make explicitly. First, whether planned curtailment you sell as a feature (lower price in exchange for interruptible power) earns a credit at all. Second, whether credits are paid as account credit against the next invoice or as a credit note on the affected one. Our guides to uptime credits you can automate and credit notes and clawbacks go through the accounting.
For prepaid credit, the customer tops up a balance and invoices are paid from it. For 100 machines on the example all-in rate, one month in advance is 100 × $189.00, or $18,900.00. A security deposit is different: it is held, not spent, and returned or applied at the end of the contract, so it should sit in its own ledger line rather than in the spendable balance.
For crypto, use a gateway that quotes a fixed amount per invoice for a short window and reports payment by webhook, so the invoice closes without anyone checking a wallet. Underpayments, overpayments and late payments after the quote expires are the cases to test before going live.
FluxBilling is billing and automation software for hosting providers with DCIM and colocation built in. For a mining host, what it does:
What it does not do, plainly. It does not meter kWh: PDU polling keeps only the current reading, with no per-outlet data and no energy history, so metered pass-through has to come from your own meter readings, entered as invoice lines. It has no curtailment feature and does not calculate uptime credits automatically. It has no separate security-deposit ledger, only spendable prepaid credit. And suspending a service in FluxBilling does not switch a PDU outlet off. If metered power is the core of your pricing, you need a metering system alongside it.
Plans start at €4.95 a month excluding VAT, with DCIM included; see pricing and the colocation billing software page.
Billing software for operators who host other people’s mining machines. It invoices power and hosting by kW, by kWh or by machine, takes deposits and often crypto payments, and applies credits for curtailment or downtime.
Per committed kW is simpler and protects your margin when machines draw less than expected. Per measured kWh is fairer to the customer but needs metering per circuit or outlet with history. An all-in rate on rated draw is a middle ground.
Yes, through a crypto payment gateway that confirms each payment to the billing system. FluxBilling has free plugins for BitPay, CoinGate, CoinPayments and 2328.io.
With a formula in the contract, usually hours without power divided by hours in the month, applied to the power part of the invoice. In FluxBilling the credit is entered by an admin as a credit note or account credit.
Example figures in this article are illustrative and are not market prices. BitPay, CoinGate, CoinPayments and 2328.io are trademarks of their respective owners. FluxBilling is not affiliated with or endorsed by any of them.
Power is what a datacenter actually runs out of, and it is the line item most often priced badly. Bundle it and you subsidise your densest customers with your sparsest.
Most hosting SLAs are marketing documents never designed to be executed. They work until a real outage, when you find out the promise is either unenforceable or ruinous.
The gap between a signed colocation contract and a customer who is racked, powered and billing correctly is where operators lose time and sometimes the revenue entirely.
Shared, VPS, dedicated, colocation, and cloud each need their own billing model. Here is how to price, bill, and provision each one for 2026.
Getting money in is built carefully. Getting it back out is built in a hurry, and that is where the accounting goes wrong. Four operations that look like one.