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
MB/s
The node moves a payload through its own encrypted tunnel against a loopback peer — itself — and signs the throughput, the round-trip time, and the same payload’s speed without the tunnel. The signed `mode` field says `loopback`, and it means exactly that.
This is a measurement of what the tunnel costs on that machine, not of a link to anywhere. It tells you how much throughput encryption takes away — on this node, 1736 MB/s direct became 379 MB/s tunnelled — and it tells you nothing about the bandwidth between two different machines. We do not measure that yet, and we do not publish a number for it.
Reachability is its own scarcity. A machine with capacity that nothing can route to is not capacity. We do not own a backbone or a micro-centre anywhere, so what we can prove about the network is what a node can prove about its own tunnel — and that is the part your privacy actually rides on.
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 →Not a specification, not a vendor sheet. The best verified result any node on this network has signed for network — and, below it, everything else that node put inside the same signature.
tunnel.throughput
1,387 MB/s
A benchmark reports one number and signs several. These travelled inside the same signature, so they are as verifiable as the figure above — and they are usually the ones that decide whether the machine suits your work.
direct_rtt_ms
0.03
direct_rtt_ms
Signed by the node. We have not written an explanation for this field yet, and would rather show it unexplained than invent one.
Direct throughput
9,119
direct_throughput_mbps
The same bytes moved without the encrypted tunnel. The gap between this and the headline number is what privacy costs on this machine.
Interface
en0
interface
The network device this node would send through.
Measurement path
loopback
mode
“loopback” means the node measured against itself. It is a true measurement of the tunnel, and it is not a measurement of a link to anywhere else.
MTU
1,500
mtu_bytes
The largest packet the path accepts. A tunnel adds header bytes, so a payload sized for a 1500-byte path fragments inside an encrypted one, and the cost surfaces as throughput nobody can explain.
Payload size
8
payload_mb
How much data was moved. Small payloads flatter a disk by living in its cache.
Round-trip time
0.091
rtt_ms
How long one packet took to go out and come back.
setup_ms
0.023
setup_ms
Signed by the node. We have not written an explanation for this field yet, and would rather show it unexplained than invent one.
What the tunnel costs
84.79
tunnel_overhead_pct
The share of throughput encryption takes away, on this machine. It is the price of the perimeter, and almost nobody publishes it.
Nothing recorded against network. That is a statement about our backlog, not a claim of completeness — the full list lives on the proof page.