Secure compliance, Empower resilience

Because your existing installed base is an exposure surface. Industrial and connected equipment in service was rarely designed with strong identity. It is built to last ten or twenty years. You do not replace it — you need a trust layer that wraps around it without modifying it.

Because network dependence is a vulnerability. Security that relies on the cloud collapses when the link goes down. On a critical site or in operations, you cannot assume a permanent connection. The decision must be made locally, in milliseconds, whether the network is available or not.

Because presence does not prove identity. Being there, or claiming to be there, is not enough to authorize a sensitive action. You need proof — and certainty that this proof matches an activity that was actually planned.

Because physical bypass is the blind spot. Unplugging a device, rewiring it directly, resetting equipment, or inserting a power strip: most systems see nothing. You need a device that treats physical access as a threat in its own right.

Because compliance demands it. NIS2 and IEC 62443 require control, traceability, and incident evidence as close to the field as possible. A signed audit log is no longer optional.

Because sovereignty is a security criterion. For critical infrastructure or defense missions, depending on a non-European vendor or cloud is itself a risk.

“It must work without a network.” The Cube makes decisions locally. Cut off from the world, it continues to authorize, alert, and block according to the rules it has been given. Connectivity returning is only a synchronization event, never a condition.

“We cannot touch the existing equipment.” The Cube is non-intrusive. It requires no changes to existing machines: it observes, recognizes, and brings trust around them.

“Our data must not leave the site.” Everything is processed locally. Nothing passes through a third-party cloud. Data sovereignty is structural, not a contractual promise.

“We need evidence for audit.” Every authorization, every denial, every incident is time-stamped, justified, and signed. You get a forensic log that your supervision can use directly.

“The environment is hostile.” The Cube comes in multiple formats: DIN rail for electrical cabinets, a sealed enclosure for outdoor and harsh conditions, and an interactive version for checkpoints. Same core, deployment adapted to the field.

The Cube is a fixed applicance with communications and sensors, installed by room, building, or cabinet. It continuously perceives its wireless environment and derives three certainties before authorizing anything.

Presence. It knows which equipment and which enrolled people are actually nearby, based on the presence of their devices.

Identity. Presence is not enough. The Cube requires a strong identity proof, anchored in hardware and impossible to spoof with a simple imitation.

Authorization. The right person is not enough either. The Cube checks that this action — this equipment, in this place, at this time — is actually listed in the planned activity schedule. The right person, the planned equipment, at the planned time: otherwise, denied.

When these three conditions are met, they trigger a local action at three levels depending on your needs: observe and alert, control access, or cut power. You choose the level; the Cube executes it autonomously.

And because the real threat is often physical, the Cube detects bypass attempts: equipment unplugged, moved, rewired directly, or reset. It does not merely note an absence — it verifies that the power feeding your equipment still passes through the authorized points. At the slightest deviation, it locks the zone, triggers the alarm, logs the incident, and can restore the installation to compliance on its own.