top of page

The PKI and signing platform for CRA-ready devices

EU-HOSTED · CRYPTO-AGILE · POST-QUANTUM READY

LAAVAT runs your PKI, signs your firmware for the silicon you ship, and gives every device a trusted identity. Keys stay in FIPS-validated HSMs. Most teams sign from their own pipeline on day one.

Meet us at embedded world 2027. Nuremberg, 16–18 March 2027, stand 5-381. Book a meeting at the show →

Trusted by

Foxconn — LAAVAT customer
HERE — LAAVAT customer
KONE — LAAVAT customer
Vaisala — LAAVAT customer
Treon — LAAVAT customer
Kemppi — LAAVAT customer
customers

One platform across build, factory and field

Requests go in over REST or EST. Signed artifacts, device certificates and the audit trail come back. Nothing changes in how your developers build.​

 

Build: your pipeline requests a signature and gets the signed image back; the private key never leaves the HSM. Factory: the provisioning station requests a certificate for every unit built. Field: every boot stage and update is checked against the trust anchors you provisioned.

LAAVAT platform diagram: build pipelines, factory provisioning and field devices connected through HSM-backed signing and PKI

Three foundations every CRA-ready device needs

All three rest on one PKI, signing and encryption backbone. LAAVAT provides it as a managed service: we run your PKI, sign your firmware across your chipsets and issue each device a trusted identity — with HSM-protected keys, approval workflows and a full audit trail, mapped to CRA, RED, NIS2 and IEC 62443-4-1/4-2.

Integrate in a day, not a quarter

Engineering teams sign from their pipeline the same day: REST and EST interfaces, ready-made clients for CI/CD and provisioning stations, a Yocto recipe, and reference flows for MCUboot, HAB/AHAB, FIT, RAUC, Mender and OCI.

 

Security and compliance teams get HSM-backed keys, quorum approvals and an immutable, exportable audit trail — the evidence CRA, RED, NIS2 and IEC 62443 conformity assessments ask for, without building a signing service.

 

Product and manufacturing teams get one product per device family: signing operations, approval rules and access groups configured once and used by every pipeline and every production line.

What our customers say

KONE logo
“Securing our connected products is key in making the world's cities smarter and more sustainable places to live. The LAAVAT solution for centrally managing cryptographic keys used for digital signing and encryption plays an important role in ensuring trust in KONE’s software supply chain. The LAAVAT solution also helps us to adhere to the standards and regulations on cybersecurity, such as IEC 62443.”
​
Jussi Valkiainen, Head of Product and Application Security

Built for silicon. Run as a service. Your keys stay yours.

Built for silicon

​

Silicon-specific secure-boot signing, not just generic digest signing: NXP HAB and AHAB, AMD/Xilinx Bootgen, TI, and MCUboot on STM32, Nordic, Renesas and Microchip, plus FIT, RAUC, Mender, OP-TEE and OCI. One platform for every format your products use.

No lock-in​

​

Run it as EU-hosted SaaS, with your own HSM in your own AWS account, or on-premises. Key export is designed in, so your business continuity does not depend on us.

Run as a service

​

Every CA and signing key is generated and used inside FIPS-validated AWS CloudHSM; only signatures and public keys come back to your build. SSO with Entra ID or Google, quorum approvals and an exportable audit trail come standard, and post-quantum ML-DSA and hybrid schemes are available today.

The CRA compliance clock is running

​

Full CRA obligations apply from 11 December 2027, with penalties up to €15M or 2.5% of global turnover. Secure boot and signing infrastructure takes most manufacturers 6–18 months to build. See how it maps in our CRA compliance guide.

See it in practice

​

Pick your hardware or update tool and watch a team go from first login to a signed release, in about 90 seconds.

Try it before you commit

bottom of page