Maratha Coalition-Building and Alliance Politics

The Art of Making Allies Without Giving Away the Project

A state that can only fight by itself stays small. Shivaji faced a strategic environment with multiple hostile major powers (Mughal empire, Bijapur sultanate, Portuguese, British East India Company) and a handful of potential allies whose interests could be aligned with Maratha interests — but only if the alignment was structured correctly. His alliance-building followed a consistent logic: create arrangements that gave the other party what they actually needed, while preserving Maratha freedom of action.

The plain version: Shivaji was not generous with his sovereignty. He would give tribute, access, trade rights, and military assistance — he would not give away his ability to make independent decisions.

The Kanhoji Jedhe Loyalty Test: Coalition-Building as Character Screening

Before building a coalition, you need to know which potential allies are reliable. Purandare documents the Kanhoji Jedhe loyalty test as one of Shivaji's early coalition-building methods: presenting a potential ally with a situation that required genuine commitment to the Maratha cause, then observing the response. The test was not an abstract declaration of loyalty but a situational probe that revealed whether the commitment would hold under pressure.¹

This is alliance-building as intelligence operation: the allied relationship is not assumed from declaration but verified through designed situations that require the ally to choose between their interests and the alliance. Genuine allies pass; opportunists reveal themselves. Shivaji apparently used this method systematically in building the Maratha chieftain network that became the foundation of his military capacity.

Chhatrasal Bundela: The Alliance You Build by Not Building It

The most counterintuitive alliance decision in Purandare's account is Shivaji's response to Chhatrasal Bundela, a Rajput chieftain who came to Shivaji seeking to join the Maratha confederation as a subordinate commander. Shivaji's response: go back and build your own kingdom.¹

On the surface, this is refusing an alliance. Strategically, it is building a more valuable one: an independent Rajput kingdom fighting the Mughals in northern India is worth more to Shivaji than a subordinate commander in the Deccan, because an independent kingdom opens a second front against the Mughals that they must defend. Chhatrasal Bundela's subsequent career (building exactly the kingdom Shivaji recommended) created precisely that second-front pressure.

This is the Sun Tzu "prevent alliance" logic inverted: instead of preventing your enemy's alliances, you construct the conditions for your ally's independent capability. The allied state is more useful to you fighting its own war than fighting your war for you.

The Golconda Arrangement: Tribute as Investment

The Golconda sultanate (in what is now Andhra Pradesh) paid approximately 1 lakh hons per year to the Maratha state during this period. Purandare describes this as tribute — a regular payment that secured Maratha military non-interference with Golconda territory.¹

This is alliance-building through deterrence economics: the payment structures the relationship without requiring ongoing military commitment from either side. Golconda got a guaranteed quiet boundary; the Maratha state got regular income and a friendly eastern frontier. The Treaty of Hyderabad with Qutub Shah before the southern expedition formalized a similar arrangement — Shivaji secured his rear before advancing into new territory.

The pattern repeats: before any major Maratha expansion, the flanks and rear were secured through arrangements that converted potentially hostile neighbors into passive non-participants. The four-step sequence (secure northern flank, secure eastern flank, secure western coast relations, then advance south) is visible in the 1670s campaigns.

The British East India Company: Forcing a Treaty

The British East India Company was initially hostile to Maratha interests — their Rajapur factory was plundered, their traders harassed — and Shivaji held British factors as prisoners for roughly two years. The eventual outcome: a treaty in which the British paid 10,000 rupees in compensation for Rajapur and received trade access in return.¹

The British episode is alliance-building through coercion: Shivaji used the leverage of the held factors and the naval threat to the Company's coastal operations to extract a payment and a formalized relationship. The British East India Company, which would later become the dominant power in India, was forced to pay the Maratha state and acknowledge its legitimacy in order to operate on the western coast. The message to other European trading powers (Portuguese, Dutch) was structural: Maratha maritime power must be accommodated, not ignored.

The Portuguese chauthai (one-fourth tax) arrangement after the Ramnagar engagement followed similar logic: extract a regular payment that formalizes the acknowledgment of Maratha sovereignty in the coastal zone.

Evidence and Tensions

[POPULAR SOURCE] — The specific financial details (Golconda tribute amounts, British EIC settlement figures) are described without citing primary documents. The Kanhoji Jedhe loyalty-testing episodes are drawn from Marathi oral tradition. The Chhatrasal Bundela account is the most verifiable detail, as Chhatrasal's subsequent career as an independent Rajput kingdom-builder is documented in multiple historical traditions.¹

