Native support for Tenzro.
One binary, from a desk to a rack.
When a node joins, its hardware profile — processor, cores, memory, accelerators, secure-execution capability — is detected and attached to its identity, where the routing layer can see it. An ordinary workstation, a Lab cluster and a full Rack all run the same binary and participate in the same marketplace. They take work in proportion to measured throughput.
That is a good fit for a hardware company, because it means the value of a machine on the network is a function of what the machine can actually do, measured continuously, rather than what its datasheet says.
Tenzro is a protocol and a network. It does not ship hardware, and we do not ship a protocol. The integration is deliberate, and the boundary between the two is the reason it works.
Inference
Models are registered and served from the node. Routing is modality-aware and scored on price, latency and provider reputation, so a machine earns according to how it performs.
Chat, text and vision embedding, segmentation, detection, transcription and forecasting runtimes are installed and served out of the box.
Training
Nodes participate in distributed training runs, contributing gradients that are aggregated into a run whose outcome is committed and receipted.
Roles are separated: a trainer contributes compute, a syncer aggregates, a sponsor posts the task and the dataset reference.
Distribution
Model weights and artifacts move peer-to-peer over a content-addressed transport, so a cluster pulls once and shares internally.
Content addressing means integrity is verified on transfer rather than trusted from a source.
| Join | First bootIdentity, wallet and hardware profile provisioned in one step |
|---|---|
| Node roles | Validator · Model provider · Storage · Light clientSelected per machine; a Lab node typically serves models, a Rack can validate |
| Accelerator runtimes | CUDA · ROCm · Metal · Vulkan · CPUSelected automatically at runtime |
| Reachability | No public address requiredTraversal and relay handle networks behind NAT |
| Identity | Hardware-rooted, persistentSurvives restart, rebuild and reinstall |
| Interfaces | JSON-RPC · HTTP · MCP · A2A |