Security Engineers Who Build, Not Just Advise

We are a team of engineers who have spent many years building security systems: for industrial controllers, hardware security keys, personal gadgets, and other connected electronics.

Over time we realized that all this work could become the foundation of a universal framework - one that would suit most connected-device hardware, whatever the industry. And we wanted to build it.

One thing held us back: most manufacturers didn't want to spend resources on security in their devices. Especially when it came to products they themselves didn't see as critical - smart home devices, for example. We were always convinced this attitude was wrong, and we kept insisting that basic security features belong in every device without exception, regardless of what it's for.

And when this view finally received support at the legislative level - with the arrival of the CRA - things began to change. The regulation obliges manufacturers to build security into their devices, and that's a step in the right direction. The CRA is not a bureaucratic attempt to over-regulate the market or cash in on fines. These days, it's a necessity.

That was the final push for us. We weren't setting out to launch "yet another startup" - we took the work we had been doing for years and made it a company of its own. That's how Platanor came to be in 2026.

Our mission is to make CRA adoption easier for small manufacturers and startups: teams that are great at their product but don't have a dedicated security department. Some of them are even considering leaving the European market altogether, because they lack the expertise and resources to meet the new requirements.

Today we do this work hands-on: we develop the security part of the firmware for our clients' devices, and the libraries it's built on.

And in parallel, we're building what we had in mind from the very beginning - a complete ecosystem: that same low-level framework for different MCUs, secure communication protocols, provisioning and manufacturing tools, PKI, and above all a cloud portal for managing the device lifecycle and production, monitoring vulnerabilities, and supporting a secure development lifecycle (SDL). Some of it is already running in client projects; some is still in development. Together, it's everything you need to comply with the CRA and similar regulations.

If you're building a connected device and the CRA is already on your agenda - get in touch: we'll look at your product and tell you honestly where to start. And if, like us, you care about making the world around us a safer place - we're open to partnership and collaboration. We'd be glad to hear your ideas and thoughts.