History
History

The Siege Of Purandar 1665

History

The Siege Of Purandar 1665

For thirty years Shivaji's whole defence had rested on one fact everyone took for granted: you cannot drag a cannon up a mountain.
developing·concept·1 source··Jun 13, 2026

Cracking the Hill: How the Mughals Killed a Doctrine

For thirty years Shivaji's whole defence had rested on one fact everyone took for granted: you cannot drag a cannon up a mountain. The big guns lived on flat ground, because that was where carriages rolled and gun-crews could brace, and so the forts on the high crags of the Sahyadris were safe from the one weapon that flattened walls. In April 1665 Mirza Raja Jai Singh's gunners hauled artillery half-way up Purandar to a shelf the locals called the machi and fired down into a fort that had assumed it was out of range.1 A mine finished what the cannon started, and the sentinel-rock that held "the key to Purandar" came apart in eighty Mughal corpses and a gaping hole.2 This page is about a siege, yes — but really about the moment a piece of received wisdom died. The hill-fort doctrine that had protected Shivaji was not outfought. It was made obsolete by men who refused to believe a gun belonged on the ground.

The Citadel and the Strategist: What the Mughals Walked Into

Jai Singh did not march on Purandar by accident. He picked his camp at Saswad, to the east, over the obvious choice of Pune, because Saswad sat between Shivaji's state and Bijapur — letting him watch both, swing either way, and stop the two rivals from joining hands.3 Then he aimed at the right thing. Where the previous Mughal commander, Shaista Khan, had stopped touching forts after a bruising siege at Chakan and contented himself with grabbing open territory, Jai Singh understood that the hill forts were the state. "We have primarily to attack the hill forts," he wrote to Aurangzeb, asking for the big guns already lying with the Mughals and the cannons freshly cast.4 Inside Saswad's reach stood one of Shivaji's proudest citadels: Purandar. Checkmate Purandar, Jai Singh reasoned, and Sinhagad and Rajgad to the west would logically follow.5

The fort itself was a brute of a thing. Purandar rose 4,500 feet above sea level, and its base alone sat at over 2,500 feet.6 A garrison ten thousand strong held the summit and its outworks.6 To climb it you first had to take the lower fortress, and to take the lower fortress you had to get past Rudramal — a sentinel rock whose crest gave cover to everything below it.6 Jai Singh told Aurangzeb, correctly, that Rudramal held "the key to Purandar."7 Against this he threw more than twenty thousand men — Mughals, Rajputs, and Europeans in the artillery department — with the Afghan Diler Khan leading the thrust on the ground.8 And he did not point all his force at the one fort. He planted large teams across Maratha country so local officials would submit, ordered surrounding districts ransacked to forestall any daring relief, and instructed that any peasant or soldier who came over was to be welcomed and paid to break the back of Shivaji's forces.9 The siege was only the spearhead of a deliberately relentless, all-sides offensive.

The Gun on the Shelf (The Internal Logic)

Strip the siege down and the whole thing turns on a single piece of geography: the machi. A hill fort is built in tiers — open ground at the bottom, then a shelf part-way up where outbuildings and lower posts sit, then the bale-killa or top fort on the crown.10 Everyone understood that infantry could fight their way up tier by tier. What nobody on the Maratha side had priced in was that a cannon could be carried to that middle shelf and fired from there. Once a gun sits on the machi, the math of the fort inverts. The height that used to be pure protection — the thing that put the walls beyond reach — becomes a firing platform pointed at the defenders' own works.

Watch the sequence play out as a machine. The Mughals first chased the Marathas off the lower posts and burned the houses there, then dug trenches and ringed the fort from every side.11 On Jai Singh's order they aimed first at Rudramal, because Rudramal covered the lower fortress, and the lower fortress covered the top.7 It was laborious work — hauling the guns within striking distance of Rudramal's key points while the ten-thousand-strong garrison rained arrows, stones, and projectiles down on twenty thousand attackers.6 But the determined Mughals got there inside a few days and unleashed a volley of cannon fire that opened a breach.6 Then the sappers laid a mine along Rudramal's walls and blew a second gaping hole, throwing Purandar open to a full assault.6 The cannon and the mine were two halves of one idea: get the wall-breaking weapon up the hill, and the hill stops being a fort. The cost was real — eighty Mughals dead, over a hundred wounded just in breaching Rudramal — but Jai Singh then did the cleverest thing of all: he offered free passage to the garrison that surrendered there, hoping a clean exit would tempt the main garrison to fold without a fight.12

