India’s Fighter Choice Is Not Rafale vs Su-57: It Is Which Dependency India Can Survive

India’s next fighter decision is usually described as a contest between two aircraft. On one side is the Rafale F4 pathway: an upgraded French 4.5-generation combat system built around a fighter family the Indian Air Force already operates in earlier Rafale standards, and which India has also selected in naval form for the Indian Navy. On the other hand is Russia’s Su-57E, marketed as a fifth-generation stealth fighter and publicly offered to India with the possibility of deeper technology transfer, local production, and source-code access. Framed this way, the debate becomes a familiar comparison of performance, price, stealth, and sovereignty.

Illustration by Geopolitics Next

That framing is too narrow. India is not merely choosing between Rafale and Su-57E. It is choosing which dependency it can tolerate. While the Chinese air threat grows, the Indian Air Force remains below its authorised squadron strength, and India’s indigenous fifth-generation fighter, the Advanced Medium Combat Aircraft, remains a capability for the 2030s rather than the present decade.

The real question is not which aircraft has the stronger brochure. It is which pathway gives India usable airpower in the 2030s without locking the country into a dependency that becomes binding in wartime.

THE PROBLEM INDIA IS TRYING TO SOLVE

India’s fighter problem has three layers. The first is mass. The Indian Air Force has long planned around a much larger fighter force than it currently fields, and multiple legacy fleets will age out through the 2030s. Even before comparing stealth, missiles, or electronic warfare, India needs enough combat aircraft to sustain a two-front contingency against Pakistan and China.

The second layer is quality. China’s J-20 fleet is no longer a distant future concern. The People’s Liberation Army Air Force has already inducted the aircraft in meaningful numbers, and even rotational deployments into Tibet and Xinjiang matter because geography turns small numbers of advanced aircraft into strategic pressure. India does not need to match China aircraft for aircraft, but it does need a credible answer to a future battlespace shaped by low-observable aircraft, long-range missiles, airborne sensors, electronic warfare, and networked targeting.

The third layer is sovereignty. India does not want to buy foreign aircraft that it cannot modify, arm, repair, upgrade, or sustain without foreign permission. This is where the Rafale-Su-57E debate becomes more complicated than “French reliability” versus “Russian openness.” France may offer a more mature and dependable aircraft ecosystem, but it has historically protected sensitive software and integration access. Russia may offer more permissive language on technology transfer, but its promises sit inside a weaker production base, a sanctions-hit supply chain, and the memory of the failed Indo-Russian fifth-generation fighter project.

The decision, therefore, has to be judged across four questions: how quickly the option improves Indian combat power, how much technology control India actually receives, whether the aircraft can be produced and sustained at scale, and what geopolitical costs the choice imposes.

RAFALE'S STRENGTH IS MATURITY

The Rafale case begins with a practical advantage: India already operates the type. That matters. A fighter aircraft is not just an airframe. It is a training pipeline, a weapons ecosystem, a maintenance architecture, a logistics chain, a simulator environment, a doctrine base, and a political relationship. Adding more Rafales would deepen an existing system rather than force India to create a new one from scratch.

The proposed Rafale F4 pathway also sits on a relatively clear upgrade path. The F4 standard improves connectivity, electronic warfare, sensor fusion, satellite communications, data links, maintenance tools, and weapons integration. These are not minor enhancements. Modern air combat is increasingly decided by who detects first, shares targeting information fastest, survives electronic attack, and launches weapons from positions of advantage. Rafale’s value lies less in a single performance statistic and more in the maturity of the whole combat system.

This is why Rafale is the safer operational spine for India’s 2030s air force. It is not stealthy in the same way a dedicated fifth-generation aircraft is supposed to be stealthy, but it is proven, upgradeable, logistically intelligible, and already embedded inside the Indian system. It offers continuity at a time when India cannot afford another decade-long procurement failure.

But Rafale’s strength is also its weakness. A mature Western combat system usually comes with controlled access. The central issue is not whether India can bolt an Indian missile onto a French aircraft in a one-off arrangement. The deeper issue is whether India receives durable interface rights: the technical and contractual ability to integrate future Indian weapons, sensors, electronic-warfare tools, data links, and mission-system updates without returning to France for every major change.

This is what the source-code and interface-control debate is really about. “Source code” is often used loosely in public debate, but the more precise issue is control over the aircraft’s mission systems and integration interfaces. If India lacks that control, Rafale remains a powerful platform but not a sovereign one. If India secures partial access for named Indian weapons, Rafale becomes a practical compromise. If India secures expandable integration rights for future systems, Rafale becomes the strongest overall pathway because it combines operational maturity with manageable autonomy.

