Resource network
Distributed RAM — pooled across the nodes in a ring so a model larger than any single machine still has somewhere to live.
Metered in GB-hours
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
mem.bandwidth
Unit
MB/s
The node copies a payload buffer repeatedly and signs the sequential memcpy bandwidth it sustained.
Sequential bandwidth only. Random-access latency — which matters for some workloads more than bandwidth does — is not yet measured, so we do not quote it.
RAM, not FLOPS, is what stops an LLM from running. Every other decentralised compute network treats memory as a property of a machine you rent. We treat it as a resource you can draw from a ring, meter, and prove. As far as we know, nobody else does.
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.
Memory is pooled, never captive. Stop paying and the pages return to their owners.
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.
Memory is metered in GB-hours. 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 →