Hardware identity
19 articles
Distributed computingThe Tenzro testnet is live
The Tenzro testnet started today: a network for compute of every kind, where AI inference, compute, storage and data are served by machines that each prove who they are with a hardware key, and settled on one network. Here is what is running, how to install a node and how to join.
2 min read- Edge AI
Compute that stays local: running your own Tenzro node
What a node on your own hardware is, what it runs, what the documentation says it needs, and how its keys stay in the machine. Documented requirements only: no measured running costs have been published yet.
4 min read 
SecurityQuantum-resistant and AI-era security: what is done and what is not
What is post-quantum on Tenzro Network today, what stays classical and why, how machine identity, agents with owners, signed releases and adversarial testing fit together, and an explicit list of what is not done.
5 min read
Sovereign AISovereignty is about placement: compute and AI where you choose
A practical reading of sovereign AI for people who run or buy it: choose where work runs, who can use it, who holds the keys and what you can show afterwards, with the limits of each stated.
4 min read
Payments for machinesWhat a receipt for AI work proves
Agent payment schemes prove that a payment was made and that someone consented to it. Inference receipts prove that a machine produced an answer. Neither alone proves that the money matched the work. What each kind of evidence covers, where the gap is, and how Tenzro binds the two.
6 min read
Payments for machinesSpending limits and revocation for agents
When software spends money, someone has to answer for it. That takes a responsible party behind every agent, limits the agent cannot raise itself, and a revocation that stops payment on every rail at once. How each of those works on Tenzro, and why each has to be enforced outside the agent.
5 min read
Payments for machinesFor operators: paid for AI work you did not have to sell
Operators already run the machines AI needs. The hard part is the demand: finding buyers, pricing small units of work, and being sure of getting paid by software rather than a signed customer. How demand reaches an operator's capacity through Tenzro, and how per-call settlement and signed receipts reduce counterparty risk.
6 min read
Sovereign AISovereign AI is a placement problem
Sovereign AI is often discussed as a question of who owns the data center. In practice it comes down to three engineering questions: where each request runs, who controls the keys, and what can be proven afterwards. Each one can be answered in the infrastructure itself.
5 min read
SecuritySecuring the AI Model Supply Chain, From Weights to Serving
A model file is executable risk: it can carry code, be swapped in transit or be served by a machine that is not what it claims. A layered control set for model provenance, safe formats, signed releases and attested serving.
5 min read
Financial servicesAI in Financial Services: Records an Examiner Can Verify
Banks, insurers and asset managers are moving AI into credit, claims, compliance and operations. Supervisors in the EU, UK, US and Singapore expect model inventories, third-party oversight and records. What a verifiable inference record should contain, and how to keep it.
4 min read
ManufacturingAI on the Factory Floor: Edge Inference and Machine Identity
Factories need AI that keeps running when the internet does not, on machines that can prove what they are. How to place inference on the shop floor, anchor every device in hardware, and meet the security regimes now arriving for industrial products.
4 min read
Distributed computingFrom idle capacity to served inference: what operators need
Inference demand rises and falls through the day, so most AI capacity has spare hours. This article covers the five things a data-center operator needs to sell those hours on an open network: machine identity, a trusted model supply, metering, proof of availability and direct settlement.
5 min read
Distributed computingGPU operators: sell compute on verifiable service levels
Conventional cloud SLAs are measured by the provider, and the customer has to claim any credit. On an open market of independent GPU operators, availability and output have to be verified by someone else, and payment has to follow the verification. This article explains how that works and what it changes for operators.
6 min read
Hardware identityDevices that join a network at first boot, with hardware identity
For hardware manufacturers, the identity a device carries out of the factory decides what it can do in the field. This article covers which identifiers can anchor a machine and which cannot, why keys belong sealed to the hardware, and how devices can join an open AI network from the first time they power on.
6 min read
Hardware identityHardware-Rooted Identity for Machines: TPMs, Enclaves and Passkeys
A key file can be copied, and a copied key is a second machine nobody knows about. Why Tenzro derives every machine and person's identity from keys that never leave hardware, and how that works on servers, laptops and boards without a TPM.
5 min read
Machine economyThe machine economy: agents, robots and devices as buyers
Software agents, robots and devices are starting to buy and sell AI work themselves. This briefing for decision makers covers what changed in 2025 and 2026, what a machine needs in order to transact safely, and the infrastructure questions to ask before letting machines spend.
5 min read
Physical AIPhysical AI: Robots That Buy Compute and Sell Their Work
Robots and field devices increasingly need inference they cannot run on board, and produce data and work others will pay for. What it takes for a machine to transact safely: identity, budgets, placement and verifiable evidence.
5 min read
SecurityPreparing AI Infrastructure for Post-Quantum Cryptography
NIST's ML-KEM, ML-DSA and SLH-DSA standards are final, the IETF has standardized hybrid key exchange for TLS, and the US and EU have set dates. A practical migration plan for AI infrastructure, and how Tenzro applies hybrid post-quantum keys today.
5 min read
Hardware identityTDIP: one identity protocol for humans and machines
Humans, delegated agents and autonomous agents under one W3C DID method, with keys rooted in passkeys and device hardware. Why agents need an identity of their own.
2 min read