For companies that design the board in house and have the software developed outside
Changing who develops your software, without pausing releases
Seven questions about your software, and you see straight away how much of the existing work is reused, how many weeks a new team needs to reach the first release, and what keeps selling in the meantime.
See your handover plan Free · seven questions · two minutes · result on screen straight away
The plan answers three questions
- 1How much is reused
Source, build procedure, keys and documentation: what you already hold shortens the handover.
- 2How long it takes
The estimated weeks for a new team to reach the first release on your product.
- 3What keeps selling
The current product keeps selling, and the version in progress reaches its release.
Free plan · 7 questions · 2 minutes
Your handover plan, in two minutes
What you already hold of the software, what kind of product it is, when the next version ships. Only what you already know by heart. The plan appears on screen straight away.
Le 7 questions of the plan
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
The three things that hold a handover back, and how they are handled
The release calendar
The handover attaches to a version already planned and the two tracks run in parallel: your current supplier closes the version in progress while the new team prepares the next one.
The cost of the first handover
It concentrates on the first release, because the existing software has to be read and picked up. From the following versions the cost returns to that of a normal development contract, and the comparison is with the annual spend you already have.
Knowledge of the product
It sits in the software and the documentation, and it is recovered by reading them: that is why the first release takes longer than the ones after it. For identity, updates and traceability we start from TemperCrate, which is already built.
The board design is not touched: it stays where it already is, with you. What changes is who writes the software, and at the end the source, the rebuild procedure and the keys are in your name.
What is inside a product
With the design in hand, what else it takes to release
The design is the first of the five parts of a connected device. These are the others, and they decide who can release a version.
Design
Schematics, layout, bill of materials and production files: this part is already yours, and it is what lets you choose the manufacturer.
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 rates
Development spend sits in the five-year total. With the source and the procedure in hand you can ask another developer for a quote, and the negotiation changes; without them, it stays with one counterpart only.
Your supplier stops supporting the product
The device keeps working and keeps selling, and the design stays yours. What stops are the versions, because source, procedure and keys sit elsewhere. With those three in hand, the work goes to whoever you choose.
What changes when the chain is yours
Holding source, procedure and keys does not force a change of supplier: it puts you in a position to make one. That possibility alone moves price and timing, even if you stay with the same partner.
Frequently asked questions
How a handover works
Changing who develops the software does not mean starting over: the board design stays yours and is not touched, the existing software is read and reused, and the handover attaches to a version already on the calendar.
Do we have to pause releases?
No, when the two tracks run in parallel: your current supplier finishes the version in progress while the new team prepares the next one. That is the sequence the plan proposes when you have a version within six months.
How long does the first release with a new team take?
It depends on the type of software and on how much you already hold. The plan gives an estimate in weeks from your answers, and it is verified by reading the existing software during the 30 minutes.
How much does the handover cost?
The cost concentrates on the first release, because the existing work has to be read and picked up. From the following versions it returns to the cost of a normal development contract, and that is the comparison to make.
What if the current supplier does not hand over what is missing?
Whatever does not arrive is rebuilt starting from the product you already sell, and it usually concerns the update part and the keys. The plan sets out what to request in writing and what to plan on rebuilding.
Does the board design stay ours?
Yes, and it is not touched. What we hand over at the end is the source, the rebuild procedure, the keys and the software documentation.
Dobbiamo assumere qualcuno?
No. We do the development, you receive the documented software project, and long-term maintenance is agreed separately.
How we work
From the calculation to the project in your hands
The plan
The seven answers become the handover plan for your product.
The review
Thirty minutes with one of our engineers on your numbers, with a written outcome that stays with you.
The path
You request source, procedure and keys from your supplier, and development restarts on your board.
The handover
Project, documentation and infrastructure in your name, with long-term maintenance agreed separately.
Two minutes, and you have the plan
Seven questions about what you already hold. At the end you see how much work is reused, how many weeks a new team needs for the first release, and what keeps selling in the meantime. Everyone who completes the plan gets a review by a senior engineer, the same person who would lead the work.