What the Hill Hands the Vault: Synergies & Handshakes

The siege of Purandar gives the rest of the vault a clean specimen of doctrine-death by technique — the moment a defensive system that has worked for a generation is broken not by more force but by a single overturned assumption. It is the structural inverse of the held-defile pages. Where Pavan Khind and Umbarkhind show terrain rationing the enemy down to a trickle the defenders can meet, Purandar shows what happens when the attacker cancels the terrain advantage outright: drag the decisive weapon to where the geography said it could never go, and the slot, the height, the layered tiers all stop saving you.13 It also pairs tightly with the fort-architecture page as the event that stress-tests the architecture — read the architecture page for how the tiers are built; read this one for the day a Mughal gun-crew proved the tiers were not enough. And it hands the Treaty-of-Purandar pages their pressure: the tent negotiation only makes sense once you feel how thoroughly the military situation had collapsed.

Analytical Case Study: The Letter That Bragged About a New Idea

The richest single moment of this siege is not the breach itself — it is a sentence in a letter. Jai Singh, satisfied with what his men had pulled off, wrote to Aurangzeb to crow, and in the crowing he named the innovation precisely. Until then, he said, it had been believed that cannons could only be used against forts that stood close to the ground.14 Then the certification: "But our campaign has established one thing. It is indeed possible to carry the big guns half-way up the hill forts, to the very place the people of these regions called the machi. From that spot, a highly effective assault can be launched on the fort. That's precisely what we did in the case of Rudramal."15

Slow down on what that sentence is doing. A commander in the field is telling his emperor, in writing, that a settled rule has just been falsified. He is not reporting a victory so much as a discovery — and he knows it, which is why he frames it as "our campaign has established one thing." This is the rare case where the man who broke the doctrine narrates the breaking in his own words, and the words survive. The whole subtle-body of hill-fort warfare in the Deccan turned on the unspoken premise that artillery lived on the plain. Jai Singh's gunners did not argue with the premise. They carried a gun to the machi and let the result do the arguing.

Then watch the second move in the same letter, because it is just as telling. Having claimed a genuine first, Jai Singh immediately hands the credit upward: there was no doubt Diler Khan and his men had done an excellent job, "but in truth, all of this happened because of the Badshah's great good fortune, his manifest destiny."16 The enemy, he added, had never before experienced such a disaster, and "Shivaji has been taught a real big lesson."16 In two breaths he both claims the innovation and disowns it — the technique is his army's, the glory is the emperor's. The gloating and the supplication ride in the same paragraph. That is the texture of how a frontier general talks to a paranoid sovereign: prove your competence, then bury it under the sovereign's destiny so the competence never reads as a threat.

What makes the episode load-bearing is that the brag is also the evidence. We know the machi-gun tactic was felt as a breakthrough precisely because the man who used it bragged that it overturned a belief. The boast is the primary source for the doctrine's death.

Implementation Workflow: Standing on the Machi

You are half-way up the hill, on the shelf the locals call the machi, and your shoulders ache from what it took to get the gun here. Below you the gun-crews are still cursing the slope; above you the garrison thinks the fort's height has kept them safe, the way it always has. Feel the assumption hanging in the air — guns belong on the ground — an assumption so old nobody on the crag has thought to test it for a generation. Now look at the gun beside you, level it, and notice what the height has just become. The protection has flipped into a platform. The thing that made the defenders safe is now aimed back at them.

That is the move, and it transfers off the mountain cleanly. Whenever you face a position that has held for years, do not pour more of the obvious force at it. Find the rule everyone treats as a law of nature — the guns can't go uphill of that situation — and ask what it would take to falsify it. The decisive weapon is rarely missing; it is just sitting where the rule says it has to stay. Drag it to the shelf nobody thought to climb. And when it works, remember the second half of Jai Singh's letter: claim the discovery long enough to learn from it, then be ready to set the credit down where the people above you need it to sit. The technique buys the fort. The humility buys you permission to keep using it.

