India’s US$40 Billion Rafale Deal in Crisis as France Blocks Source Code Access Over Fears of BrahMos-Russia Tech Leak
France’s refusal to give India access to Rafale mission software and electronic warfare source code has delayed the 114-fighter deal, intensified tensions over BrahMos integration, and revived Russia’s Su-57E stealth fighter offer.
(DEFENCE SECURITY ASIA) — India’s proposed acquisition of 114 additional Rafale fighter jets has entered its most politically sensitive and strategically consequential phase after France refused to grant access to the aircraft’s core software architecture.
The dispute now threatens a defence package worth between US$36 billion and US$40 billion (RM136.8 billion to RM152 billion), while simultaneously reopening the possibility of a rival Russian offer centred on the fifth-generation Su-57E stealth fighter.
More importantly, the impasse has exposed a widening fault line between India’s “Atmanirbhar Bharat” self-reliance strategy and France’s determination to protect some of the most sensitive military software ever exported by a Western power.

French officials are reportedly alarmed that any deep integration of the Indo-Russian BrahMos supersonic cruise missile onto the Rafale could expose sensitive avionics and electronic warfare software to Russian entities linked to the BrahMos joint venture.
That concern has become the central obstacle delaying what India expected would become one of the world’s largest fighter aircraft acquisitions following the Indian Defence Acquisition Council’s in-principle approval in February 2026.
Even before formal contract negotiations concluded, the dispute transformed the Rafale programme from a conventional fighter purchase into a broader geopolitical contest over sovereignty, software control, technology transfer and India’s future force structure.
French President Emmanuel Macron’s February 2026 visit to India had initially been expected to produce momentum toward a final agreement, while Dassault Aviation chief executive Éric Trappier publicly stated in March that he hoped the contract would still be signed this year.
Instead, the negotiations remain stalled because India is demanding access to the Rafale’s most sensitive operational software, including the Thales RBE2 active electronically scanned array radar, the aircraft’s Modular Data Processing Unit mission computer and the SPECTRA electronic warfare suite.
Those systems collectively form the operational core of the Rafale, determining how the fighter identifies targets, processes combat information, manages sensors and responds to hostile radar and missile threats.
Without at least partial access to those software layers, Indian engineers would remain unable to independently integrate indigenous weapons such as the Astra beyond-visual-range missile, Rudram anti-radiation missile and future domestically developed strike systems.
The issue has therefore evolved beyond a simple procurement disagreement into a test of whether India can achieve genuine operational sovereignty while continuing to rely upon imported Western combat aircraft.
At the same time, Russia has moved aggressively to exploit the deadlock by presenting the Su-57E stealth fighter as an alternative platform offering complete source code access, unrestricted weapon integration and deeper local production opportunities.
READ: Russia’s Su-57 for India Will Be Built With “Maximum Use of Indian Industry and Indian Systems”
Why Source Code Has Become the Decisive Battleground
India’s demand is not centred on technology transfer in the traditional industrial sense, but rather on obtaining the digital authority required to independently modify and operate the aircraft throughout its service life.
Without at least partial access to the Rafale’s interface control documents or source code, the Indian Air Force would remain dependent on French approval every time it wanted to add new weapons or modify mission software.
That dependency has become strategically unacceptable for New Delhi because the Indian Air Force currently fields only around 31 combat squadrons against an officially sanctioned requirement of 42 squadrons.
India therefore views software sovereignty as essential to maintaining operational flexibility against both China and Pakistan during a period of increasingly compressed warning times and rapidly evolving electronic warfare environments.
Indian officials argue that future integration of indigenous systems such as the Astra beyond-visual-range missile, the Rudram anti-radiation missile and other locally developed munitions cannot proceed efficiently without direct access to the aircraft’s software backbone.
The same concern applies to the SPECTRA electronic warfare suite because India wants the ability to update threat libraries independently as Chinese and Pakistani air defence systems continue evolving.
French firms, however, have rejected those demands because the software embedded inside the Rafale has been developed across decades and represents some of France’s most protected military intellectual property.
Paris also fears that unrestricted software access could permit unauthorised modifications that might degrade performance, compromise cybersecurity or create liability issues during future combat operations.
French officials therefore appear willing to support integration of Indian weapons only if Dassault Aviation and Thales maintain permanent oversight of the process and retain exclusive control over all core software modifications.

