Resource network
The electricity a workload actually consumes, measured on the node, with its source and regional carbon intensity attached.
Metered in kWh, with a carbon score
The same resource, the same meter, three answers to “whose machine is this?” You choose per workload, and you can move a workload inward when the rules tighten.
On your device
Available
Inside your gram
Available
On a stranger’s machine — not available
Not applicable for this resource
Each node benchmarks itself and signs the result with its own key. Where a benchmark does not exist yet, the node says so and emits nothing in its place. So do we.
Signed metric
energy.joules_per_hash
Unit
joules per unit of work, average watts
The node reads its processor’s own energy counter (Intel RAPL) across a fixed workload and signs joules consumed and average power draw.
Intel RAPL on Linux only. On every other platform the benchmark returns “not supported — no power sensor wired yet” rather than an estimate. It reads the processor package, not the wall socket, so it undercounts the whole machine.
Compute-only networks cannot tell a regulator, a CFO or an ESG committee what a workload cost the grid. We measure it per node, from the silicon’s own counter. This is the resource that makes the rest of the network legible to people who must answer for it.
We surface estimates. We do not bill you for your own electricity.
There is no 24/7 operations centre, because we do not employ one. Instead a node that cannot prove it is healthy is evicted from the ring rather than quietly serving your work. Fail-closed, not fail-silent.
The measurement is yours. Export it, audit it, put it in your disclosure.
Every resource above reaches your workload through the same substrate, whichever ring it was drawn from.
Each node runs k3s. One orchestration layer schedules all seven resources, so a workload moves between rings without being rewritten.
Workloads that cannot be containerised run as virtual machines on the same cluster, through the open-source KubeVirt project. Same scheduler, same meter.
Standard containers, standard VMs, content-addressed objects, exportable receipts. The cost of leaving is the reason to trust the platform.
Energy is metered in kWh, with a carbon score. Each unit of work produces a receipt naming the node that performed it and the price it was charged at, on the one ledger the whole platform shares. We publish no hourly rate table on this page, because a price is meaningless without the signed unit it is counting.
See how we price compute →