The Stalled-Siege Failure (Diagnostic Signs)

You can tell the machi insight has been lost when an army keeps hammering the base of a hill fort, taking the lower posts again and again and never threatening the crown. That is force without the overturned assumption — Shaista Khan's pattern, the commander who stopped touching forts after one hard siege and settled for grabbing flat territory instead.17 Grabbing the open country feels like progress and changes nothing, because the state lives on the crags. The diagnostic sign is a campaign that is busy everywhere and decisive nowhere.

The second failure sign is the opposite: a commander so in love with one clever breach that he forgets the siege is only the spearhead of a wider squeeze. Jai Singh avoided this — even as the guns climbed Rudramal he had six thousand troops torching fifty villages near Rohida, reaching Rajgad's gates, and devastating Kondhana's neighbourhood, so that Shivaji could never concentrate to relieve the fort.18 An army that wins the technical breakthrough but lets the enemy mass freely elsewhere has cracked the hill and lost the war. The healthy version keeps both hands working: the new tactic at the point of decision, and relentless pressure across the whole country so the point of decision can never be reinforced.

Evidence / Tensions / Open Questions

This account is [POPULAR SOURCE] — Purandare is writing a narrative biography for a general readership, not a critical siege study.19 What gives the chapter unusual spine, though, is that its central claims rest on Jai Singh's own dispatches to Aurangzeb, which Purandare quotes directly: the "we have primarily to attack the hill forts" instruction, the "key to Purandar" identification of Rudramal, and above all the machi-gun innovation passage.20 These are a commander's contemporaneous letters, not a later chronicler's embroidery, which makes the artillery-doctrine claim sturdier than most popular-source material. Treat the specific casualty figure at Rudramal — eighty dead, over a hundred wounded — as [SINGLE SOURCE], since it comes through this one narration without corroboration on the page.12

A genuine interpretive tension sits underneath the triumphal letters: Jai Singh is the only voice describing his own success, and self-reported dispatches to a sovereign have every incentive to inflate. "Things which would have been impossible to do in a month are being accomplished in a day," he tells Aurangzeb — a line that is plainly courtier's rhetoric as much as field report.21 The reader has to hold the verifiable mechanical claim (a gun was carried to the machi and it worked) separately from the boast wrapped around it (manifest destiny, a real big lesson taught). Open questions follow. How novel was the machi-gun tactic really, across Deccan siegecraft as a whole, versus how novel Jai Singh needed it to sound to his emperor? And how much did the offered free passage at Rudramal — the psychological lever — do the work that the cannon gets credited for?

Author Tensions & Convergences

Purandare is the sole modern voice on this page, so the tensions to read are the ones embedded inside his sourcing — and here the dominant embedded voice is unusual: it is the antagonist's own paperwork. Most of this chapter is built on Jai Singh's letters to Aurangzeb, which means Purandare is narrating Shivaji's worst military disaster substantially through the documents of the man who inflicted it.20 That tilts the texture. Against the Maratha chronicle tradition — the Sabhasad Bakhar register that elsewhere supplies the heroic Murar Baji material — the Mughal dispatch is colder, more administrative, more interested in logistics and credit-management than in valour. The convergence between the two registers is real and worth stating first: nobody disputes that Purandar's outworks fell, that Rudramal was breached by cannon and mine, that the siege went hard against the Marathas. The event is agreed across the hostile and the sympathetic sources alike. The tension is one of frame. Read through Jai Singh's letters, Purandar is a feat of imperial engineering and the emperor's destiny made manifest; read through the Sabhasad strain, the same weeks are the stage for Maratha martyrdom. What the split reveals about the concept is that a doctrine-death looks completely different depending on which end of the breach you are standing at. To the gunner on the machi it is a discovery to brag about; to the garrison above it is the day the mountain stopped being a friend. Purandare's quieter service is to let the antagonist's voice carry the technical truth — because on the narrow question of how the hill was cracked, the man who cracked it is the better witness, even if his glory-talk has to be peeled off first.

Cross-Domain Handshakes

A siege and a treatise on spycraft and a study of humiliation do not obviously belong on the same shelf, but the siege of Purandar reaches all three because the thing it really documents is an assumption breaking — and broken assumptions are a problem that runs across war, intelligence, and the psyche.

