New Delhi’s planned purchase of 114 additional Rafale fighter jets from France has run into a critical negotiation hurdle over software control, raising fresh questions about how far foreign suppliers are willing to go in sharing the digital architecture of advanced combat aircraft.The proposed acquisition, valued at about ₹3.25 trillion, was meant to expand the Indian Air Force’s Rafale fleet beyond the 36 aircraft already in service and help address a widening fighter squadron gap. The talks have now moved beyond price, delivery schedules and local assembly to a more sensitive issue: whether India will receive enough access to the aircraft’s interface and mission systems to integrate weapons, sensors and upgrades without depending fully on the original manufacturer.
At the centre of the dispute is access to the aircraft’s Interface Control Document and related software layers. Such access determines how a user country can connect new weapons, electronic warfare tools, data links and mission systems to a combat aircraft. For India, the issue is not merely technical. It goes to the heart of operational sovereignty, especially as the armed forces seek to combine foreign-origin platforms with locally developed missiles, sensors and battlefield networks.
France has traditionally guarded core Rafale source codes and mission-system architecture closely, arguing that these systems embody proprietary technology and national-security sensitivities. Dassault Aviation, Thales, Safran and MBDA are central to the Rafale ecosystem, covering the airframe, radar, engine and weapons package. Paris has shown willingness to deepen industrial cooperation, including local manufacturing and component sourcing, but full software control remains a far more difficult concession.
New Delhi’s position has hardened because the air force wants future Rafales to work smoothly with weapons such as Astra air-to-air missiles, Rudram anti-radiation missiles and longer-range precision systems under development. Without sufficient technical access, integration would require repeated approvals and engineering support from France, adding cost, time and dependence during crises.
The 114-jet plan follows the 2016 government-to-government contract for 36 Rafales and the April 2025 agreement for 26 Rafale-Marine aircraft for carrier operations. Those purchases strengthened confidence in the platform, particularly its long-range weapons, electronic warfare suite and high availability. The next phase, however, is larger and more politically sensitive because it involves local production, deeper industrial participation and long service life stretching into the 2050s.
The air force operates far below its authorised combat strength of 42 squadrons, with ageing MiG-series aircraft retired and several Jaguar and MiG-29 fleets approaching the end of their service lives over the next decade. Tejas Mk1A, Tejas Mk2 and the Advanced Medium Combat Aircraft are central to long-term planning, but delivery timelines and production rates have kept pressure on the government to secure proven fighters faster.
France sees the Rafale as a strong fit because India already operates the type, reducing training, maintenance and infrastructure costs. Safran’s readiness to establish engine assembly work and source parts locally has strengthened the industrial case. Thales-linked radar component work and possible weapons manufacturing partnerships also support India’s push to build a wider defence manufacturing base.
The software dispute, however, exposes the limits of technology transfer in high-end combat aviation. Modern fighters are defined as much by code, sensors and electronic warfare as by engines and airframes. Control over software updates can determine how quickly a country adapts to new threats, deploys indigenous weapons or modifies systems after combat experience.
France also has strategic concerns. Rafale systems include sensitive electronic warfare capabilities and radar technologies that Paris may not want exposed beyond tightly controlled channels. The presence of Russian-origin platforms and weapons in India’s military inventory adds another layer of caution for French negotiators, particularly where integration work could involve systems with mixed supply chains.
For New Delhi, accepting limited access could weaken the logic of a large follow-on order. The government has placed self-reliance at the centre of defence procurement, and a multibillion-dollar aircraft deal that preserves dependence on foreign software gateways would invite scrutiny from Parliament, the services and domestic industry.
A compromise remains possible. France could offer expanded interface access without releasing the deepest source codes, while creating secure joint integration facilities in India. Such a model would allow faster weapons integration and upgrades while protecting proprietary architecture. It could also give local engineers greater experience in avionics, mission computing and electronic warfare integration.