BAE Systems' insistence that Brontanax is built to an open architecture is not a technical footnote — it is a targeted message to export customers, and the Middle East in particular. The Gulf states have spent the last decade demonstrating that they will not buy combat aircraft they cannot modify. Indigenous munitions, national sensor packages and sovereign mission software are now table-stakes for any serious pitch to Riyadh, Abu Dhabi or Doha.
Brontanax's open-architecture promise is a direct response to that reality. If the aircraft can genuinely accept third-party weapons, third-party sensors and third-party mission code without a full BAE integration cycle for every change, it becomes a very different export product from a traditional locked-down Western fighter. That is the pitch, and it will be tested hard.
The Middle East is not the only market. Japan and Italy, as GCAP partners, are natural candidates for a teaming aircraft that plugs into their shared Tempest ecosystem. Australia already operates the MQ-28 Ghost Bat and is unlikely to switch, but could plausibly buy Brontanax as a complementary higher-end platform. India, Turkey and South Korea all have indigenous CCA efforts and are more likely to be competitors than customers.
The wildcards are the smaller NATO air forces. Countries like Norway, the Netherlands or Poland cannot afford bespoke CCA programmes but face the same operational problem — how to add uncrewed mass to a small crewed fighter fleet. A BAE-supported Brontanax buy, integrated with F-35s under a NATO-standard teaming protocol, is a plausible route for several of them by the late 2020s.
The single biggest risk to the export map is the US Increment 1 CCA programme. If General Atomics or Anduril moves quickly to offer their airframes to NATO allies at an aggressive price, backed by US Air Force operational credibility, Brontanax's export window narrows sharply. BAE's answer to that has to be built in from the start: a genuinely open platform, delivered on schedule, at the promised cost.