A drone agreement does not become a strategic victory merely because someone photographs it beside Pakistani flags. If Pakistan receives imported aircraft while a foreign company retains the source code, encryption keys, mission-data architecture, critical components and authority over software updates, then Pakistan has not acquired sovereignty—it has rented capability.
That is the uncomfortable standard against which the newly announced Powerus arrangement must be judged.
On September 17, 2026, American defence-technology company Powerus announced that it had received a “limited procurement order” from Pakistan’s Ministry of Defence covering unmanned aerial systems and associated support. The company separately disclosed a strategic memorandum of understanding for possible cooperation in autonomous defence technologies. Neither the contract value nor the exact systems ordered were revealed.
The announcement followed a September 16 meeting at General Headquarters in Rawalpindi between a Powerus delegation led by co-founder Brett Velicovich and Field Marshal Syed Asim Munir. According to the company’s release, the discussion covered defence procurement, production and capacity building.
Those three words—production and capacity building—matter more than every photograph, handshake and public-relations statement surrounding this deal.
What Pakistan and Powerus Have Actually Signed
The first distinction being lost in the online noise is the difference between the procurement order and the memorandum.
Powerus says it has received a limited order for unmanned aerial systems and support. That appears to be an actual procurement commitment, although its financial value, quantity, configuration and delivery schedule remain undisclosed.
The separate memorandum is much less concrete. Powerus explicitly states that it creates no purchase obligation, is not a definitive agreement and remains subject to future contracts, US law, regulatory approvals and government authorisations.
| Announced element | What is confirmed | What remains unknown |
|---|---|---|
| Limited procurement order | Covers unmanned aerial systems and associated support | Price, quantity, model, payload and delivery timeline |
| Strategic memorandum | Creates a framework for possible wider cooperation | Binding localisation commitments and investment value |
| Production discussions | Production and capacity building were discussed at GHQ | Pakistani facility, ownership structure and local workshare |
| Technology relationship | Powerus has publicly discussed combining US and Pakistani capabilities | Source-code access, intellectual-property transfer and export restrictions |
| Operational purpose | Powerus supplies aerial, maritime and autonomous systems | Whether Pakistan ordered interceptors, FPV systems, heavy-lift platforms or another capability |
The factual conclusion is therefore narrower than either the celebration or outrage seen online: Pakistan has placed an undisclosed limited order and opened negotiations for deeper cooperation, but no publicly available document yet proves that a manufacturing plant or comprehensive technology transfer has been secured.
That difference must not be buried.
Powerus Is American, but Its Story Runs Through Ukraine
Describing Powerus simply as a “Ukrainian company” is inaccurate. Powerus, formally Autonomous Power Corporation, presents itself as an American defence and autonomy company. Its commercial identity, proposed public listing and corporate transaction are American.
Ukraine is nevertheless central to its technological narrative. The company has built its pitch around systems informed by the modern battlefield and has assembled capabilities through businesses such as Kaizen Aerospace, Agile Autonomy and Tandem Defense. Its portfolio spans heavy-lift aircraft, modular first-person-view drones, autonomous systems and maritime platforms.
That makes Powerus potentially useful to Pakistan. The Ukraine war has transformed unmanned warfare from an expensive specialist domain into an industrial contest involving disposable aircraft, electronic warfare, rapid software modification, distributed manufacturing and relentless battlefield iteration.
Pakistan should want access to that learning cycle—but access is not the same as ownership.
A foreign vendor can sell the hardware while retaining the integration layer that makes it valuable. It can provide maintenance without teaching local engineers how to redesign the platform. It can establish an assembly line that imports motors, flight controllers, sensors and datalinks in kits. It can call this “local production” while Pakistan remains dependent on external approval for every meaningful upgrade.
That would be localisation theatre, not technology transfer.
The Ziv Marom Question Requires Scrutiny, Not Fabrication
A significant part of the domestic backlash concerns Powerus co-founder and chief vision officer Ziv Marom. Powerus’s own leadership page identifies Marom as an “IDF veteran,” while another published biography associates his military background with robotics and an Israeli intelligence unit.
This documented background gives Pakistan legitimate grounds for intensified security vetting. It does not, however, automatically prove that Powerus is an Israeli company, that Marom currently works for Israeli intelligence or that espionage has occurred.
Those claims require evidence.
Pakistan should be neither naïve nor hysterical. A founder’s previous service in the Israeli military is strategically relevant when the customer is Pakistan’s defence establishment, particularly because Pakistan does not recognise Israel and because unmanned systems can collect extraordinarily sensitive operational information. Yet serious national-security analysis must distinguish a disclosed biography from an unproven allegation.
The correct response is not an online slogan. It is an uncompromising counterintelligence and technical-assurance regime.
Every flight controller, communications module, firmware package, ground-control station, cloud function, diagnostic interface and update mechanism should be inspected. No Pakistani deployment coordinates, mission logs, imagery or equipment signatures should pass through foreign-controlled servers. Remote access must be disabled unless specifically authorised for a controlled test environment. Software updates must be reproducible, auditable and locally signed.
Trust is not a cybersecurity architecture.
