Second Anglo-Maratha War

The immediate occasion for the war was the collapse of authority within the East India Company's principal Maratha interlocutor, the Peshwa. In 1801 Peshwa Baji Rao II was driven from Poona by the forces of Jaswant Rao Holkar, and in October 1802 he accepted British protection through the Treaty of Bassein, by which he agreed to receive a permanent subsidiary force and to cede territories sufficient to maintain it^[1]. That treaty, which restored Baji Rao to his capital following the Battle of Poona in March 1803, was the proximate trigger for war: the chiefs of the Maratha confederacy — above all Daulat Rao Sindhia and the Bhonsle Raja of Berar — regarded it as a surrender of Maratha sovereignty and refused to recognize its terms^[2].

The structural context was the broader transformation of British policy in India under Governor-General Richard Wellesley, who arrived in Calcutta in 1798 committed to a strategy of paramountcy rather than coexistence. Wellesley's subsidiary alliance system was designed explicitly to reduce Indian states to dependence on Company military power while preventing them from entering into independent diplomatic relations with one another or with European powers^[3]. The Marathas, as the only confederacy capable of fielding European-trained infantry and artillery in numbers that could contest Company armies, represented the principal obstacle to that design. Bassein was therefore not merely a response to Baji Rao's weakness; it was an instrument for dissolving the confederacy's coherence from within.

The military capacity of Sindhia and the Bhonsle had itself been transformed over the preceding two decades by French and other European officers who organized, drilled, and led substantial regular infantry brigades along Bourbon-era lines^[4]. This modernization made the Maratha chiefs more formidable than most Indian antagonists the Company had previously faced, but it also meant their armies were expensive, their finances chronically strained, and their European officers potentially susceptible to the pressures that the French Revolutionary and Napoleonic wars were placing on French service abroad. Wellesley calculated, not unreasonably, that the window in which Company forces enjoyed a tactical edge was narrowing.

Fiscal and territorial competition among the Maratha chiefs added a further dimension. The confederacy was not a unitary state but a collection of largely autonomous houses — Sindhia, Holkar, the Bhonsle, and the Gaekwad — whose rivalries over tribute, territory, and the nominal authority of the Peshwa had produced intermittent civil warfare since the death of Madhavrao I in 1772^[1]. These rivalries made coordinated resistance to British pressure structurally difficult and gave the Company opportunities for sequential engagement rather than a simultaneous coalition war. The conflict that opened in August 1803 was accordingly fought on two geographically separated fronts: Arthur Wellesley's force operating in the Deccan against the Bhonsle and Sindhia's southern territories, and General Lake's army advancing through Hindustan toward Delhi and the upper Doab^[5]. The battles of Assaye, Delhi, and Laswari determined the outcome within the year, but the causes lay in the cumulative interaction of British imperial ambition, Maratha political fragmentation, and the destabilizing logic of the subsidiary alliance itself.

The war's formal close came through a series of separate treaties negotiated between the East India Company and the principal Maratha chiefs in 1803 and 1805. Scindia of Gwalior accepted the Treaty of Surji-Anjangaon in December 1803, ceding territory in the Doab, the districts around Agra and Delhi, and his claims over the Mughal emperor Shah Alam II; the Bhonsle of Nagpur concluded the Treaty of Deogaon, surrendering Cuttack and the province of Berar west of the Wardha River; and Holkar of Indore, though never decisively beaten in the field and undefeated at the walls of Bharatpur, ultimately signed the Treaty of Rajghat in 1806 under conditions that checked but did not eliminate his power^[1]. Together these settlements effected the single largest territorial expansion the Company had achieved in India to that date^[2].

The most strategically consequential transfer was the Company's assumption of control over the Mughal imperial capital. By establishing a protectorate over the aged emperor at Delhi — secured in part by the victory at Delhi and consolidated through the subsequent campaign — the Company became, in effect, the paramount power of Hindustan^[3]. The fiction of Mughal suzerainty was preserved, but real authority passed to the Governor-General's agents. This realignment severed the residual connection between the Maratha confederacy and the symbolic legitimacy it had derived from acting as the ostensible protector of the Mughal throne, an arrangement that had underpinned Maratha influence in northern India for decades.

Territorially, the gains were transformative. Cuttack gave the Company a continuous coastal corridor between Bengal and Madras. The Doab districts and Gujarat holdings brought agrarian revenues and strategic highways into British hands^[2]. Arthur Wellesley's campaigns in the Deccan, including the costly engagements at Assaye and Argaon and the reduction of Gawilghur, demonstrated that Maratha infantry and artillery trained on European lines could be overcome by disciplined Company forces — a lesson that shaped the Company's military doctrine and Wellesley's own career^[4]. Lord Lake's northern operations, culminating at Laswari and Deeg, similarly dismantled the most formidable of Scindia's regular brigades^[5].

The social and political fabric of the Maratha confederacy did not collapse immediately, but the war permanently altered the internal balance among its constituent powers. Scindia and the Bhonsle had been the strongest advocates of collective resistance; their successive defeats discredited that policy and emboldened the faction around the Peshwa at Poona — already compromised after Poona fell in 1803 — to seek accommodation with the Company on terms of dependency^[6]. The subordinate alliance system that the Company imposed locked each chief into bilateral obligations that precluded concerted action and eroded the confederacy's capacity to function as a unified political entity.

What the war conspicuously did not resolve was the question of Maratha sovereignty altogether. Holkar's resilience, the unbroken capacity of Nagpur and Gwalior to rebuild their military establishments, and the Peshwa's enduring resentment of British supervision ensured that the underlying contest remained open. The confederacy retained sufficient territorial base and trained manpower to resist again, and the conditions that produced the Third Anglo-Maratha War of 1817–1819 were already visible in the incompleteness of the 1803–1805 settlement^[1]. The Second Anglo-Maratha War thus marked a decisive shift in the balance of power on the subcontinent without delivering the finality that the Company's strategists sought.