Dear ModalAI Team,

We are building Vectraswarm, an EU-based platform for secure autonomous drone swarm coordination targeting KRITIS (critical infrastructure) and defense-adjacent markets. VOXL 2 is currently under evaluation as our companion compute platform, and we are assessing the TrustZone/QTEE security architecture as part of our trust chain design between the flight controller and companion compute.

We were unable to find public documentation covering custom Trusted Application (TA) development on VOXL 2, so we would very much appreciate clarification on the following points:

1. Does VOXL 2 support execution of custom, customer-developed QTEE/QSEE trusted applications, or is TrustZone/QTEE reserved for ModalAI's own internal use?

2. If custom TA development is possible, is there an SDK, documentation, a sample TA, a signing tool, or a documented build workflow available to customers?

3. Is VOXL 2 configured for secure production boot (i.e., is the boot chain from PBL through XBL/TZ signature-verified) on standard production units, or only on specific SKUs/configurations?

4. Are the QFPROM secure-boot fuses programmed/blown on VOXL 2 production units? If so, is there a supported path for customers to sign and load their own trusted applications—for example, via ModalAI's OEM signing infrastructure, an alternate root certificate provisioning process, or a customer-signable development/debug firmware variant?

We understand that TrustZone/QTEE internals are largely proprietary to Qualcomm even from ModalAI's perspective, so any clarification you can share—including whether this would require a deeper partnership discussion—would help us scope our security architecture accurately for Phase 1 of our project.

We would be happy to schedule a short call if that is easier than covering this by email.

Thank you very much for your support.

Best regards,
Murat Albrecht
Founder & Commercial Lead, Vectraswarm
info@vectraswarm.com
vectraswarm.com