Resource network
Bandwidth, relay slots and public reachability for workloads that need to be reached from outside the ring.
Metered in GB transferred, plus relay-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
tunnel.throughput
Unit
Mbit/s
The node measures throughput over its own tunnel — the same path your traffic takes — and signs the result.
It measures that node’s tunnel at that moment, from that location. It is not a claim about a backbone, because we do not own one.
Capacity sits in regional micro-centres near the people it serves, so traffic travels less distance. We size transit per site as the network grows rather than quoting a fabric-wide number.
LAN and same-node traffic are free and never leave your perimeter.
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.
Layer-2 VPC when you need it. Standard routing, standard firewalling, standard egress.
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.
Network is metered in GB transferred, plus relay-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 →