The BrahMos Factor and France’s Russian Exposure Fears
The immediate French concern revolves around India’s desire to eventually integrate the BrahMos supersonic cruise missile, or the lighter BrahMos-NG variant, onto the Rafale fleet.
Because BrahMos Aerospace remains a joint Indo-Russian venture derived from the Russian P-800 Oniks missile programme, any integration effort would inevitably involve technical interaction with Russian-linked entities.
French analysts reportedly believe that such integration could indirectly expose proprietary Rafale interfaces, avionics logic, software architecture or electronic warfare protocols to Russian engineers.
For Paris, that risk extends beyond commercial protection and enters the realm of national security because the Rafale’s radar, mission computer and SPECTRA suite are among the most sophisticated technologies inside the French military inventory.
France is therefore not objecting to Indian weapons integration in principle, but rather to any process that would create an uncontrolled technical bridge between French systems and Russian defence organisations.
That distinction explains why French negotiators appear willing to consider limited application programming interfaces or tightly controlled integration pathways similar to those previously offered to the United Arab Emirates.
Such arrangements would permit selected Indian weapons to communicate with the aircraft while still preventing direct access to the Rafale’s underlying software architecture.
India, however, considers those limited solutions insufficient because they would still leave the Indian Air Force dependent on French technical assistance whenever new weapons, sensors or electronic warfare updates become necessary.
The disagreement therefore reflects not merely a procurement dispute, but a fundamental clash between India’s demand for operational sovereignty and France’s insistence on retaining permanent technical authority over the platform.
A US$40 Billion Deal Facing Delays and Rising Costs
The proposed MRFA programme remains one of the largest fighter procurement projects currently under negotiation anywhere in the world.
The overall package is estimated at between US$36 billion and US$40 billion, equivalent to approximately RM136.8 billion to RM152 billion using the current exchange rate of US$1 to RM3.8.
Under the current structure, France would initially deliver 18 Rafales directly from existing production lines before the remaining 96 aircraft are assembled in India.
The local assembly phase is expected to involve Indian industrial partners such as Hindustan Aeronautics Limited or Tata, beginning with roughly 30 percent indigenous content.
India is nevertheless pressing for that local content level to eventually rise toward between 50 percent and 60 percent in order to support domestic aerospace manufacturing ambitions.
The dispute over software access has therefore become inseparable from wider disagreements over localisation, industrial participation and how much control India will ultimately possess over the finished aircraft.
Those delays are especially significant because India originally expected the Rafale agreement to move rapidly following its February 2026 approval by the Defence Acquisition Council.
No formal contract has yet been signed despite expectations that Macron’s visit would provide the necessary political breakthrough.
Indian parliamentary inputs submitted in March 2026 still listed the 114-aircraft Rafale programme as a priority objective for the 2026–27 financial year, indicating that New Delhi continues pursuing the agreement despite the impasse.
Russia’s Su-57E Emerges as the Alternative France Cannot Ignore
The prolonged Rafale dispute has simultaneously created an opportunity for Russia to reposition the Su-57E as an alternative more compatible with India’s self-reliance agenda.
Russian officials have openly presented the export version of the Su-57 as the exact opposite of the French offer by promising full source code access, design documentation and unrestricted software modification rights.
United Aircraft Corporation chief executive Vadim Badekha has repeatedly stated that Indian engineers would receive complete authority to customise avionics, modify mission systems and integrate domestic weapons without Russian approval.
Russia has even reportedly assured India that the aircraft’s software would be “Trojan-free” and free from hidden external controls or backdoor access restrictions.
That offer directly addresses the precise issue currently obstructing the Rafale negotiations because India would theoretically gain full authority to integrate the BrahMos missile, Astra missile, Rudram missile and other indigenous systems.
Russian officials also argue that India could acquire between 200 and 230 Su-57E aircraft, together with weapons, training and infrastructure, for roughly the same overall budget currently associated with 114 Rafales.
Such a proposal would represent a dramatic increase in numbers while also providing India with a fifth-generation stealth capability that the Rafale, as a 4.5-generation aircraft, cannot match.
The Su-57E also aligns with India’s broader requirement to counter China’s expanding fleet of J-20 stealth fighters along the Himalayan frontier and across the wider Indo-Pacific region.
Nevertheless, the Russian proposal remains politically complicated because some Western analysts continue questioning the Su-57 programme’s maturity, production tempo and long-term reliability compared with the combat-proven Rafale.
India May Ultimately Pursue a Mixed Fighter Fleet Strategy
The most likely outcome increasingly appears to be a compromise in which India continues negotiating for the Rafale while simultaneously expanding discussions around the Su-57E.
Such a mixed-fleet approach would allow India to exploit the advantages of both aircraft while avoiding total dependence on either France or Russia.
Additional Rafales would immediately strengthen Indian Air Force squadron numbers because the service already operates 36 examples and is separately acquiring 26 carrier-capable Rafale-M fighters for the Indian Navy.
That existing infrastructure, pilot training pipeline and logistics network would reduce operational risk and accelerate induction if the MRFA agreement eventually proceeds.
At the same time, the Su-57E could provide India with an interim fifth-generation capability while the indigenous Advanced Medium Combat Aircraft programme continues developing.
Such a strategy would also preserve India’s longstanding defence relationship with Russia, which already encompasses the S-400 air defence system, nuclear submarine cooperation and multiple existing combat aircraft fleets.
For France, however, the longer the source code dispute continues unresolved, the greater the danger that India could gradually redirect political and financial momentum toward Russian alternatives.
The Rafale therefore now faces a paradoxical challenge in which its greatest strength as a technologically advanced Western fighter has also become its greatest vulnerability because France remains unwilling to surrender control over the software that makes the aircraft effective.
Whether the negotiations ultimately produce a compromise through restricted interface access, joint integration teams or phased localisation will determine not only the future of the Rafale in India, but also the wider balance between sovereignty and dependency in global arms exports.
