History
History

Ali Adil Shah II and the Fall of Bijapur

History

Ali Adil Shah II and the Fall of Bijapur

In 1680, two court artists named Chand Muhammad and Kamal Muhammad sat down in Bijapur and painted every Adil Shahi king who had ever ruled — all of them on one carpet, lined up from the founder Yusuf down to the boy-king then on the throne.
developing·concept·1 source··Jun 15, 2026

Ali Adil Shah II and the Fall of Bijapur

The Painted Curtain Call: A Dynasty Watching Itself Die

In 1680, two court artists named Chand Muhammad and Kamal Muhammad sat down in Bijapur and painted every Adil Shahi king who had ever ruled — all of them on one carpet, lined up from the founder Yusuf down to the boy-king then on the throne.1 Yusuf alone sits enthroned, a Safavid figure behind him handing over a key to both the worldly and spiritual realms; behind that, a sea with a ship, signalling how far Bijapur's trade once reached into the early-modern world.2 The boy at the end of the line, Sikandar, is the smallest figure in the frame — even his turban only imitates his father's, because he had not yet carved out any identity of his own.3 He never got the chance. One scholar called the picture not a genealogy but a "painted curtain call" on a once-glorious dynasty.4 Six years after the paint dried, Aurangzeb's armies took the city, and the line that began with Yusuf around 1490 ended with a twelve-year-old in a turban he had borrowed from a dead man.

What This Actually Is

This is the story of how the Adil Shahi sultanate of Bijapur went from a wealthy, well-armed Deccan power to a Mughal province in a single generation — the reign of Ali Adil Shah II (1656–72), the regency wreck that followed him, and Aurangzeb's final siege and annexation in 1686.5 The decline has three engines running at once: Mughal pressure from the north, Maratha raids from inside Bijapur's own territory, and a court that rotted from within while its king drank himself out of relevance. Ali II inherited a kingdom that still fielded an army of 80,000 cavalry and a quarter-million infantry and pulled in revenues that rivalled a respectable European state.6 None of that saved it. The page tracks the mechanism of that collapse — why a rich, defensible kingdom failed anyway — and ends with the surrender of the keys on 22 September 1686.

The Double Game (The Internal Logic)

Ali II's survival strategy was to be two-faced on purpose, and for a while it worked. He was, in Pillai's phrasing, "overtly submissive, but secretly subversive" toward the Mughals, certain that open war with them was eventually unavoidable.7 So when Aurangzeb sent a Rajput general south in the mid-1660s to crush Maratha rebels — Shivaji's men, rising in territory that was nominally Bijapur's own — Ali II quietly fed those same rebels.8 The logic was elegant: keep the Marathas just strong enough to act as a wall between the imperial army and his own capital, while never letting them grow strong enough to swallow Bijapur whole.9 The Mughal general saw through it and reported home that "Adil Khan in his folly played false with me," sending an army into Maratha lands for show while secretly wanting the rebels left standing as a buffer.10 The double game was rational, even clever. It was also a slow poison: by subsidising Shivaji, Bijapur was feeding the very force that would later strip its forts away one by one.

Information Emission (Synergies & Handshakes)

This page gives the vault the Bijapur-side view of Shivaji's rise — the crucial fact that the Maratha power did not erupt against the Mughals first but against Bijapur, in Bijapur's own land, partly on Bijapur's own coin. That reframes the Maratha-hub material: the bargi-giri raiding doctrine matured against a sultanate that was simultaneously its sponsor and its prey. It also supplies the demographic and fiscal scale of a "weak" kingdom — 80,000 cavalry, 78 million rupees of revenue — which corrects the lazy reading that Bijapur fell because it was small. It was not small. It fell because it was divided, drunk, and outlasted. Finally, it hands the vault the closing bracket on the Adil Shahi founding: the dynasty Yusuf started around 1490 dies here, completing the arc that runs from the four-kingdom Deccan through Talikota to this surrender.

Analytical Case Study: The Siege That the Besieger Lost

The 1666 siege of Bijapur is the whole tragedy in miniature, because the Mughals technically won and still lost. Aurangzeb's Rajput general arrived with 40,000 of his own soldiers plus 9,000 Maratha troops supplied by the very rebels Ali II had recently been subsidising — a grim joke, the king's old clients now marching against him.11 The general had not even planned a real siege; the plan was to win the court with money and promises of Mughal favour, having already bribed several Bijapuri nobles.12

Then Ali II did something that surprised everyone: he fought scorched earth. He had the tank embankments demolished, poison and carrion thrown into the wells, trees and tall buildings near the fort destroyed, and the whole surrounding country laid waste until "not a trace of grass or fodder was left."13 The bribed-court plan collapsed against a landscape with no water and no food for miles. For eight months the general blustered and tried to force his way, but a kingdom that still commanded 80,000 cavalry and vast revenues was no easy annexation.14