Without such access, a large Rafale purchase risks becoming a black-box procurement dressed in the language of Make in India.

SU-57E'S STRENGTH IS LEVERAGE, NOT CERTAINTY

The Su-57E offer is attractive because it speaks directly to India’s frustration with Western technology control. Russia has publicly signalled willingness to discuss local production, design documentation, and source-code access. For India, that offer has obvious appeal. It suggests the possibility of a foreign fifth-generation aircraft that Indian engineers could modify more freely than a Western platform.

But the offer must be separated from the executed reality. A proposal is not a contract. A contract is not a delivery. A delivery is not a sustainable fleet. The decisive question is not whether Russia says India can receive source code. It is which code, for which subsystems, under what restrictions, at what price, and with what enforceable rights.

This distinction matters because the most sensitive parts of a modern fighter are not the easiest to transfer. Radar, electronic warfare, engine control, flight-control logic, mission computers, sensor fusion, and weapons interfaces are precisely where states protect their advantage. Even if Russia were more willing than France to share some layers of access, India would still need to know whether it is receiving genuine system control or only enough access to integrate selected weapons under Russian supervision.

The failed FGFA programme is the shadow over this entire discussion. India and Russia once attempted to build an Indian fifth-generation fighter variant based on the Russian programme. The effort collapsed after years of disagreements over cost, workshare, stealth, engines, and technology transfer. That history does not prove every future Russian offer will fail, but it does mean India cannot treat the Su-57E proposal as if it starts from a clean slate.

The Su-57E also faces a production credibility problem. Russia has built the Su-57 in limited numbers, and its defence-industrial base is under pressure from war demands and sanctions. A small Indian bridge buy may be imaginable. A large co-production programme at the MRFA scale is a different matter. India would not only be buying aircraft. It would be betting that Russia can produce, upgrade, spare, and support an advanced fleet while meeting its own domestic needs and managing sanctions-constrained supply chains.

The aircraft’s “fifth-generation” label also requires caution. The Su-57 has real advantages over older Russian fighters: internal weapons carriage, better shaping, modern sensors, long range, and strong kinematic performance. But open-source assessments do not support treating the export Su-57E as equivalent to the most mature Western low-observable aircraft. Its stealth profile appears better understood as partial low observability plus standoff strike capability, not as a clean solution to China’s J-20 problem.

That does not make the Su-57E irrelevant. It makes it a hedge, a bargaining chip, and possibly a limited bridge. It should not be treated as the centrepiece of India’s next-generation airpower strategy unless Russia can convert marketing language into enforceable delivery, subsystem access, and sustainment guarantees.

THE SANCTIONS RISK IS NOT AUTOMATIC, BUT IT IS REAL

A major Su-57E purchase would also create a geopolitical problem that cannot be reduced to slogans. The United States has a sanctions framework aimed at significant transactions with Russia’s defence sector. India has not been treated like Turkey, and Washington has strong strategic reasons to preserve defence cooperation with New Delhi. India’s role in the Indo-Pacific, its growing defence relationship with the United States, and its value as a balancing power against China all reduce the likelihood of a maximal American response.

But “less likely” does not mean “irrelevant.” A limited legacy purchase is one thing. A large, forward-looking co-production programme with sanctioned Russian entities is another. The risk is not only formal sanctions. It is programme disruption, licensing friction, delayed approvals, reduced technology trust, and complications in other parts of India’s defence-modernisation agenda.

This matters because India’s future airpower ecosystem is increasingly entangled with the United States. The Tejas and AMCA pathways depend heavily on American engine cooperation, particularly the GE engine family. Tejas Mk1 and Mk1A depend on the GE F404 engine, while Tejas Mk2 and the first AMCA variants are tied to the GE F414 class. India’s long-term goal is engine sovereignty, but it has not yet reached that point. Until it does, any decision that creates avoidable stress in the US-India defence technology channel has to be treated as a real strategic cost.

That risk is not abstract. If a major Su-57E purchase triggered American export-control retaliation, licensing friction, or even a slower informal approval environment, the damage would not be confined to the Russian aircraft. It could spill into the Tejas ecosystem that India is relying on to rebuild squadron strength. Operational Tejas fleets need engine spares, overhaul support, and future sustainment depth. Future Tejas Mk1A and Mk2 deliveries need engines on time. India has already experienced delays in GE engine deliveries, which shows how exposed an indigenous airframe can become when its propulsion chain remains foreign-controlled. A Su-57E deal may therefore threaten not only the diplomatic comfort of the US-India relationship, but the practical tempo at which India can field its own fighters.

