Medieval India: Delhi Sultanate to the Marathas
Learning Objectives
- Understand the fundamental concepts of Medieval India: Delhi Sultanate to the Marathas
- Apply key formulas and techniques to solve problems
- Practice with exam-level questions to build speed and accuracy
1. The Delhi Sultanate: Foundations of Muslim Rule in North India
1.1 Emergence of the First Dynasty – the Mamluk (Slave) Dynasty
The Delhi Sultanate began in the early thirteenth century when Qutb‑ud‑dîn Aibak, a former slave of Muhammad Ghori, established his authority over the territories captured from the Rajput confederacies. Aibak’s accession in 1206 marked the start of the Mamluk dynasty, which introduced a centralized administration centred on Delhi. The Sultanate’s early expansion was driven by the need to secure trade routes linking Central Asia with the Indian subcontinent and to extract tribute from the agrarian hinterland. The construction of the Qutb Minar complex symbolised both religious legitimacy and the assertion of political power.
1.2 The Khalji Expansion and Economic Reforms
In 1290, Jalāl‑ud‑dīn Khaljī seized the throne, inaugurating the Khalji dynasty. Khalji’s most notable ruler, Alauddin Khalji (r. 1296‑1316), pursued a policy of aggressive territorial expansion into the Deccan and Gujarat, thereby gaining control over the lucrative spice and textile trade. To finance these campaigns, Alauddin instituted market control measures, fixing prices of essential commodities and imposing strict grain procurement systems. These reforms curtailed the power of local merchants and increased state revenue, but also generated resentment among the agrarian classes, laying the groundwork for later rebellions.
1.3 The Tughluq Consolidation and Administrative Innovations
The Tughluq dynasty (1320‑1414) sought to consolidate the Sultanate’s vast territories through a series of administrative experiments. Muhammad bin Tughluq, known for his ambitious but often impractical policies, attempted to shift the capital from Delhi to Daulatabad in the Deccan to achieve a more central location. Although the relocation was reversed, the episode highlighted the challenges of governing a geographically dispersed empire. The Tughluqs also introduced a token currency system and a land revenue assessment based on the “iqta” system, which allocated land revenues to military officers in exchange for service.
1.4 The Sayyid Interregnum and the Rise of Regional Powers
Following the death of Firuz Shah Tughluq, the Sayyid dynasty (1414‑1451) ruled a weakened Sultanate, marked by internal factionalism and the resurgence of regional kingdoms such as the Bengal Sultanate and the Rajput states of Mewar and Marwar. The Sayyids were unable to restore central authority, and their reliance on mercenary forces eroded the Sultanate’s fiscal base. This period witnessed the gradual decentralisation of power, setting the stage for the emergence of the Lodi dynasty.
1.5 The Lodi Dynasty and the End of the Sultanate
The Lodi dynasty, founded by Bahlul Khan Lodi in 1451, represented the last Afghan‑ruled phase of the Delhi Sultanate. The Lodi rulers attempted to revive central authority through military reforms and alliances with Rajput chieftains. However, internal dissent and the inability to adapt to the evolving gunpowder technology of the emerging Mughal forces culminated in the decisive defeat of Ibrahim Lodi at the Battle of Panipat in 1526, which marked the termination of the Sultanate and the beginning of Mughal dominance.
2. Vijayanagara Empire: A Southern Counter‑Balance to the Sultanates
2.1 Founding and Ideological Foundations
In 1336, the brothers Harihara I and Bukka Raya I established the Vijayanagara Empire in the Deccan plateau, motivated by the need to provide a Hindu political centre that could resist the incursions of the northern Sultanates. The empire’s legitimacy rested on the concept of “dharmic kingship,” which combined Shaivite and Vaishnavite patronage, and on the strategic location of its capital on the banks of the Tungabhadra River, which facilitated control over the fertile Krishna basin and the lucrative spice routes to the Arabian Sea.
2.2 Territorial Expansion under the Sangama and Saluva Dynasties
The early Sangama rulers expanded the empire southwards, annexing the coastal regions of present‑day Karnataka and Kerala, thereby gaining access to the maritime trade in pepper and sandalwood. The Saluva dynasty (late 15th century) continued this expansion, but also faced repeated attacks from the Bahmani Sultanate, leading to a series of fortified frontier towns (garh) that served both defensive and administrative purposes.
2.3 The Golden Age of the Tuluva Dynasty
The reign of Krishnadevaraya (r. 1509‑1529) is regarded as the zenith of Vijayanagara’s political and cultural achievements. Under his rule, the empire extended from the Narmada River in the north to the Kaveri delta in the south. Krishnadevaraya’s patronage of literature produced the celebrated “Madhuravani” and “Amuktamalyada,” while his military campaigns against the Gajapati kingdom of Odisha and the Sultanates of Bijapur and Golconda secured the empire’s borders. The capital’s monumental architecture, exemplified by the Hazara Rama Temple and the Lotus Mahal, reflected a synthesis of Dravidian and Islamic styles, indicating a pragmatic approach to cultural integration.
2.4 Decline and the Aftermath of the Battle of Talikota
The decisive defeat of Vijayanagara at the Battle of Talikota in 1565, fought against a coalition of Deccan Sultanates, led to the sacking of the capital and the fragmentation of the empire into smaller successor states. Although remnants of the royal family continued to rule in peripheral regions, the loss of central authority marked the end of Vijayanagara as a dominant power, creating a power vacuum that would later be filled by the Marathas and the Mysore kingdom.
3. The Mughal Empire: From Babur’s Conquest to Aurangzeb’s Decline
3.1 Babur’s Invasion and the Establishment of Mughal Authority
Babur, a Timurid prince from Central Asia, entered the Indian subcontinent in 1526, capitalising on the disunity among the remnants of the Delhi Sultanate. His victory at the First Battle of Panipat, achieved through the effective use of field artillery and superior cavalry tactics, laid the foundation for Mughal rule. Babur’s memoir, the “Baburnama,” provides a vivid account of the early challenges of consolidating power over a culturally diverse landscape.
3.2 Akbar’s Administrative Synthesis and Religious Policy
Akbar (r. 1556‑1605) transformed the Mughal Empire into a centrally administered state by introducing the “mansabdari” system, which graded nobles based on the number of cavalry they maintained. This system created a professional bureaucracy that linked revenue collection directly to military obligations. Akbar’s policy of “Sulh‑i‑Kul” (universal tolerance) sought to integrate Hindus, Sikhs, Jains, and other communities into the imperial framework, exemplified by the establishment of the “Ibadat Khana” for inter‑religious dialogue. These measures fostered political stability and facilitated the empire’s expansion into Gujarat, Bengal, and the Deccan.
3.3 Shah Jahan’s Architectural Patronage and Economic Prosperity
Shah Jahan (r. 1628‑1658) presided over a period of economic prosperity, driven by the flourishing of textile exports, especially cotton and silk, and the expansion of maritime trade through the ports of Surat and Masulipatnam. His reign is renowned for monumental architecture, most famously the Taj Mahal, which symbolised the empire’s wealth and artistic synthesis of Persian, Islamic, and Indian motifs. The construction of grand gardens and public works also reflected the centralised fiscal capacity of the state.
3.4 Aurangzeb’s Expansionist Policies and the Seeds of Decline
Aurangzeb (r. 1658‑1707) pursued an aggressive policy of territorial expansion, extending Mughal control to the frontiers of the Indian subcontinent, including the annexation of the Deccan Sultanates of Bijapur and Golconda. However, his orthodox Islamic policies, such as the re‑imposition of the jizya tax on non‑Muslims and the destruction of several Hindu temples, alienated large sections of the population. The prolonged military campaigns in the Deccan strained the imperial treasury, while the rise of regional powers like the Marathas and the Sikhs began to challenge Mughal authority, setting the stage for the empire’s fragmentation after Aurangzeb’s death.
4. Regional Kingdoms and the Fragmentation of Central Power
4.1 The Rise of the Bengal Sultanate and Its Maritime Trade
Following the decline of the Delhi Sultanate, the Bengal region witnessed the emergence of an independent Sultanate in the early fourteenth century. Centered at Gauda and later at Pandua, the Bengal Sultanate capitalised on the fertile deltaic plains and the strategic position along the Bay of Bengal to develop a thriving maritime trade network with Southeast Asia and the Middle East. The Sultanate’s emphasis on shipbuilding and the export of muslin and rice contributed to its economic autonomy, while its patronage of Bengali literature fostered a distinct cultural identity.
4.2 The Ahom Kingdom in the Northeast
The Ahom kingdom, founded in the early thirteenth century in present‑day Assam, demonstrated remarkable resilience against external invasions, notably repelling Mughal attempts to annex the region in the seventeenth century. The Ahoms employed a sophisticated administrative system known as the “Paik” system, which organised labour and military service on a rotational basis. Their control over the Brahmaputra valley’s rice production ensured food security, while diplomatic marriages with neighbouring hill tribes facilitated political stability.
4.3 The Rajput Confederacy and Its Relations with the Mughals
Rajput states such as Mewar, Marwar, and Amber maintained a complex relationship with the Mughal Empire, oscillating between open rebellion and strategic alliance. The policy of “Mansab‑dar” appointments for Rajput nobles allowed the Mughals to co‑opt local elites, while the Rajputs retained a degree of autonomy in internal affairs. Notable episodes include the resistance of Maharana Pratap of Mewar against Akbar’s expansion and the later alliance of Jai Singh II of Amber with Shah Jahan, which exemplified the pragmatic diplomacy of the period.
4.4 The Emergence of the Sikh Misls in Punjab
In the late seventeenth and early eighteenth centuries, the Sikh community, initially a religious movement, evolved into a militarised confederacy known as the “Misls.” These semi‑autonomous units, each led by a chief (Sardar), controlled distinct territories in the Punjab plains. The Misls engaged in frequent skirmishes with Mughal forces and later with Afghan invaders, gradually consolidating power and laying the groundwork for the later Sikh Empire under Maharaja Ranjit Singh.
5. The Rise of the Marathas: From a Regional Power to a Pan‑Indian Force
5.1 Shivaji’s Foundational Vision and Guerrilla Warfare
Shivaji Bhonsle, born in 1630, founded the Maratha kingdom by exploiting the weaknesses of the waning Mughal authority in the Deccan. He pioneered the use of guerrilla tactics—rapid cavalry raids, fortified hill forts (gad), and a network of intelligence informants—to challenge larger Mughal armies. Shivaji’s coronation in 1674 as “Chhatrapati” established a sovereign Hindu polity that emphasized administrative reforms such as the “Ashta Pradhan” council, which distributed executive responsibilities among eight ministers.
5.2 Expansion under the Peshwa Leadership
After Shivaji’s death, the Maratha state experienced periods of internal strife, but the appointment of the Peshwa (prime minister) as the de‑facto leader in the early eighteenth century revitalised expansionist ambitions. The Peshwas, particularly Balaji Vishwanath and his son Bajirao I, extended Maratha influence northwards into Gujarat, Malwa, and the Bundelkhand region through a combination of diplomatic treaties (e.g., the “Treaty of Surat”) and military campaigns. Their strategy of demanding “chauth” (a quarter of the revenue) from conquered territories created a tributary system that financed further conquests.
5.3 The Maratha Confederacy and Its Administrative Structure
By the mid‑eighteenth century, the Maratha empire had evolved into a confederacy comprising semi‑autonomous chiefs such as the Holkars of Indore, the Scindhias of Gwalior, and the Bhonsles of Nagpur. Each chief maintained his own army and collected revenue, but they owed allegiance to the Peshwa in Pune, who coordinated joint military operations. This decentralised structure allowed rapid mobilisation of forces but also sowed seeds of internal rivalry that would later be exploited by the British.
5.4 The Third Battle of Panipat and Its Aftermath
The decisive encounter between the Marathas and Ahmad Shah Durrani’s Afghan forces at the Third Battle of Panipat in 1761 resulted in a catastrophic loss for the Marathas, halting their northward expansion. The defeat weakened the confederacy’s military capacity and exposed the vulnerability of its fragmented command structure. Nevertheless, the Marathas recovered under the leadership of Madhavrao I, who reinstated fiscal reforms and re‑asserted control over key regions, demonstrating the resilience of the Maratha political system.
| Aspect | Delhi Sultanate | Mughal Empire |
|---|---|---|
| Land Revenue Assessment | Iqta system – land assigned to military officers | Mansabdari system – graded nobles with revenue assignments |
| Centralisation | Relatively weak; power often devolved to regional governors | Strong central bureaucracy with provincial “subahs” |
| Legal Framework | Sharia‑based courts with limited codification | Combination of Sharia, customary law, and imperial edicts (farmans) |
| Military Organisation | Reliance on cavalry and slave soldiers | Standing army with artillery, infantry, and cavalry |
| Kingdom | Capital | Economic Base | Notable Cultural Contribution |
|---|---|---|---|
| Vijayanagara Empire | Hampi | Agriculture (rice, millets) and trade in spices, textiles | Vijayanagara architecture; patronage of Sanskrit and Telugu literature |
| Bahmani Sultanate | Bidar (later Gulbarga) | Control of Deccan trade routes; cotton and metalwork | Introduction of Persianate court culture in the Deccan |
| Vijayanagara’s Successor States (e.g., Mysore) | Various | Expansion of sugarcane and coffee cultivation | Fusion of Hindu and Islamic artistic motifs |
Discuss how the administrative innovations of the Mughal Empire under Akbar differed from those of the Delhi Sultanate, and evaluate the impact of these differences on the empire’s ability to govern a diverse subcontinent.
Solution: Akbar introduced the mansabdari system, which graded nobles by the number of cavalry they maintained, creating a merit‑based hierarchy that linked military service directly to revenue assignments. In contrast, the Delhi Sultanate relied on the iqta system, where land grants were given to officers without a standardized assessment of their military capacity. Akbar’s system facilitated a more efficient and centrally controlled bureaucracy, enabling better tax collection and troop mobilisation across vast territories. Moreover, Akbar’s policy of Sulh‑i‑Kul promoted religious tolerance, integrating Hindus and other communities into the administrative framework, whereas the Sultanate’s governance was more overtly based on Sharia law, limiting broader participation. These innovations allowed the Mughal Empire to sustain a larger, more diverse population, maintain fiscal stability, and project power far beyond the reach of the earlier Sultanate.
When answering a question on the rise of the Marathas, begin by linking Shivaji’s guerrilla tactics to the geographical advantage of the Western Ghats, then trace how the Peshwa’s fiscal policy of “chauth” transformed a regional power into a pan‑Indian confederacy; this logical progression demonstrates both cause and consequence, which is rewarded in answer‑writing.
6. Synthesis: Continuities and Transformations from the Sultanate to the Marathas
6.1 Patterns of Centralisation and Decentralisation
Across the medieval period, Indian polities oscillated between centralised authority and fragmented regional governance. The Delhi Sultanate’s early centralisation gave way to the decentralised rule of the Sayyid and Lodi dynasties, a pattern echoed in the Mughal era where strong emperors like Akbar and Shah Jahan were followed by the weakened authority of Aurangzeb’s successors. The Maratha confederacy epitomised a hybrid model: a central figure (the Peshwa) coordinated a network of semi‑autonomous chiefs, mirroring earlier Sultanate practices of delegating authority to provincial governors while retaining overall suzerainty.
6.2 Economic Foundations and Trade Networks
Economic vitality consistently underpinned political power. The Sultanate’s control of the Indo‑Gangetic plain facilitated grain surplus and tax revenue, while the Vijayanagara Empire leveraged coastal trade in spices and textiles. The Mughal Empire expanded this model by integrating maritime commerce through ports like Surat, creating a fiscal base that financed monumental architecture and a standing army. The Marathas, lacking a comparable maritime network, relied on tribute (chauth) and agricultural revenue from the Deccan plateau, illustrating a shift from trade‑based wealth to tribute‑based extraction.
6.3 Cultural Syncretism and Religious Policies
Religious tolerance and cultural patronage varied according to the ruler’s objectives. The early Sultanate imposed Islamic law but accommodated local customs to maintain order. Akbar’s Sulh‑i‑Kul represented an ideological commitment to inclusivity, fostering a composite culture that blended Persian, Central Asian, and Indian elements. In contrast, Aurangzeb’s orthodoxy reversed this trend, contributing to dissent. The Marathas, while championing Hindu identity, also employed Muslim administrators and adopted Persian administrative terminology, reflecting a pragmatic syncretism that ensured effective governance.
6.4 Military Evolution and Technological Adoption
From the cavalry‑centric armies of the early Sultanate to the gunpowder artillery of the Mughals, military technology shaped the trajectory of Indian states. The Marathas, initially reliant on light cavalry and guerrilla tactics, later incorporated European firearms and artillery, learned from both Mughal and European mercenaries. This adaptation allowed them to challenge both the declining Mughal forces and the emerging British East India Company, underscoring the importance of technological flexibility in sustaining imperial ambitions.
6.5 Legacy for Early Modern India
The medieval period set the structural foundations for early modern India. The administrative practices, revenue systems, and cultural syntheses developed under the Sultanate and Mughal empires were inherited, modified, or resisted by later powers such as the Marathas, Sikhs, and eventually the British. Understanding these continuities and transformations equips students to analyse the complex tapestry of Indian history and to appreciate how regional dynamics interacted with imperial ambitions to shape the subcontinent’s political landscape.
The Iqta System: Evolution, Assessment, and Limits under the Delhi Sultanate
The iqta was the principal instrument through which the Delhi Sultanate translated military service into revenue rights. Under Iltutmish the grant was essentially a temporary assignment of land revenue to a commander (muqti) who collected the produce, maintained a contingent of cavalry, and forwarded a surplus to the treasury. Balban tightened the system by insisting on regular audits (mahsul) and by limiting the size of iqtas to prevent the emergence of autonomous magnates. Alauddin Khalji introduced the most far‑reaching reforms: he ordered a comprehensive measurement (paimaish) of cultivated land, fixed the state demand at half the gross produce (kharaj), and required the muqti to deposit the assessed revenue in cash rather than in kind. This shift to cash collection reduced the muqti’s discretion and enabled the sultan to finance a standing army paid in silver tankas.
Despite these measures, the iqta retained structural weaknesses. The grant remained non‑hereditary in theory, yet in practice powerful muqtis such as the Tughluq nobles managed to transmit their assignments to sons, eroding central oversight. The system also lacked a uniform cadastral record; local revenue officials (amils) often relied on outdated estimates, leading to frequent disputes between the state and the assignee. Moreover, the iqta did not create a bureaucratic cadre loyal to the crown; loyalty was personal to the sultan, and a change of ruler could trigger wholesale reassignment, causing administrative discontinuity. The Lodi period saw a further dilution as iqtas were increasingly granted to Afghan tribal chiefs on a hereditary basis, accelerating the fragmentation that culminated in the Sultanate’s collapse.
Key Features of the Reformed Iqta under Alauddin Khalji
- Land measurement (paimaish) conducted by royal surveyors.
- State demand fixed at 50 % of gross produce (kharaj).
- Revenue collected in cash (tanka) and deposited in the central treasury.
- Muqti’s military obligation quantified: a fixed number of horsemen per iqta.
- Regular audits (mahsul) and penalties for shortfalls.
Mansabdari Reforms: Zat, Sawar, and the Fiscal‑Military Nexus under Akbar and Successors
Akbar’s mansabdari system replaced the loose iqta framework with a graded hierarchy that linked rank (zat), cavalry obligation (sawar), and salary (jagir) in a single numerical scale. Every noble received a mansab expressed as two numbers: the zat indicated personal status and salary entitlement, while the sawar specified the number of horsemen the holder must maintain. The emperor retained the power to revise both numbers, ensuring that military capacity remained under central calibration. Salaries were paid through revenue assignments (jagirs) that were theoretically transferable every few years, preventing the entrenchment of local power bases.
Under Jahangir the system acquired a dual‑track character: the introduction of the “du‑aspah sih‑aspah” (two‑horse three‑horse) distinction allowed a noble to hold a higher sawar than his zat, rewarding meritorious service without inflating his personal rank. Shah Jahan further rationalised the revenue side by standardising the jagir assessment (jama) against the empire’s measured produce (dastur‑ul‑amal), and by insisting that jagirdars submit annual accounts (waqia‑navis) to the diwan. Aurangzeb’s long reign saw a proliferation of mansabs — over 1,500 at its peak — and a growing gap between the nominal sawar and the actual cavalry maintained, as many nobles commuted their obligation into cash payments. This fiscal‑military disconnect weakened the empire’s field strength and contributed to the reliance on mercenary contingents in the Deccan campaigns.
Comparative Summary of Mansabdari Parameters
| Reign | Zat Range | Sawar Linkage | Jagir Transfer Frequency |
|---|---|---|---|
| Akbar | 10–10,000 | Sawar ≤ Zat | Every 3–4 years |
| Jahangir | 10–12,000 | Du‑aspah sih‑aspah allowed | Every 3 years |
| Shah Jahan | 10–10,000 | Strict sawar‑zat parity | Every 2–3 years |
| Aurangzeb | 10–12,000 | Wide sawar‑zat gap common | Irregular, often extended |
Vijayanagara’s Nayankara System: Provincial Governance and Revenue Extraction
The Nayankara (or amara‑nayaka) arrangement was the backbone of Vijayanagara’s territorial administration from the Sangama period onward. The emperor granted large tracts (amaram) to military governors (nayakas) in return for a fixed annual tribute (kavali) and a stipulated contingent of troops for imperial campaigns. Unlike the iqta, the amaram was often hereditary within a nayaka family, provided the tribute was paid punctually. The nayaka exercised judicial, fiscal, and military authority within his domain, maintaining a personal retinue and fortifying strategic hill‑top strongholds (durga).
Revenue collection under the Nayankara operated on a dual layer: the nayaka assessed the produce of his amaram using local measurement units (khanduga, putti) and forwarded the agreed tribute to the central treasury at Hampi. The empire supplemented this with a cadre of royal agents (mahamandaleshvara) who audited the nayaka’s accounts and ensured that the kavali reflected current agricultural output. In periods of strong central rule — notably under Krishnadevaraya — the audit was rigorous, and defaulting nayakas faced confiscation or military reduction. However, after the Battle of Talikota (1565) the central audit collapsed, and many nayakas asserted de facto independence, evolving into the later Nayaka kingdoms of Madurai, Tanjavur, and Gingee.
Distinctive Features of the Nayankara
- Hereditary amaram grants conditional on tribute compliance.
- Nayaka’s military obligation quantified in elephants, cavalry, and infantry.
- Local revenue assessment using regional units, not a uniform imperial standard.
- Royal auditors (mahamandaleshvara) with powers of inspection and penalty.
- Integration of temple endowments (devadana) into nayaka’s fiscal base.
Maratha Fiscal Instruments: Chauth, Sardeshmukhi, and the Confederacy’s Revenue Architecture
The Maratha confederacy’s financial engine rested on two levies extracted from territories outside their direct administration. Chauth (one‑fourth of the assessed revenue) was claimed as a protective tribute from Mughal or Deccan Sultanate provinces; in return the Marathas undertook not to raid the paying region. Sardeshmukhi (an additional ten per cent) represented the Maratha claim to the hereditary “sardeshmukh” right — a superior zamindari status over the same lands. Both levies were collected by the Peshwa’s agents (karkuns) who maintained detailed registers (daftar) of assessed villages, crop yields, and payment schedules.
Under Balaji Vishwanath and Baji Rao I the collection machinery was professionalised: the Peshwa appointed a “chauth‑sardeshmukhi” department headed by a senior Brahmin official (the “chauth‑peshwa”) who coordinated with regional commanders (sardars) such as the Holkar, Scindia, and Bhonsle houses. The revenue was remitted to the central treasury at Pune, where it funded the standing artillery corps, the navy at Kolaba, and the diplomatic missions to European powers. The system’s flexibility allowed the Marathas to expand their fiscal frontier without permanent annexation; however, it also created friction with local zamindars and Mughal subahdars, who frequently contested the legitimacy of the levies, leading to periodic military confrontations.
Operational Flow of Chauth Collection
- Survey of target pargana by Maratha revenue surveyors (potdars).
- Assessment of standard revenue (jama) based on Mughal dastur‑ul‑amal.
- Calculation of chauth (25 % of jama) and sardeshmukhi (10 % of jama).
- Issuance of sanad (grant) to local headman acknowledging Maratha suzerainty.
- Quarterly collection by karkuns; receipts recorded in daftar.
- Remittance to Pune treasury; audit by the chauth‑peshwa.
Deccan Sultanates: Military Organization, Gunpowder Adoption, and Diplomatic Strategies
The five successor states of the Bahmani kingdom — Ahmadnagar, Bijapur, Golconda, Bidar, and Berar — developed a distinctive military culture that blended Persianate cavalry traditions with indigenous infantry and an early embrace of gunpowder artillery. Each sultanate maintained a core of elite cavalry (bargirs) recruited from Persian, Turkic, and African (Habshi) groups, supplemented by locally raised foot soldiers (paiks) armed with matchlocks (toradar). The decisive factor in their sieges was the deployment of heavy bronze cannon (malik‑i‑maidan) cast at foundries in Bijapur and Golconda; the famous “Malik‑i‑Maidan” at Bijapur, weighing over 55 tonnes, exemplifies the scale of ordnance.
Diplomatically, the Deccan sultanates pursued a balance‑of‑power strategy: they alternated alliances with the Mughal Empire, the Portuguese at Goa, and the Vijayanagara Empire to prevent any single hegemon from dominating the plateau. Treaties often involved the cession of strategic forts (e.g., the 1636 Mughal‑Bijapur treaty ceding the fort of Parenda) in exchange for recognition of sovereignty over contiguous territories. The sultanates also cultivated Sufi shrines as channels of legitimacy, granting land endowments (inam) to prominent dargahs to secure popular support. By the late seventeenth century, however, sustained Mughal pressure under Aurangzeb — combined with internal succession disputes — eroded their military capacity, culminating in the annexation of Bijapur (1686) and Golconda (1687).
Key Military Assets of the Deccan Sultanates
| Sultanate | Heavy Cannon (nos.) | Matchlock Infantry (est.) | Elite Cavalry (bargirs) |
|---|---|---|---|
| Ahmadnagar | 12 | 8,000 | 3,500 |
| Bijapur | 20 | 12,000 | 5,000 |
| Golconda | 18 | 10,000 | 4,500 |
| Bidar | 6 | 4,000 | 2,000 |
| Berar | 5 | 3,500 | 1,800 |
- Confusing the iqta’s non‑hereditary principle with the mansabdari’s transferable jagir; the two systems operated on different legal bases.
- Assuming the Nayankara tribute (kavali) was a fixed cash amount; it was periodically reassessed based on agricultural output.
- Treating chauth and sardeshmukhi as identical levies; chauth was a protective tribute, sardeshmukhi a superior zamindari claim.
- Overstating the uniformity of Deccan artillery; each sultanate maintained independent foundries and calibres.
- Neglecting the role of Sufi endowments in legitimising Deccan sultanate rule; they were integral to political stability.
- Believing the mansabdari sawar always matched actual cavalry maintained; by Aurangzeb’s reign the gap was substantial.
- Review these traps regularly to avoid common errors in the examination.
Sher Shah Suri’s Administrative Reforms and Their Mughal Legacy
Sher Shah Suri (r. 1540‑1545) interrupted Mughal rule but left a bureaucratic template that Akbar later systematised. His most consequential innovation was the standardised land measurement (the paimaish) based on the bigha of 3,025 square yards, replacing the heterogeneous local units that had plagued revenue collection under the Lodis. He introduced a uniform cash revenue demand (the zabt) assessed at one‑third of the estimated produce, payable in silver rupees of a fixed weight (178 grains). To enforce this, Sher Shah created a hierarchy of revenue officers: the shiqdar (district collector), the amil (pargana‑level assessor), and the qanungo (hereditary record‑keeper). He also mandated the maintenance of a detailed cadastral register (daftar‑i‑mal) that recorded each cultivator’s holding, crop pattern, and payment history.
In the fiscal sphere, Sher Shah reorganised the currency system, issuing the silver rupiya and copper dam with consistent metallic content, and he established a network of sarais (caravanserais) at roughly 8‑kilometre intervals along the Grand Trunk Road to secure trade and postal communication. His military reforms included the branding of horses (dagh) and a descriptive roll (chehra) for every cavalryman, a practice Akbar adopted verbatim in the mansabdari system. The Suri emperor also codified a judicial code (the Qanun‑i‑Sher Shahi) that blended Islamic law with customary riwaj, appointing qazis at the pargana level and a chief qazi‑ul‑quzzat at the capital.
When Akbar regained the throne, he retained the Suri revenue terminology (zabt, bigha, daftar) and expanded the measurement to the entire empire through the Ain‑i‑Akbari. The dagh‑chehra system became the backbone of the mansabdari cavalry verification. Even the sarais network was extended, facilitating the movement of imperial officials and merchants. Historians therefore regard Sher Shah’s five‑year reign as a “administrative bridge” between the Sultanate’s iqta‑based extraction and the Mughal’s centralised, data‑driven fiscal‑military apparatus.
Mughal Land Revenue: Zabt, Dahsala, and the Ain‑i‑Akbari
The Mughal revenue system reached its most sophisticated form under Akbar’s finance minister, Raja Todar Mal. The zabt (cash revenue) replaced the earlier crop‑sharing (batai) in the core provinces (subahs) of Agra, Delhi, Lahore, Allahabad, and Malwa. Zabt required a decennial assessment (dahsala) — a ten‑year average of actual yields — to smooth out seasonal fluctuations. Revenue officials (amils) measured each field with the jarib (a 60‑gaz chain) and recorded the area in bighas using the standard Akbari bigha (2,500 square yards). The state demand was fixed at one‑third of the estimated produce, converted into cash at the prevailing market price (dastur‑ul‑amal).
The Ain‑i‑Akbari (Book III) enumerates four revenue categories: polaj (annually cultivated), parauti (fallow for one‑two years), chachar (fallow three‑four years), and banjar (uncultivated). Each carried a progressive tax rate, with polaj bearing the full one‑third demand and banjar a nominal cess. The register also lists cash crops (cotton, indigo, sugarcane) assessed at higher rates because of their commercial value. To prevent arbitrary exaction, Akbar instituted the taqavi (advance loans) system, allowing peasants to borrow seed and oxen from the state treasury, repayable at harvest.
Under Jahangir and Shah Jahan the dahsala cycle was generally respected, but Aurangzeb’s prolonged Deccan wars forced frequent re‑assessments and the re‑introduction of batai in newly conquered territories where cadastral surveys were incomplete. The zabt system’s reliance on accurate measurement and price data made it vulnerable to corruption: amils often under‑reported yields to pocket the difference, while qanungos manipulated registers to favour local zamindars. By the early eighteenth century, the breakdown of the decennial cycle and the rise of revenue farming (ijara) signalled the system’s decay, paving the way for the Maratha chauth and the British zamindari settlements.
Indo‑Islamic Architectural Evolution: Structural Techniques and Symbolic Programs
The transition from Sultanate to Mughal architecture reflects a shift from trabeate (post‑and‑lintel) construction to the arcuate (true arch, vault, dome) system, enabled by the mastery of lime mortar (chuna) and the use of red sandstone and white marble as facing materials. Early Sultanate monuments — Qutb Minar (1199‑1220), Alai Darwaza (1311), and the tomb of Ghiyas‑ud‑din Tughluq (1325) — employ corbelled arches and heavy rubble cores, with decorative bands of Quranic calligraphy in kufic and naskh scripts. The Lodi period (1451‑1526) introduces the double‑dome (an inner structural dome and an outer aesthetic shell) seen in the tomb of Sikandar Lodi, a technique that Mughal builders refined.
Under Babur and Humayun, Timurid influences appear: the charbagh (four‑quarter garden) layout, the pishtaq (monumental portal), and the use of glazed tile revetment (e.g., Humayun’s Tomb, 1565‑1572). Akbar’s reign marks a syncretic synthesis: the ibadat‑khana at Fatehpur Sikri combines Hindu chhatri pavilions with Persian iwan halls; the Panch Mahal employs a tiered, columnar structure reminiscent of Rajput palaces. Structural innovations include the pendentive transition from square chamber to circular dome, the use of squinches in the Diwan‑i‑Khas, and the introduction of jali (perforated stone screens) for light modulation.
Shah Jahan’s architecture epitomises marble veneer perfection and pietra dura inlay. The Taj Mahal (1632‑1653) showcases a double‑dome with a 35‑metre outer height, a four‑minaret composition for visual balance, and a riverfront terrace that integrates the Yamuna into the symbolic paradise garden. The Red Fort (1639‑1648) demonstrates a palace‑fort complex with a hierarchical spatial sequence: public audience hall (Diwan‑i‑Am), private audience hall (Diwan‑i‑Khas), and the imperial harem (Rang Mahal) each articulated through distinct arch forms — cusped, multifoil, and ogee respectively. Aurangzeb’s patronage contracts to the Bibi‑ka‑Maqbara (1660) and the Moti Masjid (1659‑1660), where ornamentation is restrained, reflecting both fiscal pressure and a shift toward orthodox aesthetic norms.
Maritime Trade, Port Cities, and European Factories in the Mughal‑Deccan World
The Indian Ocean littoral of the sixteenth‑seventeenth centuries was a polycentric commercial zone linking the Mughal heartland, the Deccan sultanates, and the European trading companies. The principal Mughal ports — Surat (Gujarat), Cambay, Broach, and Hugli (Bengal) — handled the bulk of textile exports (cotton piece‑goods, indigo, silk) and imported silver, horses, and luxury goods. Surat alone accounted for an estimated 70 % of Mughal maritime customs revenue (mahsul) in the 1620s. The Mughal state levied a 2.5 % ad valorem customs duty (sair‑jihat) collected by the mutasaddi (port commissioner) who reported to the diwan‑i‑tan (revenue minister).
In the Deccan, the sultanates of Ahmadnagar, Bijapur, and Golconda maintained ports at Chaul, Dabhol, Goa (Portuguese), and Masulipatnam. Golconda’s Masulipatnam became the primary outlet for the diamond and textile trade of the Qutb Shahi realm. The Portuguese Estado da Índia enforced a cartaz (pass) system, compelling Asian vessels to purchase safe‑conduct passes; this generated friction with Mughal and Deccan merchants, leading to periodic naval confrontations (e.g., the 1615 Mughal‑Portuguese clash at Surat).
The English East India Company secured a farman from Jahangir (1615) permitting a factory at Surat, followed by factories at Masulipatnam (1628), Hugli (1651), and Bombay (ceded by Portugal in 1665). The Dutch VOC established a chain of factories from Pulicat (1608) to Bengal (1635), focusing on spice and textile procurement. The French Compagnie des Indes arrived later, founding Pondicherry (1674) and Chandernagore (1688). European factories operated under farmans that granted extraterritorial judicial rights for their employees, a precedent for later colonial legal enclaves. By the early eighteenth century, the Mughal customs administration weakened, and European companies increasingly negotiated dastaks (duty‑free passes) — a practice that eroded state revenue and facilitated the transition to colonial fiscal dominance.
The Maratha Navy and the Angre Dynasty
While the Maratha land forces are well documented, their naval power** under the Angre family (c. 1690‑1756) constituted a unique indigenous maritime challenge to European naval supremacy on the Konkan coast. Kanhoji Angre (c. 1669‑1729), appointed Sarkhel (admiral) by Chhatrapati Shahu, established a fortified base at Vijaydurg (later Suvarnadurg) and a network of coastal forts — Kolaba, Khanderi, Underi — that controlled the approaches to Bombay and Goa. The fleet comprised gallivats (light oared vessels, 30‑40 tons), ghurabs (larger gun‑carrying ships, up to 300 tons), and captured European prizes refitted with Indian teak hulls.
Angre’s strategy combined convoy protection for Maratha‑allied merchantmen with privateering against Portuguese, English, and Dutch shipping that refused to purchase Maratha passes (dastaks). He levied a “sea‑chauth” — a 25 % customs duty on vessels entering the Konkan littoral — collected by his officers at the forts. The revenue financed the navy’s artillery (bronze cannon cast at Pune foundries), shipbuilding yards at Vijaydurg, and the maintenance of a standing marine infantry (maratha‑naval‑sepoys) trained in musketry and boarding tactics.
The Anglo‑Maratha naval confrontations culminated in the Battle of Kolaba (1721), where a combined British‑Portuguese squadron failed to dislodge Angre’s fortifications. Subsequent treaties (1731, 1740) forced the East India Company to recognise Angre’s sovereignty over the Konkan waters in exchange for a modest annual tribute. After Kanhoji’s death, his sons Sekhoji and Sambhaji continued the naval tradition, but internal succession disputes and the rising firepower of British line‑of‑battle ships eroded Maratha naval effectiveness by the 1750s. The Angre legacy demonstrates that indigenous naval architecture (teak hulls, lateen rigs, shallow draft) and decentralised fort‑based logistics could sustain a credible maritime deterrent against European joint‑stock companies for over half a century.
- Confusing the dahsala decennial average with an annual reassessment; the dahsala was explicitly a ten‑year cycle.
- Attributing the double‑dome innovation solely to the Mughals; it appears first in Lodi tombs and was refined by Mughal architects.
- Assuming the Portuguese cartaz system applied uniformly to all Asian ships; Mughal vessels often negotiated exemptions through farmans.
- Treating the Maratha sea‑chauth as identical to the land chauth; the maritime levy was a customs duty on shipping, not a protective tribute on agrarian revenue.
- Overstating the permanence of European factory privileges; farmans were revocable and frequently renegotiated with each new Mughal emperor.
- Neglecting the role of teak timber from the Western Ghats in giving Maratha ships superior durability compared to European oak in tropical waters.
- Believing the Angre navy operated as a centralized state fleet; it functioned as a semi‑autonomous hereditary admiralty with its own revenue base.
The Du‑Aspah Sih‑Aspah Mansab Innovation under Jahangir and Its Fiscal Consequences
Jahangir (r. 1605‑1627) inherited Akbar’s mansabdari framework but faced mounting pressure on the imperial treasury from prolonged Deccan campaigns and the costly maintenance of a large standing army. In response he introduced the du‑aspah sih‑aspah (two‑horse three‑horse) classification around 1620, a refinement that allowed a mansabdar’s sawar (cavalry) rank to exceed his zat (personal) rank without a proportional increase in salary. Under the original Akbari scheme the sawar could not be higher than the zat; the new rule permitted a mansabdar holding a zat of 5,000 to be granted a sawar of 7,000 (du‑aspah) or even 10,000 (sih‑aspah) provided he maintained the stipulated number of horsemen. The fiscal effect was twofold: the state could mobilise larger cavalry contingents for Deccan operations while keeping the cash outlay tied to the lower zat, and the mansabdars gained prestige and command authority without a matching rise in jagir revenue assignments.
The innovation required a more rigorous verification of troop musters. Jahangir’s waqia‑navis (news writers) and the mir‑bakshi (paymaster‑general) instituted periodic dagh (branding) inspections, recording the breed, age, and equipment of each horse. Fraudulent musters were punished by reduction of sawar rank and confiscation of jagir income. Contemporary chronicles such as the Tuzuk‑i‑Jahangiri note that the system temporarily swelled the imperial cavalry from an estimated 180,000 to over 250,000 effective horsemen by 1625. However, the reliance on hereditary jagirdars to supply the extra horses led to widespread short‑changing; many mansabdars substituted inferior ponies or inflated numbers on paper. The resulting revenue leakage prompted Shah Jahan, on his accession in 1628, to tighten the dagh protocol and to link sawar increments more closely to actual jagir yields, effectively curbing the du‑aspah sih‑aspah excesses.
From a fiscal‑military perspective the du‑aspah sih‑aspah experiment illustrates the Mughal state’s capacity for institutional improvisation. It decoupled ceremonial rank from cash expenditure, a principle that resurfaced in later Mughal reforms and in the Maratha saranjam grants. Yet the episode also underscores the structural limitation of a revenue system anchored in agrarian jagirs: any expansion of military manpower beyond the land’s surplus inevitably erodes central fiscal control.
Vijayanagara’s Mahanayakacharya and the Integration of Temple‑State Networks
The Mahanayakacharya (great leader of the nayakas) emerged in the early sixteenth century as the supreme coordinator of the nayankara provincial system that underpinned Vijayanagara’s territorial cohesion. Unlike the Delhi Sultanate’s iqta holders, the nayakas were not merely revenue farmers; they were military governors who also administered major temple complexes, controlled irrigation works, and mediated local trade. The Mahanayakacharya, appointed directly by the emperor (often from the royal Sangama or Tuluva lineage), exercised authority over the appointment, transfer, and audit of all nayakas, ensuring that the temple‑state nexus remained an instrument of central policy rather than a source of autonomous power.
Epigraphic evidence from the Karnataka Inscriptions (c. 1510‑1565) shows the Mahanayakacharya issuing sasana (royal orders) that mandated the allocation of a fixed share of temple revenues — typically one‑sixth of the kudam (grain measure) — to the imperial treasury, while the remainder funded temple rituals, feeding houses (annadana), and the maintenance of irrigation tanks (kere). This fiscal arrangement linked the spiritual legitimacy of the king (who styled himself Hindu‑raya‑suratrana) to the material prosperity of the agrarian base. The Mahanayakacharya also supervised the kavalgars (watchmen) who protected temple lands from encroachment, and coordinated the dasara festival processions that symbolically unified the dispersed nayaka territories.
The office’s effectiveness depended on a delicate balance: the Mahanayakacharya had to command the loyalty of powerful nayaka families (e.g., the Saluvas of Madurai, the Aravidus of Penukonda) while preventing them from converting temple endowments into private estates. The 1565 Battle of Talikota shattered this balance; the death of the reigning Mahanayakacharya, Rama Raya’s brother Tirumala, and the subsequent flight of the imperial court led to the fragmentation of the nayankara network. Surviving nayakas in the deep south (Madurai, Tanjavur, Gingee) retained the temple‑state model but operated as de facto independent kingdoms, a legacy that persisted into the Nayaka period of the seventeenth century.
The Ahom Paik System: Labour Organization and State Formation in the Northeast
The Ahom kingdom (c. 1228‑1826) sustained a unique corvée labour institution known as the paik system, which functioned as the backbone of its military, agricultural, and administrative apparatus. Every able‑bodied male between the ages of 15 and 50 was registered as a paik and assigned to a khel (guild) based on his hereditary occupation — cultivators (khar), artisans (silpa), boatmen (nau), or soldiers (senapati). Each khel was headed by a bora (chief) who reported to the phukan (minister) responsible for that sector. The state exacted a fixed quota of labour days per year: 60 days for agricultural work on royal lands (khet), 30 days for construction of forts, roads, and irrigation embankments, and an additional 20 days for military drills or active service during campaigns.
In return, paiks received a patta (land grant) of cultivable land, typically 2.5 bighas (≈ 0.6 ha), which they could cultivate for subsistence. The land was technically state property; the paik held usufruct rights contingent on continued service. This arrangement created a self‑replenishing pool of manpower that allowed the Ahoms to mobilise up to 30,000 troops for major expeditions — such as the 1671 Battle of Saraighat against the Mughals — without maintaining a standing salaried army. The system also facilitated the rapid construction of the garh (fortified capital) at Garhgaon and the extensive network of dongs (earthen embankments) that controlled the Brahmaputra’s floodplain.
Administratively, the paik registers (paik‑bahi) were updated annually during the Bihu festival, when village headmen (gaonburha) presented muster rolls to the borphukan (chief minister). Evasion was punished by confiscation of the patta and reassignment of the defaulter’s labour to a more onerous khel. The system’s resilience is evident in its survival through the Mughal‑Ahom conflicts, the Moamoria rebellion (1769‑1805), and the early British annexation; the British initially retained the paik registers for revenue assessment before replacing them with the ryotwari settlement in the 1830s.
Maratha Revenue Officials: Kamavisdar, Deshmukh, and the Decentralised Fiscal Architecture
The Maratha confederacy’s fiscal machinery rested on a layered hierarchy of revenue functionaries that balanced central oversight with local autonomy. At the apex stood the kamavisdar (also spelled kamavisdar), a salaried officer appointed by the Peshwa or the Chhatrapati to oversee a sarkar (revenue district) comprising several parganas. The kamavisdar’s duties included the annual jamabandi (settlement), verification of patta holdings, collection of chauth and sardeshmukhi from subordinate chiefs, and transmission of the net surplus to the central treasury at Pune. His remuneration consisted of a fixed tankha (salary) plus a percentage (usually 5 %) of the gross collection, incentivising efficient assessment.
Below the kamavisdar operated the deshmukh and deshpande, hereditary local magnates who controlled clusters of villages (mauzas). The deshmukh acted as the primary revenue farmer, responsible for measuring cultivated area (paimash), fixing the batai (crop‑share) rate — typically one‑third of the produce for the state — and maintaining the bahi (ledger) of cultivators. The deshpande served as the accountant, auditing the deshmukh’s returns and certifying the kabuliyat (agreement) with the kamavisdar. Both offices were hereditary but subject to confirmation by the central authority; failure to remit the agreed share could result in the grant being transferred to a rival family.
This decentralised architecture allowed the Marathas to extract revenue across a fluid frontier that stretched from Gujarat to Tanjore. The system’s flexibility is illustrated by the 1730s saranjam grants in the Carnatic, where the Peshwa assigned revenue rights to loyal commanders (e.g., the Bhonsles of Nagpur) who in turn appointed their own kamavisdars. However, the reliance on hereditary deshmukhs created pockets of entrenched interest that resisted central reforms — notably the 1761 attempt by Madhavrao I to introduce a uniform zabt cash assessment, which sparked the Deshmukh Rebellion in the Deccan. The episode highlights the tension between fiscal centralisation and the patrimonial networks that underpinned Maratha military mobilisation.
Gunpowder Fortifications in the Deccan Sultanates: Design, Artillery Placement, and Siege Warfare
The Deccan sultanates — Ahmadnagar, Bijapur, Golconda, Bidar, and Berar — pioneered a distinctive style of gunpowder fortification that blended Persianate military architecture with indigenous stone‑working traditions. From the late fifteenth century, rulers such as Mahmud Gawan (Bahmani) and later Yusuf Adil Shah (Bijapur) commissioned massive curtain walls up to 12 metres thick, faced with finely dressed basalt and reinforced by a core of rubble and lime mortar. The hallmark of these forts was the circular bastion (known locally as burj), designed to deflect cannonballs and provide overlapping fields of fire for the defenders’ own artillery.
Artillery placement followed a systematic geometry: heavy bronze topkhana (cannon) of 30‑40 pounder calibre were mounted on the upper tier of each bastion, while lighter swivel guns (zamburak) occupied the lower embrasures. The gol (gunpowder magazine) was sunk deep within the citadel, accessed via a vaulted passage to protect stores from direct hits. Water supply was secured through subterranean karez channels feeding cisterns (hauz) capable of sustaining a garrison of 5,000 for six months. The 1565 siege of Bijapur by the combined Vijayanagara‑Ahmednagar forces demonstrated the effectiveness of this design; despite a 40‑day bombardment with over 200 cannon, the citadel’s bastions remained intact, and the defenders’ counter‑battery fire inflicted heavy casualties on the besiegers’ siege works.
Siege warfare in the Deccan evolved into a duel of engineering. Attackers employed mines (tunnels packed with gunpowder) to breach walls, while defenders countered with counter‑mines and sorties by cavalry from sally ports. The 1686 Mughal siege of Golconda, led by Aurangzeb’s general Mir Jumla, saw the first extensive use of European‑style mortars (cast at the Mughal foundry in Agra) that could lob 100‑pound shells over the high curtain walls. Golconda’s fall after an eight‑month blockade owed less to wall breach than to the severing of its karez water supply and the exhaustion of food stores — a reminder that logistical resilience remained decisive even in the age of gunpowder.
- Confusing the du‑aspah sih‑aspah system with Akbar’s original mansabdari rules; the former allowed sawar to exceed zat, the latter did not.
- Assuming the Mahanayakacharya was a purely military post; he simultaneously managed temple revenues, irrigation, and nayaka appointments.
- Treating the Ahom paik system as a simple tax; it was a corvée labour obligation tied to hereditary land grants and military service.
- Equating the kamavisdar with the Mughal faujdar; the kamavisdar was a revenue officer with a salary‑plus‑commission structure, not a military governor.
- Believing Deccan bastions were copied directly from European trace italienne; they evolved independently from Persian‑Indian precedents before European influence.
- Overstating the permanence of Maratha saranjam grants; they were revocable and frequently reassigned during succession disputes.
- Neglecting the role of water management (karez, hauz) in Deccan fort endurance; sieges were often decided by hydraulic denial rather than wall breach.