An internet for machines starting with one address

The idea

One coordination socket

A machine should be able to join a shared network regardless of who manufactured it or what software it uses.

Every participant — ERP, BIM, robot, AI, PLC, legacy machine — connects to one coordination socket. Not “connect your Siemens PLC.” Not “integrate SAP with Autodesk.” The same door for all of them.

The frame

Open banking for machines

Shared rails for identity, state, trust, and coordination — not another siloed app.

Open Banking let money move across institutions without each pair building a private pipe. HomeQube is that pattern for machines: one network address, one stamp, one trusted heartbeat — then Alive on the wire. Our windows are the interaction design on those rails: each view pulls you into the part of the Machine Economy you need — same network, respective views.

First connection

What “online” means here

1. 01The machine gets a permanent network address
2. 02QR stamped on the physical thing — address on the object
3. 03A trusted heartbeat → the node is Alive (digitally connected)
4. 04Anyone can open its page without an account
5. 05Richer integrations later — optional now

Microcard signal

How a Microcard gets a signal

Every machine can have an identity. Machines that emit trusted signals become digitally Alive.

1. 01 Address + QR — Microcard address; QR is the stamp surface. Not yet Alive.
2. 02 Trusted heartbeat — phone, smart plug, gateway, or API. Same Alive outcome.
3. 03 Richer later — native API, autonomous agent. Upgrades, not the door fee.

APIs are one heartbeat source — not the definition of a connected machine. Legacy equipment stays in.

If you say yes

What happens next

1. 01You request a connection — short form, human review
2. 02We hold a brief — partner, not training
3. 03You mint on the main site: Add → Stamp → Heartbeat
4. 04Your machine page is the close — Alive, signal on the socket

This isn’t a software tour. First connection — like bringing a host onto a new internet.