01
MCU-Native ZK Protocol
The Hierophant ZK protocol runs natively on microcontrollers with as little as 64KB of RAM. No operating system required. No protocol stack abstraction layer. The ZK proof generation, key agreement, and message authentication run directly on the MCU in a minimal firmware footprint designed for resource-constrained embedded environments.
MCU SDK · 64KB RAM · No OS Required
02
Post-Quantum MCU Encryption
NIST post-quantum cryptography optimized for constrained MCU environments — hardware-accelerated where available, software-only fallback where not. Full post-quantum protection runs on the same class of microcontroller used in industrial IoT and smart grid devices today, without requiring a hardware upgrade.
NIST PQC · MCU-Optimized
03
OS-Free Bare-Metal Runtime
The Hierophant embedded runtime has no operating system. No Linux kernel. No RTOS. No shell. No process manager. The protocol firmware is the entire software stack — below it is the hardware, above it is the application interface. The OS vulnerability class does not exist on a device that runs no OS.
No OS · No Kernel · No Shell · Bare-Metal
04
Sovereign IoT Network Integration
MCU devices join the sovereign non-IP mesh without IP address assignment or DNS registration. Sensors and controllers communicate with each other and with gateway nodes through the ZK mesh protocol. The IoT device appears in no IP-layer network record, no router log, and no internet address space registry.
Non-IP Mesh · No IP Address · Invisible
05
Non-IP Private Networks
The IoT mesh operates without internet protocols throughout — including at the MCU layer. Sensors and controllers connected to a non-IP mesh are immune to the entire class of IP-layer attacks: port scanning, exploit delivery via TCP/IP, botnet recruitment, and internet-routed command injection. Non-IP is not just privacy — it removes the attack surface entirely.
No TCP/IP · No Port Scan Surface · Non-IP IoT
06
Anonymous OTA for MCUs
Firmware updates delivered over the sovereign mesh without the update server learning which devices connect, their current firmware versions, or their locations. Each device receives the update through an anonymous channel. No OTA traffic analysis can enumerate the fleet, identify vulnerable version cohorts, or geolocate devices. The update completes; the fleet remains invisible.
Anonymous OTA · No Fleet Enumeration · Blind Server
07
Tamper-Evident IoT Hardware
Reference hardware with physical tamper detection that wipes key material on intrusion attempt. Austrian-manufactured MCU boards with EU-sourced components and full supply chain audit trail. Hardware attestation certifies that the device has not been physically modified since manufacturing. Tamper-evident seals provide visual inspection path for field security audits.
Tamper-Detect · Key Wipe · EU Supply Chain
08
Regulatory Compliance Layer (IEC 62443)
Hierophant embedded generates the cryptographic audit evidence required for IEC 62443 industrial cybersecurity certification and EU Cyber Resilience Act device compliance. Post-quantum encryption, authenticated firmware updates, and tamper-evident hardware together satisfy the technical security baseline for KRITIS-relevant IoT devices, with compliance artifacts generated automatically during operation.
IEC 62443 · CRA · KRITIS IoT · Compliance