Resource network
General-purpose CPU capacity — the work that does not need a GPU and should not pay for one.
Metered in vCPU-seconds
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
Available
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
cpu.throughput
Unit
hashes/s
The node hashes a fixed 1 MB buffer with SHA-256 for a fixed duration and signs the throughput it achieved.
Single-threaded by design, so the number is comparable across machines regardless of core count. It is not a whole-machine throughput figure, and we do not publish one, because we do not yet measure one.
Most workloads are not model training. Rendering, analysis, transcoding and everything a normal institution runs are CPU-bound, and pricing them against a GPU SKU is how cloud bills get absurd.
Free on your own hardware. The meter only runs when you consume someone else’s.
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.
Standard containers on k3s. Nothing to port.
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.
Compute is metered in vCPU-seconds. 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 →