Tension with the Arthashastra four instruments: Kautilya's four instruments of statecraft — sama (conciliation), dana (gifts), bheda (creating dissension), and danda (punishment) — describe a toolkit for managing external relations. Shivaji's alliance-building used all four: conciliation with Golconda (sama), tribute accepted as payment (dana), the Chhatrasal strategy as creating a second front that divides Mughal attention (bheda), and coercive pressure on the British (danda). The Arthashastra framework is a more explicit theoretical articulation of what Shivaji was practicing empirically.

Tension with "coalition integrity" — the more allies you build, the more interests you must manage: Each alliance arrangement created obligations that potentially constrained future operations. The Portuguese chauthai arrangement made the Portuguese non-hostile but also meant Shivaji couldn't raid Portuguese shipping without breaking the arrangement. Whether the constraints created by alliance-building limited Maratha strategic freedom is a genuine tension that Purandare doesn't fully address.

Cross-Domain Handshakes

History — Arthashastra Kingship and the Four Instruments: Arthashastra — Kingship and the Rajarshi Ideal — Kautilya lists sama/dana/bheda/danda as the king's instruments for managing external relations. Shivaji's alliance-building is a practical worked example of how these four instruments combine in a single strategic context: sama with Golconda (negotiated peace), dana accepted from the British (10,000 rupees as formalized acknowledgment), bheda via Chhatrasal (creating division within the Mughal front), danda on the Portuguese (military coercion before the chauthai arrangement). Neither Purandare nor the Arthashastra produces this integration alone; the cross-reference illuminates how the four instruments function as a system rather than alternative tools.

History — Sun Tzu Victory Without Fighting: Sun Tzu — Victory Without Fighting — The Chhatrasal strategy is the clearest example in the Maratha record of Sun Tzu's "prevent alliance" logic operating positively: creating an independent allied capability rather than neutralizing a hostile one. Sun Tzu's hierarchy (attack plans > prevent alliances > attack armies > besiege cities) assumes you're trying to disrupt your enemy's coalitions. The Chhatrasal move shows the same logic applied constructively — building allied capacity that creates strategic pressure on the enemy without requiring your own military commitment. The two sources together produce a principle: strategic alliance-building and alliance-disruption are the same skill applied in opposite directions.

The Live Edge

The Sharpest Implication The Chhatrasal advice — go build your own kingdom rather than join mine — is the counterintuitive principle that most alliance-builders miss. A subordinate ally gives you a fraction of their capacity; an independent ally fighting their own war gives you a strategic second front. The algebra is not obvious: more control over an ally typically produces less strategic effect. The implication extends beyond military alliances: in any networked system where other actors have independent capability and motivation, making them more independent (and therefore more capable) can produce more strategic value than incorporating them into your hierarchy (and therefore taking on their overhead). The Chhatrasal move is a theory of decentralized strategic coordination: let each node fight its own war, and the distributed pressure on the common enemy is greater than any centralized campaign.

Generative Questions

The Kanhoji Jedhe loyalty test is designed to reveal whether an alliance commitment will hold under pressure before the alliance is relied upon. What is the general principle: should all strategic alliances be tested before being relied upon? What are the costs of testing (you reveal your distrust; you provoke the ally into actual defection if the test is too severe)?
The Chhatrasal strategy produced its intended effect only because Chhatrasal had the capability and motivation to build an independent kingdom. Is the "go build your own kingdom" advice generalizable, or does it only work when the potential ally already has the capacity to become independent — and Shivaji was identifying an existing capability rather than creating one?
The British EIC payment and the Portuguese chauthai both formalized Maratha maritime sovereignty through financial acknowledgment. Does this suggest that financial arrangements are the most stable form of sovereignty acknowledgment — because they create ongoing incentive to maintain the arrangement — compared to military treaties or diplomatic agreements?

Connected Concepts

Maratha Economic Dimensions — Chauth and Revenue Reform — the chauthai system as both alliance mechanism and revenue stream
Arthashastra — Kingship and the Rajarshi Ideal — four instruments of statecraft as theoretical framework for Maratha practice
Sun Tzu — Victory Without Fighting — preventing enemy alliances vs. building allied capacity
Diplomatic Correspondence as Statecraft — the written instrument of alliance management

Open Questions

Are there British East India Company records documenting the Rajapur episode from the Company's perspective — including what they understood of Shivaji's political aims and how they assessed the threat?
The Golconda tribute arrangement — is there evidence that it was actually paid regularly, or was it a nominal agreement that lapsed?
Chhatrasal Bundela's subsequent career as an independent Rajput kingdom-builder is documented; is there evidence that he maintained contact with the Maratha state and that the relationship produced the strategic second-front effect Shivaji apparently intended?