MCN-1 is being designed for connected systems where teams need to inspect the wireless stack, control firmware authorization, and produce evidence about what is running.
MCN-1 is pre-silicon. Conversations today are about requirements and fit — not samples, pricing, or lead times.
Autonomous platforms should not have to treat the radio stack as a blind spot. MCN-1 targets owner-controlled secure boot, measured firmware, attestation, dual-band Wi-Fi 6, Bluetooth 5.4 LE, and dual CAN-FD for connected control systems.
Industrial controllers, machinery, and gateways often remain deployed for years. MCN-1 is intended to support controlled provisioning, authenticated updates, rollback protection, field attestation, and production integration.
Facility systems, utilities, and EV charging equipment face increasing questions about firmware provenance and update control. MCN-1 targets hardware identity, measured boot, attestation, and owner-controlled trust roots to support those reviews.
Environmental monitors, facility sensors, and remote instruments may need evidence about the software producing their data. MCN-1 targets device identity, protected key storage, secure updates, and attestation for long-lived edge devices.
Connected medical and other regulated products require product-specific safety, cybersecurity, and lifecycle reviews. MCN-1 is intended to provide firmware measurements, attestation, secure updates, and supporting documentation; it does not itself confer regulatory compliance.
Programs with strict provenance and key-management requirements need verifiable system boundaries. MCN-1 is intended to provide documented boot and attestation flows, owner-managed keys, controlled provisioning, and auditable wireless firmware.
The firmware foundation is intended to remain open in every case. OEM and program engagements add support, provisioning, key management, and documentation — not a different closed codebase.
Planned public boards, modules, SDK, examples, migration guides, and documentation.
Provisioning workflows, integration support, and lifecycle planning under commercial agreements.
Program-specific key handling, provisioning, documentation, and access controls where required.
Tell us what your system needs from its wireless MCU. We will work through the requirements with you and see where MCN-1 fits.
