Give machines an identity
A substation meter, a ward pump or a scheduling agent needs its own authority. Each unit gets an identity of its own, and its permissions hang off that. Operators can see which one acted, and shut one down without touching the rest of the fleet.
A shared secret is not an identity.
A fleet that shares one key cannot isolate a single compromised unit. If your estate shares a key, it shares the damage. There is usually no way to prove which device sent a given message. Here each one has its own.
It gets worse at scale. Changing the keys across a fleet already in the field is painful enough that it rarely happens, and one broken store exposes every device behind it. Each unit holds its own instead, so an operator can shut one down without touching the others.
Four steps, and you can switch off exactly one.
Issue at source
A meter gets its own identity on the production line, before it reaches the site.
Authenticate
The gateway proves itself directly. Nothing of yours holds a shared secret.
Bind policy to identity
The signed agreement ties the meter's reading and spending permissions to its identity, not to its network address.
Revoke individually
The operator shuts down one meter. Every other unit keeps working, and the change is recorded.
What proves the machine.
A meter, a haulier and a scheduling agent, all proved the same way.
Digital Identity
Your staff and your sensors use one model.
The record itself
A fleet reporting every minute does not overwhelm it.
Neuro-Ledger®
The network between organisations
Your meter and a partner's gateway can trust each other.
Neuron™ protocol
Once a machine can prove itself, it can transact.
Once a meter can prove itself, it can pay, sign and request access within the permissions its operator set.