This does not mean India should let Washington veto its procurement choices. It means India should understand the trade-off. A Su-57E deal may increase autonomy from Western software restrictions while increasing vulnerability to Western sanctions, licensing, and engine-supply risk. That is not sovereignty. It is a substitution of one dependency for another.

THE DEEPER PROBLEM IS PROPULSION

The engine question complicates the entire debate because it shows that even India’s indigenous pathway is not fully indigenous yet. Tejas Mk1 and Mk1A depend on the American GE F404. Tejas Mk2 and AMCA Mk1 are expected to depend on the American GE F414. AMCA Mk2 is supposed to move to a higher-thrust engine co-developed with France’s Safran. In other words, the fighter debate is sitting on top of a propulsion-sovereignty problem.

This matters because engines are not ordinary components. They define range, payload, acceleration, supercruise potential, maintenance burden, infrared signature, sortie generation, and upgrade headroom. More importantly, the core technologies inside high-performance fighter engines are among the hardest technologies in defence aerospace to master: single-crystal turbine blades, advanced cooling, hot-section metallurgy, coatings, compressors, full-authority digital engine control, and the manufacturing discipline needed to reproduce all of this reliably at scale.

France does not appear to be offering India a ready-made AMCA Mk2 engine that can simply be installed when required. The proposed pathway is the co-development of a new 110-120 kN class engine with Safran and India’s Gas Turbine Research Establishment. That could be strategically important if India receives genuine design authority, shared intellectual property, manufacturing know-how, hot-section access, and the ability to modify and upgrade the engine without future French permission. But if the arrangement becomes licensed production with selective transfer, India will have shifted a critical dependency from the United States to France rather than solved it.

This also limits what the Su-57E can realistically solve. A Russian offer of source-code access, local production, or aircraft-level technology transfer does not automatically give India the know-how to build an indigenous fifth-generation fighter engine. Engine sovereignty requires deep transfer of propulsion technology, not just access to avionics software, weapons interfaces, assembly documentation, or airframe manufacturing methods. Unless Russia explicitly transfers usable AL-51-class engine design, hot-section, materials, manufacturing, testing, and control-system knowledge in a form Indian industry can absorb, the Su-57E would not close India’s propulsion gap. It may teach India some fifth-generation aircraft-integration lessons. It would not, by itself, create an Indian engine for AMCA.

The sharper question, then, is not whether Russia, France, or the United States is the more generous partner in the abstract. It is which partnership helps India climb the hardest part of the aerospace ladder. Software access matters. Weapons integration matters. Local assembly matters. But without propulsion sovereignty, India’s most sovereign aircraft can still be grounded by someone else’s engine bottleneck.

AMCA IS THE DESTINATION, BUT NOT YET THE EXIT

The cleanest strategic answer is indigenous airpower. India’s Advanced Medium Combat Aircraft is the programme that best aligns with the country’s long-term requirement: domestic design authority, Indian mission systems, Indian weapons integration, and eventually a stronger domestic engine ecosystem. If India wants to stop choosing between French black boxes, Russian uncertainty, and American export-control risk, AMCA is the structural answer.

But AMCA cannot solve the near-term problem, and it should not be treated as a clean exit from foreign dependency in its first form. Even under favourable assumptions, it is a 2030s capability. Its first production variant is expected to rely on American engines, while its later variant is supposed to move to a new Indo-French engine that still has to be developed, tested, certified, produced, and integrated. The usual risk in Indian defence planning is not that programmes never arrive. It is that they arrive later, in smaller numbers, and with more imported dependencies than the original political language suggests. AMCA should be protected, accelerated, and treated as the centre of gravity, but it cannot be used as an excuse to leave the IAF exposed through the next decade.

The delay-only option, therefore, has a hidden cost. It preserves strategic purity but accepts operational risk. It asks India to tolerate the fighter gap while China adds advanced aircraft, sensors, missiles, and airbase infrastructure across the region. That may be acceptable only if India is confident that Tejas Mk1A, Tejas Mk2, Rafale upgrades, air defence systems, Su-30 modernisation, and standoff weapons can collectively absorb the risk until AMCA arrives.

