Infrastructure for physical AI
How a machine joins the network
Not an app install. Not a vendor integration. Physical AI needs participants on the wire — one permanent address, a stamp on the object, a trusted heartbeat — then the node is Alive.
What it is
What is Machine Identity?
A Machine Identity is a permanent network address for a physical participant — CNC, printer, PLC, robot, or legacy shop floor gear.
HomeQube issues that address as a QR Microcard. The card is not a dashboard login. It is how the machine becomes a first-class node on shared coordination rails — the same pattern open banking used for money, applied to machines.
The path
Add → Stamp → Heartbeat
- 01 Add — Mint the Microcard. The machine gets a permanent UEN on the network.
- 02 Stamp — Put the QR on the physical thing. Address in the world, not only in software.
- 03 Heartbeat — Phone, smart plug, gateway, or API. Trusted signal → Alive.
Alive is the v1 done-when. Richer APIs and agents come later — upgrades, not the door fee.
How the rails work
Shared rails — like open banking, for machines
Infrastructure for physical AI is the category. Shared rails are the mechanism.
Open Banking let money move across institutions without each pair building a private pipe. HomeQube applies that to machines: one network address, one stamp, one trusted heartbeat. Windows and consoles on homeqube.tech are views onto those rails — same network, respective pulls.
Who this is for
Early nodes we want on the wire
-
Shop owners & operators
CNC, printers, co-op equipment — real machines you will stamp and keep Alive.
-
Manufacturers & OEMs
Give field machines an identity without forcing every site onto your private cloud first.
-
Cooperatives & shared shops
Shared gear that should participate in outcomes — not sit as anonymous capital.
We won’t mint synthetic jobs for optics, sell a dashboard tour, or ask you to learn consoles first.
Ready to put one machine on the wire?
Start on the porch, or mint if you already know the path.