The arithmetic finished it. The general spent the four million rupees Aurangzeb gave him, then over twice that of his own money, and finally "saw light."15 The Mughals retreated to their renamed headquarters at Aurangabad. Bijapur had repelled the empire.

And then Ali II threw it away. Instead of strengthening defences and disciplining a court full of factions eager to prosper as Mughal agents, he "lapsed into a world of wine."16 The kingdom that won the siege of 1666 was the same kingdom that would open its gates twenty years later — because the victory bought time the king spent drinking instead of governing. The case study's lesson is brutal: a state can survive its enemies and still die of its own neglect.

Implementation Workflow: Standing in the Durbar, 22 September 1686

You are inside the fort, and you can hear the famine before you see it. Outside the walls, the countryside is dead — Aurangzeb's armies have sat here for fourteen months, and now the emperor himself has come, which the garrison understands as a verdict rather than a threat. There are between two and three thousand soldiers left to defend the king, poorly fed, badly paid, demoralised by the sheer mass of Mughal tents and by the emperor's presence among them.17 The reserves inside are almost gone.

The gates open. A sorry procession moves out toward the Mughal camp: the Adil Shah carrying the keys to his own fort and his royal insignia, walking to surrender the kingdom his ancestors held for nearly two hundred years.18 He is Sikandar, the small boy from the painting, now in his late teens. Aurangzeb receives him almost gently — "I shall exalt you with many favours and gifts. Be composed in mind."19 The gentleness is the cruelty's polish. The king becomes "Adil Khan," a Mughal noble on a pension of 100,000 rupees, packed off to Daulatabad and then Satara, where he dies in 1700 in his early thirties.20 Behind him the city itself collapses: Aurangzeb enters scattering gold and silver coins, performing what was effectively the last rites of a gracious city, and a bubonic plague soon kills half the population, scattering its poets and scholars into nothing.21

The Survival-Game Failure (Diagnostic Signs)

The Adil Shahi collapse shows exactly how a buffer-state strategy curdles, and the warning signs are legible in hindsight. The first sign is the successful double game that breeds complacency: feeding Shivaji to wall off the Mughals worked just well enough that nobody noticed the wall had become a wolf. The second sign is the regency vacuum — when Ali II died in 1672 leaving a four-year-old, the throne became a plaything; a Habshi regent, then a Westerner, then a Habshi again, only the last lasting more than two years, while the Marathas picked off forts and governors stopped obeying the court and the treasury emptied.22 The third sign is the loyalty market: a court so factionalised that nobles openly angled to prosper as Mughal agents, so that the third regent could in 1678 pledge the king's sister in marriage to Aurangzeb's son before public fury forced him to recant.23 The misreading to avoid is "Bijapur fell because it was weak." It repelled the empire in 1666 and defeated a Mughal army again in late 1679, when the commander "marched through the country around it like a mad dog" and was recalled in disgrace after a Maratha attack in March 1680.24 The diagnostic truth is the opposite: a strong kingdom can fail by attrition and self-sabotage faster than by conquest.

Evidence / Tensions / Open Questions

Pillai flags a genuine uncertainty at the very top of Ali II's reign: Aurangzeb insisted that Muhammad Adil Shah had left no sons and that Ali II was illegitimate — a useful pretext for intervention.25 The traveller Thevenot later recorded that the king "was an orphan, whom the late king and queen adopted for their son," and contemporary Indian sources say he was raised by Muhammad's queen without naming his actual mother.26 Pillai does not resolve whether Ali II was biological heir, adopted prince, or convenient fiction — and the ambiguity is itself the point, because it gave Aurangzeb his "excuse for intervention in 1656."27 A second tension is fiscal: Pillai cites Bijapur's pre-decline revenue at 78.4 million rupees plus 52.5 million in tribute against the Mughals' 220 million in Shahjahan's reign — a real gap, but not the chasm the "doomed minor sultanate" narrative implies.28 The open question the source leaves: did the double game ever have a winning line, or was Ali II's "double or triple role, as dictated by his own survival" always just a slower road to the same surrender?29

Author Tensions & Convergences

Pillai's whole project in Rebel Sultans is to argue against the communal, nationalist reading of the Deccan — the story in which a Hindu Maratha hero rises against alien Muslim sultans. The fall of Bijapur is awkward for that tidy story and Pillai leans into the awkwardness. His Ali II funds Shivaji; his Bijapur secures its survival, briefly, by buying Maratha defence against the Mughals; the third regent, facing a Mughal alliance his own city rejects, "had to secure assistance from the Marathas for the defence of the state" — a Muslim court saved, for a moment, by the very Hindu power later mythologised as its nemesis.30 Pillai calls this "ironic," and the irony is doing argumentative work: it dissolves the clean confessional line into a mess of pragmatic alliance.31

