For companies selling a device under their own brand, made by someone else
What your product really costs over the next five years
Seven questions about your own numbers, and you see the total straight away: what you pay your supplier, what changes cost you, what the price increase is worth. Then the comparison with the two other possible paths.
Run the calculation Free · seven questions · two minutes · result on screen straight away
The calculation compares three paths
- 1Stay with your supplier
What you pay over five years, purchases and changes, using your numbers.
- 2Rebuild everything from scratch
The public figure published by a platform vendor, quoted as their estimate.
- 3Start from a ready-made base
Your product rebuilt on what you already sell, handed over documented and maintained.
Free calculation · 7 questions · 2 minutes
Your numbers, the five-year total
Units sold, price per unit, changes in a year. No technical data: only what you already know by heart. The total appears on screen straight away.
The 7 questions of the calculation
It is written for companies selling a connected electronic device under their own brand, designed or developed by someone else. Teams that have run everything in-house for years will find little new here.
Projects delivered
Engineering projects we have delivered
Devices, on-board software and infrastructure, with the project in the client’s name.
Rotork
Need. Securing end to end a distributed predictive maintenance and industrial control system, running on a wireless network and connected to the cloud, protecting firmware, data and communications in high-risk environments.
Approach. Cybersecurity authority role: secure architectures, TrustZone, secure boot, protected MQTT, AWS integration and coordination across the firmware, cloud and system architecture teams.
Result. A device with secure boot, authenticated firmware, a mobile app, encrypted communication and a reduced attack surface, with strengthened IEC 62443 compliance.
Secure boot and boot chain protection, Arm TrustZone on microcontrollers, IEC 62443 threat modelling, mutually authenticated MQTT, AWS IoT Core, IAM and KMS
Daze Technology
Need. Supporting the team in technical development and in hardening the security of embedded components, making software architectures and processes scalable and flexible.
Approach. Iterative consulting in sprints, with cybersecurity and embedded development skills in the same team.
Result. A stronger development cycle, with security and performance built in from the earliest stages.
Embedded Linux, software architecture, risk analysis and threat modelling, secure development, SCRUM and Agile, ISO 15118, OCPP
ARaymond
Need. Protecting the intellectual property of the Quara system against reverse engineering and strengthening security on Intel NUC hardware.
Approach. Technical vulnerability analysis of the device, support in strengthening protections, secure boot with TPM and full disk encryption.
Result. Main attack vectors identified, local defences of the embedded system consolidated and resistance to code extraction improved.
Intel NUC, IP protection analysis, embedded system hardening, Agile sprint project management
ALTEN Group
Need. Migrating an embedded board to a new Yocto release, in a complex project on a tight schedule.
Approach. BSP update and technical support so the team could continue independently.
Result. Migration completed, from the BSP to a Yocto version not supported by the microcontroller vendor, with on-the-job training for the ALTEN team.
Yocto (custom embedded Linux), Board Support Package, Linux kernel, Secure U-Boot with ARM TrustZone
Hitachi Rail
Need. Specialist support to restore and enhance critical software components used to test and validate perception pipelines.
Approach. Test framework update, with analysis, restored functionality and optimised critical modules, plus re-engineered parameters and models for Kalman filter based tracking algorithms.
Result. Updated and optimised code delivered, with the demo milestones met.
Synthetic test framework, object detection and tracking, Kalman filter and dynamic variants, data association strategies, Agile method
Thales GTS
Need. Developing an autonomous rail driving system able to detect obstacles, estimate trajectories and decide in real time on embedded hardware.
Approach. Optimisation of perception algorithms on ROS, with stereo vision, YOLO and sensor fusion through Kalman filters, adapted to the Jetson platform.
Result. A working demonstrator in realistic scenarios, used as the technical base for autonomous driving developments.
ROS, Nvidia Jetson, YOLO and stereo vision, Kalman filter and sensor fusion, embedded algorithms for real-time perception
H-ON Consulting, for De' Longhi
Need. Analysing and testing RED-DA and EN 18031 compliance of IoT devices ahead of certification.
Approach. Targeted technical testing and preparation of documentation for the third-party audit.
Result. Compliance achieved with automated and manual testing for several clients, in particular De' Longhi.
Embedded analysis and threat modelling, RED and Machinery Directive compliance, EN 18031, architecture and testing advice
Sohonet
Need. Enabling lossless video session streaming for remote production teams, with minimal latency and full control of the pipeline.
Approach. Cloud software development for real-time video capture, processing and transmission.
Result. A stable, high-performance platform adopted by international film teams for collaborative review of very high resolution content.
Cloud development, Python, Linux, GStreamer, AWS and Azure, cloud security analysis, Agile development
GEMARMED
Need. Supporting the Regulatory Affairs team in reviewing design specifications, applicable standards and technical documentation for the MDR file of active implantable medical devices.
Approach. Document pre-review, identification of technical requirements and methodological support on compliance.
Result. Training and document review to align the devices with the new regulatory requirements.
Technical security review of medical devices, MDR compliance and applicable standards, software lifecycle security, support in drafting the file
Barco Control Rooms
Need. Raising the security maturity of development teams, making cybersecurity part of daily work.
Approach. On-the-job coaching, SDLC process review, training and optimisation of agile team practices.
Result. Ongoing.
OWASP Top 10 and CWE Top 25, threat modelling, DAST integration, Secure Development Lifecycle, Agile and SCRUM coaching
Three paths
When the product has to change, there are three options
Carry on as you are
No upfront investment. Timing, priorities and the price of changes stay with your supplier, while your customers come to you for answers.
Build your own team
Full control at the end of the road, with the people and the time it takes to get there.
Start from a ready-made base
That is TemperCrate, the base we built: identity, updatability and traceability come ready-made, the rest is developed on top, and the project is handed over to you documented and maintained.
Unlike platforms that hold your update signing keys for you, with TemperCrate the keys stay with you: you decide which updates your devices accept.
What is inside a product
What the device you sell is made of
A connected device is not one single thing. It is five, and whoever holds them decides who can work on it.
Design
Schematics and board layout, a bill of materials with approved alternates, files to manufacture and test.
The prototype
The physical board, tested and validated, with the test results: the step that turns a design into something you can manufacture.
The on-board software
The code running on the device and the procedure that turns it into the installed program, with the list of software components and their licences.
The update base
How each device is recognised and updated remotely, and the keys used to sign those updates.
Plus the documentation that holds it together: manuals, technical file, production procedures. When we say whole product, we mean these five items handed over to you.
The item the calculation does not see: updates over the years
The Cyber Resilience Act, the EU regulation on products with digital elements, places cybersecurity requirements on the manufacturer covering design, development and maintenance, and requires vulnerabilities to be handled throughout the product lifecycle. Whoever sells the device under their own brand is the manufacturer, and the product carries the CE marking.
The dates, from the European Commission: the regulation entered into force on 10 December 2024, reporting obligations apply from 11 September 2026, and the main obligations from 11 December 2027.
For your total it means one thing: the device has to be updated over the years, and today every update is a request to your supplier, at a price and on a date they set. It is the item the calculation leaves out, and the one we size on your product during the call.
Source: European Commission, Cyber Resilience Act, page updated 22 June 2026.
Supply risk
Two things that can happen, and what they mean
Your supplier raises prices
The price per unit sits in the five-year total and multiplies across every unit you sell. Without the board design you cannot ask another manufacturer for a quote, so the negotiation happens with one counterpart only.
Your supplier stops supporting the product
The device keeps working and keeps selling. What stops are changes and updates, because files, code and keys stay where they are. With the project in your hands, that work goes to whoever you choose.
What changes when the project is yours
Holding the files does not force you to change supplier: it puts you in a position to do so. That possibility alone moves price and timing, even if you stay with the same partner.
Frequently asked questions
How the calculation works
The calculation uses only your numbers: units sold in a year, price paid per unit, last year’s increase, number and cost of changes. It projects them over five years and places them next to the two other possible paths, without adding estimates of ours.
Why five years?
It is the typical life of an electronic product line before a major revision, and it is the period over which a connected device has to be maintained anyway. Over a single year the differences between the three paths do not show.
Where does the figure for path two come from?
From an estimate published by Northern.tech in 2020: 150,000 dollars for the update base alone built in house, and 750,000 for a complete solution. We quote it as their estimate, from an interested party, and it covers on-board software only.
And the cost of path three?
It depends on your line: units, board complexity and how much of the current product can be reused. We give you the order of magnitude during the 30 minutes, on your own case.
Does the project stay ours?
Yes, that is the point of how we work: we hand over and step away. What the handover includes is covered in the call.
Do we need to hire engineers?
No. We do the work, you receive the project and the documentation, and long-term maintenance is agreed separately.
Can we stay with our current supplier?
Yes. Holding the project does not force a change: it puts you in a position to make one, and that is what moves price and timing.
How we work
From the calculation to the project in your hands
The calculation
The seven answers become the five-year total for your product line.
The review
Thirty minutes with one of our engineers on your numbers, with a written outcome that stays with you.
The path
You request from your supplier what can be obtained, and the rest is rebuilt on the product you already sell.
The handover
Project, documentation and infrastructure in your name, with long-term maintenance agreed separately.
Two minutes, and you have the total
Seven questions about numbers you already know. At the end you see what your line is worth over the next five years and how it compares with the two other paths. Everyone who completes it gets a review by a senior engineer, the same person who would lead the work.