But that confidence depends on the Tejas line actually moving and AMCA Mk1 not being delayed by the same propulsion dependency. A strategy that says “delay foreign procurement and rely on indigenous fighters” becomes fragile if the indigenous fighters are themselves waiting on foreign engines. This is why the Su-57E question cannot be isolated from Tejas or AMCA. If a Russian stealth-fighter purchase creates even a modest risk of disruption to GE engine supply, spares, licence approvals, or industrial cooperation, it could weaken the very domestic fallback that makes a delay strategy plausible.

That is a large bet.

THE HYBRID OPTION IS NARROW

The hybrid option sounds attractive because it appears to avoid a false choice: buy Rafale for reliability, buy Su-57E for stealth and leverage, and keep AMCA moving as the future. In theory, this gives India mass, maturity, and optionality.

In practice, hybrid procurement can become the worst of all worlds. Two foreign fighter ecosystems mean two logistics chains, two training pipelines, two weapons-integration battles, two upgrade cycles, and two geopolitical relationships to manage. If India buys a full Rafale fleet and a large Su-57E fleet, the result is not strategic flexibility. It is financial, industrial, and organisational overload.

The only defensible hybrid is a narrow one. Rafale would remain the primary operational spine. Su-57E would be considered only as a small bridge fleet, only if Russia offers early delivery, enforceable subsystem-level access, credible sustainment arrangements, and a sanctions-manageable structure. The purpose of such a buy would not be to replace Rafale or AMCA. It would be to create limited fifth-generation exposure, strengthen India’s bargaining position with France and the West, and hedge against AMCA delay.

Even this narrow hybrid has a hard constraint: it must not endanger the Tejas ramp-up or AMCA’s propulsion pathway. A small Su-57E bridge only makes sense if its geopolitical cost is ring-fenced from the GE-powered aircraft India is already counting on and from the later Indo-French engine effort India needs for AMCA Mk2. If the price of buying a limited Russian hedge is slower Tejas Mk1A deliveries, uncertainty around Tejas Mk2 engines, friction around AMCA Mk1’s F414 supply, or reduced confidence in the AMCA Mk2 engine pathway, then the hedge has failed its purpose. It would be adding a Russian dependency by weakening the domestic programme that was supposed to reduce dependency in the first place.

Even then, the burden of proof sits with the Su-57E offer. India should not buy a hedge that creates more risk than it offsets.

THE DECISION INDIA SHOULD MAKE

The strongest conclusion is conditional, not absolute. Rafale is the best base pathway if India secures meaningful interface rights. Su-57E is not robust enough to anchor India’s future fighter force, but it may have value as leverage or as a tightly bound bridge. AMCA remains the strategic destination, but it cannot be treated as a near-term substitute for foreign procurement or as an immediate escape from propulsion dependency.

This conclusion may sound unsatisfying because it does not produce a clean winner. But strategic procurement rarely produces clean winners. It produces trade-offs between capability, time, autonomy, cost, and geopolitical exposure. The danger is pretending those trade-offs do not exist.

If India chooses Rafale without integration rights, it buys a mature aircraft while preserving a future dependency. If India chooses Su-57E on the basis of Russian technology-transfer promises, it risks buying sovereignty theatre without operational certainty and may expose the Tejas and AMCA Mk1 engine pipelines to avoidable geopolitical risk. If India delays for AMCA alone, it risks leaving the IAF short during the very decade in which China’s airpower advantage becomes harder to ignore, while still depending first on American propulsion and then on the success of a new Indo-French engine.

The correct policy is therefore not “Rafale over Su-57” in a simplistic sense. It is Rafale as the operational spine, Su-57E as pressure and optional hedge, AMCA as the sovereign destination, and propulsion sovereignty as the deeper industrial objective. The decisive negotiation is not only over aircraft numbers or price. It is over who controls the software, weapons interfaces, mission systems, sustainment chain, upgrade path, and engine core.

India’s fighter choice is ultimately a test of strategic discipline. Russian openness without reliable production is not sovereignty. French reliability without integration control is not sovereignty. American engines inside indigenous fighters are not sovereign. A French co-developed engine without real Indian design authority would not be sovereign either. Sovereignty is the ability to keep fighting, upgrading, producing, and adapting when foreign suppliers are distracted, unwilling, sanctioned, or politically constrained.

That is the standard India should apply. Not which aircraft looks more advanced on paper, but which dependency buys India time while reducing the need to make this choice again.

---

BY GEOPOLITICS NEXT

CURATED BY TEAM GEOSTRATA

info@thegeostrata.com