Set against the vault's Laine material, the tension sharpens. The Laine pages study how Shivaji's legend was constructed as interested knowledge — the hero purified of his messy political context. Pillai's Bijapur is exactly that excised context: a Maratha power that raided, took subsidies, and sold its sword to a sultan's regent is not the immaculate dharmic liberator of the legend. Pillai is restoring the political mud the legend later washed off. Where the source is thinnest is the Maratha interior view — Pillai sees Shivaji's rise from Bijapur's collapsing throne room, not from Shivaji's own camp, so the agency runs one way. The Purandare-vantage material in the vault supplies the answering perspective.

Cross-Domain Handshakes

Plainly put: Bijapur did not die because it was poor or small — it died because it played a clever survival game that worked just well enough to let it stop paying attention, and that pattern shows up far beyond Deccan history.

The first connection is to Maratha Guerrilla Warfare Doctrine. The bargi-giri doctrine — fast light cavalry, raid-and-vanish, never hold ground you cannot defend — is usually told as a weapon aimed at the Mughals. Bijapur's fall shows the doctrine maturing against its own sponsor. Ali II subsidised the Marathas as a buffer; the forts of his kingdom then "one by one" fell to those same raiders during the regency.32 The structural insight here is that a guerrilla force's first laboratory was the patron who paid it: the doctrine was refined on the body of the kingdom that funded it, which is why a buffer-client strategy is so dangerous — you are training and financing your own dismemberment. Neither the doctrine page nor a flat "Mughal-vs-Maratha" framing surfaces that, because both look from the raider outward, not from the paymaster's collapsing treasury.

The second connection is to The Four-Kingdom Deccan and the Rise of the Marathas. That page frames the Deccan as a field of fractured sultanates whose disunity opened the door. Bijapur's fall is the door closing on one of those four kingdoms specifically, and it adds the mechanism the four-kingdom frame leaves implicit: division was not only between the sultanates but inside them — Bijapur's court was a loyalty market where nobles openly bid to become Mughal agents, and a regent could pledge a princess to Aurangzeb's son before his own city forced him to retract.33 The insight the two together yield is that "Deccan disunity" operated at two scales simultaneously, and the inner scale — a court selling itself faction by faction — was the one that actually opened the gates in 1686.

A third handshake runs to Afzal Khan, the Bijapur Nemesis. Afzal Khan was Bijapur's instrument against Shivaji, the general the sultanate sent to crush the upstart; this page is the same kingdom a generation later, reduced to buying Maratha protection for its own survival when its third regent's Mughal alliance collapsed.34 The reversal — Bijapur the hunter of Shivaji becoming Bijapur the client of his successors — is the clearest single measure of how far and how fast the Adil Shahi state fell. Lay the two pages end to end and you can finally date the flip precisely: the same court that mounted Afzal Khan's expedition is the court that, within roughly two decades, could no longer defend its own forts without Maratha cavalry. The Afzal Khan page is the high-water mark of Bijapur's offensive confidence; this page is the receding tide, and only by holding them in sequence does the speed of the drop become legible as a single human lifetime rather than an abstract "decline."

There is a fourth, deliberately stretched parallel worth naming honestly. The Habshi regents who ran the boy-king Sikandar's government — the Ethiopian-descended military elite the chapter title flags — connect loosely to the vault's African-diaspora material in Five-Tradition African Diaspora Map (North America). The stretch is real and must be stated: that page maps spiritual traditions carried across the Atlantic, not the Deccan's Habshi soldier-administrators carried across the Indian Ocean. But the structural rhyme is genuine — an enslaved-origin diaspora rising into the governing and military spine of the host society, holding real power (a Habshi regent ran the kingdom) precisely as that society fractured. The insight the rhyme produces is that diaspora elites often inherit power at the moment of a state's maximum weakness, which is also the moment that power is least worth holding; the Habshi regent of Bijapur in the 1670s and the diaspora structures the African-spirituality page tracks both occupy that bitter position of authority-without-foundation.

The Live Edge

Sharpest implication: the Adil Shahi sultanate's death is the strongest case in the Deccan story for the thesis that internal division, not external strength, decides these collapses — Bijapur out-revenued and out-mustered most of its neighbours, repelled the Mughal empire twice, and still fell, because a king's drinking and a boy-king's regents did what Aurangzeb's siege engines could not.

Generative questions:

  • If Ali II had disciplined his court instead of drinking after the 1666 victory, was Bijapur survivable, or was Mughal annexation structurally inevitable once Aurangzeb fixed on the Deccan?
  • The Marathas were both Bijapur's parasite and, briefly, its protector — at what exact point does a buffer-client flip into a successor, and is that flip ever visible to the patron in time?
  • Pillai uses the House of Bijapur painting as a death-omen read backward. How much of the "doomed dynasty" framing is hindsight imposed on what was, in 1680, just a routine genealogical portrait?

Connected Concepts

Footnotes

domainHistory
developing
sources1
complexity
createdJun 15, 2026
inbound links2