Penetration test: anti-cloning and licensing on Jetson Orin / Pi 5

We make a commercial software product that runs on NVIDIA Jetson Orin Nano and Raspberry Pi 5 / Compute Module 5 boards (embedded Linux). Customers install it on their own hardware and pay per unit. We need an independent specialist to attack the protection and tell us what holds and what does not. WHAT MUST BE PROTECTED - The program, its model weights and its data files. A person who holds a unit, including a paying customer, must not be able to copy them out or work out how the software works. - The licence. Software licensed for N units must not run on another unit, and a copied SD card or NVMe drive must not run on another board. The protection consists of an application compiled from Python to native code, encrypted storage, signed updates, a signed licence tied to each unit, a restricted operator account, and secure boot with keys bound to the board's hardware. The design documents, the threat model and the source of the protection layer are shared after an NDA. - Review the design: boot chain, disk encryption and key handling, update signing, the licence scheme, operator access. - Install our test build on a development board (your own Orin Nano or Pi 5) and try to: - copy the program, model and data off a unit you hold (storage removal, boot interruption, recovery mode, serial and debug ports, memory); - run the software on a second board from a cloned drive; - bypass, forge, replay or move a licence; - get from the operator account to root; - recover the program logic from the compiled binary, and report how long it took. - Review how we issue licences: key custody, the unit registry, revocation and replacement. WHAT YOU NEED - Hands-on embedded Linux security work: secure boot, dm-crypt/LUKS, TEE or TPM key storage. - Secure-boot-level experience on NVIDIA Jetson (fuses, OP-TEE, encrypted rootfs) or Raspberry Pi 5 / CM5. Tell us which. - Reverse engineering of native binaries (Ghidra or IDA), ideally compiled Python (Nuitka, Cython, PyInstaller). - Experience attacking or reviewing licence enforcement and anti-cloning. - Hardware basics: UART, JTAG/SWD, reading eMMC, SD and NVMe. Fault injection is a plus. - Public evidence of your work (write-ups, CVEs, talks) or references we can call.