The first handshake is to Sun Tzu — Field Intelligence and Signal Reading. Jai Singh's whole campaign is a Sun Tzu problem solved correctly where Shaista Khan solved it wrong. Sun Tzu's core demand is that the commander read the actual structure of the enemy's strength rather than the obvious surface of it — and Jai Singh's letter, "we have primarily to attack the hill forts," is exactly that reading: he saw that the forts, not the open territory, were the state.4 The structural parallel is precise. Sun Tzu warns against attacking where the enemy is merely visible instead of where he is load-bearing; Shaista Khan attacked the visible territory and changed nothing, Jai Singh attacked the load-bearing crags and won. But there is a tension the field-intelligence frame alone does not produce: Sun Tzu prizes winning without fighting, and Jai Singh's machi innovation is the opposite — a brute-force technical breakthrough that made the unfightable fightable. The insight that falls out of holding both together is that signal-reading tells you where to strike, but it does not generate the technique that lets you strike there; intelligence picks the target, and only an overturned engineering assumption opens it. The two are separate competences, and Purandar needed both.

The second handshake is to Psychological Resilience and the Survival of Humiliation. Purandar is the lowest point of Shivaji's career to date — the day his founding defensive doctrine was proved breakable and his proudest citadel was cracked open. The connection is one of sequence: a person and a state both face the same crossroads after a doctrine dies, which is whether the broken assumption breaks them too. The resilience page studies how a self metabolizes a humiliation without collapsing into it; the siege gives that abstraction a hard historical instance, because Shivaji's response to Purandar's fall was not despair but the tent negotiation and the Treaty of Purandar — a survival-of-humiliation move that converted military defeat into a temporary political settlement he would later overturn.22 The structural parallel is that resilience, at both the psychological and the strategic level, is precisely the refusal to treat a single broken assumption as a broken self. The insight neither domain produces alone: a humiliation is survivable exactly to the degree that you can quarantine what was broken — one fort, one doctrine — from the wider identity it threatens to take down with it. Shivaji lost the hill-fort doctrine at Purandar and kept the state; the psychology of that quarantine is what the resilience page names, and the siege is what it looks like under cannon fire.

There is a sharper point hiding where the two handshakes meet. Jai Singh read the structure correctly (the Sun Tzu side) and he managed Shivaji's humiliation deliberately (the resilience side) — the free passage offered to the Rudramal garrison, the relentless burning of fifty villages, the letter declaring Shivaji "taught a real big lesson" are all moves aimed not only at the fort but at the enemy's morale and self-image.18 What the combined reading exposes is that the most dangerous opponent is the one who attacks your assumptions and your resilience at once: he breaks the doctrine with a gun on the machi, and in the same campaign he works to make the breaking feel total, so that you mistake one lost fort for a lost cause. Shivaji's counter — surviving the siege into a negotiated treaty rather than a collapse — is the textbook case of refusing exactly that conflation, and neither the field-intelligence frame nor the resilience frame, taken alone, would let you see that the attack and the defence were both being fought on two boards simultaneously.

The Live Edge

The Sharpest Implication. The most destabilizing thing this page says is that your most reliable defence is exactly the thing most likely to kill you, and for the same reason. Shivaji's forts were safe for thirty years because everyone believed guns couldn't climb hills — and that very reliability is what stopped anyone from testing the belief. A defence that has never failed is a defence nobody has pressure-tested, which means the assumption holding it up has been quietly aging into a liability the whole time. The longer something protects you, the more dangerous the day someone drags a cannon to the shelf.

Generative Questions. (1) Where in a modern operation — a business moat, a personal routine, a national-security posture — does the equivalent of "guns can't go uphill" still hold, an unexamined rule treated as a law of nature simply because it has never been tested? (2) Jai Singh claimed his innovation and disowned it in the same letter; is that double-move — prove competence, then bury it under the sovereign's glory — a repeatable survival tactic for talented people under paranoid authority, and what does it cost the institution when its best operators have to hide their best work?

Connected Concepts

Footnotes

domainHistory
developing
sources1
complexity
createdJun 13, 2026
inbound links7