Karnataka’s Cabinet approved a five-year Sustainable Data Centre Policy on 18 September 2026. The headline is a target of 1 GW of cumulative data-centre IT load by 2031, paired with energy- and water-efficiency measures. The practical question is not just what the policy promises, but which benefits are operational, how performance will be measured, and whether a proposed site can actually secure power, water and fibre.
Executive summary
Karnataka’s Sustainable Data Centre Policy 2026–2031 is designed to attract digital infrastructure investment while making resource use part of the state’s data-centre plan. Reporting on the Cabinet decision describes a five-year framework with a revised budgetary framework of ₹1,300.45 crore, a 1 GW cumulative data-centre IT-load target by 2031, and an ambition to account for 10–12% of India’s AI-ready data-centre ecosystem.
Those numbers need to be read in the right category. A target is not installed capacity; a policy budget framework is not a grant cheque for each project; a park plan is not an operating campus; and eligibility language is not proof that a particular applicant will receive an incentive. Karnataka had already discussed a combined 1,000 MW of proposed data-centre parks in the Bengaluru region, Mysuru and Mangaluru. Do not automatically add that earlier park figure to the new statewide 1 GW target: the scopes may overlap.
The policy’s distinctive feature is its attempt to tie some benefits to measured energy and water performance. The Hindu reports that the policy text it reviewed includes plant-wise reporting of Power Usage Effectiveness (PUE) and Water Usage Effectiveness (WUE), a PUE-linked one-time incentive, renewable-energy support and treated-water reimbursement. The News Minute reports additional eligibility and implementation details, including registration through Karnataka Innovation and Technology Services (KITS), with separate operational guidelines still to be detailed.
For developers, operators and suppliers, the sound response is structured diligence—not treating incentives as bankable before rules are published and a project qualifies. Confirm the current policy notification, application process, measurement boundary, baseline, audit requirements, caps, payment timing, land status, power-delivery schedule, water source and fibre-route diversity. The state’s resource mapping may help investors compare sites, but it cannot replace project-level utility confirmation.
Contents
- At a glance
- What the policy is trying to change
- Read the 1 GW target and ₹1,300.45 crore framework carefully
- Which incentives are reported, and what still needs verification?
- Why PUE and WUE are useful—but incomplete
- Beyond Bengaluru: parks, corridors and Mangaluru
- Who may participate in the policy ecosystem?
- A due-diligence checklist for projects and suppliers
- What the policy does not prove
- Frequently asked questions
- Related Gridvik research
- Sources and research note
At a glance
| Item | Reported position | How to interpret it |
|---|---|---|
| Policy | Karnataka Sustainable Data Centre Policy 2026–2031 | A state policy framework approved by the Cabinet; implementation details matter. |
| Approval | 18 September 2026 | Cabinet approval is not the same as a project approval or incentive sanction. |
| Capacity ambition | 1 GW cumulative data-centre IT load by 2031 | A policy target, not present operational capacity or a committed construction schedule. |
| Ecosystem ambition | 10–12% of India’s AI-ready data-centre capacity by 2031 | A stated ambition; the public reporting does not supply a complete measurement methodology. |
| Framework | Revised five-year budgetary framework of ₹1,300.45 crore | Not a per-project award and not necessarily a single pool of direct subsidies. |
| Sustainability | PUE and WUE reporting, renewable-energy support, treated-water incentives and resource mapping | Exact conditions should be checked against the policy notification and operational guidelines. |
| Regional emphasis | Proposed zones and parks, including Hoskote, Mysuru and Mangaluru in related state plans | Proposed sites and planned capacity should not be described as operating facilities. |
The Cabinet approval and headline targets were reported by The Hindu and Moneycontrol on 18 September 2026. The more detailed sustainability provisions below are attributed to reporting that describes or quotes the policy text.
What the policy is trying to change
Karnataka is already a significant technology and enterprise-services market, but data-centre projects have to compete on more than customer demand. A large campus requires land, a credible route to grid capacity, equipment and construction delivery, water planning, fibre access, permits and a customer pipeline. AI workloads add another layer: higher rack densities and accelerated-computing systems can change cooling, electrical design and network requirements.
The new policy’s stated direction is to make growth more deliberate. It combines investment promotion with a sustainability lens: renewable energy, energy efficiency, advanced cooling, water management, emissions mitigation, and state-level mapping of resource availability. It also contemplates data-centre zones or parks and a Centre of Excellence to support research, training and ecosystem development. These measures matter only if they translate into clear procedures, useful infrastructure and verifiable performance requirements.
The change in emphasis is important. A policy that simply lists large investment intentions can attract attention; a policy that connects incentives to measured resource use may influence design and operating decisions. But the distinction between an incentive framework and a binding environmental standard remains material. Reporting on the policy notes both performance-linked support and continuing questions about disclosure, local water stress and what PUE or WUE alone can tell a community.
For background on how electricity access, policy and project timing interact across states, see Gridvik’s India data-centre power and grid-readiness guide. This Karnataka policy article is narrower: it focuses on the state’s 2026–2031 framework and the questions to resolve before using its terms in a project model.
Read the 1 GW target and ₹1,300.45 crore framework carefully
A state target is not a capacity ledger
The reported target is 1 GW of cumulative data-centre IT load by 2031. “IT load” refers to the electricity used by computing equipment, rather than simply the size of a building or the total power consumed by a facility. The distinction matters because market reports sometimes use operational IT capacity, total facility power, leased capacity, planned capacity or construction pipeline. Those figures cannot be compared without aligning definitions and dates.
The 1 GW ambition should therefore be treated as a policy objective—not as 1 GW already available to customers and not as a verified pipeline of projects. To measure progress, a future public dashboard would need to state which facilities count, whether capacity is operational or planned, how IT load is certified, and how expansions are handled. Until those definitions are available, avoid comparing the target directly with a third-party market estimate that uses a different basis.
The state’s 10–12% ambition for India’s AI-ready data-centre ecosystem has the same limitation. “AI-ready” is not a universal capacity category unless the reporting specifies density, cooling, power and network criteria. The ambition signals direction; it does not tell a buyer how much GPU capacity is currently live.
The policy framework is not the same thing as project spending
News reports describe a revised budget framework of ₹1,300.45 crore over the policy period. That figure communicates the state’s proposed programme scale. It should not be called a confirmed cash transfer to operators, the guaranteed value of approved applications, or the construction cost of a park. The framework covers more than one type of support, and the distribution of any assistance depends on final rules, eligible applicants, verification and available programme budgets.
For an investor or supplier, this changes how the number belongs in a spreadsheet. It is a policy-level signal, not revenue. Model a proposed incentive as a conditional scenario until the applicant, project phase, qualifying costs, caps, payment date and evidence requirements are known. Keep it separate from contracted customer revenue, committed financing and delivered infrastructure.
Avoid adding overlapping park figures
Before the policy approval, Karnataka had publicised a combined plan for roughly 1,000 MW of data-centre parks across the Bengaluru region, Mysuru and Mangaluru. The earlier park announcement reported by The Hindu is useful context, but its proposed capacity may sit within the broader policy ambition. The policy’s 1 GW target and the earlier 1,000 MW park plan should not be summed as 2 GW unless a primary document explicitly establishes that they are separate, additive targets.
This is a recurring problem in data-centre market analysis: a park’s announced capacity, an operator’s campus plan, a tenant’s reserved capacity and a state’s policy target can all refer to the same physical development at different levels. Gridvik’s India data-centre investment map explains how to keep those layers separate.
Which incentives are reported, and what still needs verification?
The Hindu’s 2 October report says it reviewed the policy text. The News Minute’s 30 September report provides additional details and says separate operational guidelines will explain registration. The table below is a summary of what those outlets report—not a legal eligibility opinion or a substitute for the official notification.
| Reported measure | Publicly reported terms | Practical questions before relying on it |
|---|---|---|
| Renewable-energy use | The Hindu reports an incentive of ₹0.50 per unit for units sourcing more than 50% of total energy from renewable sources, for five years, subject to an overall cap of ₹1.25 crore. | Which accounting period and energy boundary apply? How are captive, open-access and contracted supplies evidenced? Is the rate net of other benefits? |
| Treated-water use | Full reimbursement of treated-water procurement and use charges, capped at ₹8 lakh per year for five years from commercial operations, as reported by The Hindu and The News Minute. | Which sources qualify as treated water? Which invoices, meters and treatment standards are accepted? Does the cap apply by unit, project or entity? |
| PUE performance | A one-time ₹20 crore incentive is reported for qualifying PUE of 1.00–1.20, after the prescribed result is demonstrated consistently for three years; payment is described as occurring in the fourth year. | What measurement protocol, facility boundary, independent audit and qualifying period are required? What happens after expansion or a change in IT load? |
| WUE performance | The Hindu reports a WUE threshold expressed as 0.7–1.3 litres per kWh and reimbursement of 100% of water charges up to ₹30 lakh per year for two consecutive years after three years of qualifying performance. The News Minute describes the range as between 0.7 and 1.3 L/kWh. | Confirm the precise threshold notation, eligible water charges, baseline and monitoring method in the official rules. The public summaries do not replace the detailed calculation protocol. |
| Large strategic projects | The News Minute reports that projects above ₹3,000 crore may be considered for a customised incentive package, subject to individual assessment. | What counts as project investment, strategic importance and environmental/technical feasibility? “May be considered” is not an award. |
| Research and development | The News Minute reports support of up to 50% of eligible expenditure, capped at ₹15 crore per project, for qualifying R&D. | Which organisations, cost categories, milestones and intellectual-property conditions qualify? |
Several of these measures are conditional on years of operating performance. A developer cannot safely book a future reimbursement as an immediate reduction in construction cost. A lender cannot assume a grant will arrive before its stated verification period. A supplier should not promise a customer a benefit until the customer’s eligibility and application path are confirmed.
The same discipline applies to the 30+30-year lease and shared-infrastructure provisions described for proposed parks in reporting. A reported model for land tenure or common utilities is not proof that a particular parcel is allotted, serviced or available to a specific applicant. Confirm parcel boundaries, lease terms, utility agreements, environmental permissions and the responsible agency directly.
Why PUE and WUE are useful—but incomplete
PUE, or Power Usage Effectiveness, compares total facility energy with energy used by IT equipment. A lower ratio generally indicates that a smaller share of facility energy is being spent on overheads such as cooling and electrical conversion. WUE, or Water Usage Effectiveness, compares water use with IT energy consumption; it is often expressed in litres per kilowatt-hour. A lower WUE generally indicates lower water use per unit of IT energy, subject to the accounting boundary and water-source definition.
These metrics help compare operating efficiency, but they do not answer every sustainability question. A low PUE does not reveal total electricity consumption: a very large site can be efficient per unit and still consume substantial power. PUE also does not tell the reader whether that electricity is renewable or how carbon-intensive the grid supply is. A WUE ratio does not, by itself, reveal whether water came from a stressed aquifer, municipal supply, tanker, desalination or reclaimed wastewater. The local basin and the absolute volume still matter.
A credible measurement framework should make the denominator and boundary explicit. For example: which meters count toward total facility energy; how energy used by shared campus systems is allocated; how IT energy is measured; whether generator testing is included; and how reclaimed water is treated in the WUE numerator. A policy benefit tied to a ratio should state these rules, specify who audits the readings and explain how a project can challenge or correct an error.
There is also a difference between encouraging good performance and requiring disclosure before approval. The Hindu’s reporting records expert concerns that efficiency ratios alone may not disclose absolute demand or local impacts. Operators, communities and public agencies need enough information to evaluate projected water and power draw at the location—not only a ratio after the site is running.
This is why the policy’s proposed resource mapping could be important. A useful map should be granular enough to show feeder and substation capacity, upgrade timing, water sources and local stress, wastewater-treatment capacity, fibre routes and other constraints. A statewide average is not a site-feasibility certificate.
Beyond Bengaluru: parks, corridors and Mangaluru
The policy is also presented as a way to extend digital infrastructure beyond Bengaluru. Hoskote, Mysuru and Mangaluru appear in reporting on proposed parks or zones. Mangaluru has a specific strategic narrative: coastal location, potential cable-landing infrastructure, port-linked activity and scope to diversify the state’s digital infrastructure. The News Minute reports proposed common infrastructure such as dual-grid connectivity, substations, water and high-capacity fibre for the parks.
That is a planning rationale, not proof that every required asset exists today. A coastal location may offer a future route for international cable connectivity, but a cable landing station still requires permitting, partners, terrestrial backhaul, power, security and commercial demand. A proposed park needs confirmed land, environmental approvals, power delivery, water arrangements and a realistic construction schedule. Each item is a separate milestone.
A data-centre developer assessing locations should compare a site on a bundle of delivered services rather than the state name alone:
- Power: available MW by phase, connection voltage, substation scope, redundancy, tariff, upgrade responsibility and energisation date.
- Water: permitted source, monthly/seasonal availability, treated-water quality, storage, reuse plan and local basin conditions.
- Connectivity: at least two physically diverse fibre routes, carrier options, latency to customers and cloud/network exchange points, repair pathways and rights of way.
- Land and approvals: title or lease status, permitted use, environmental clearances, flood and heat risks, construction access and community considerations.
- Customers and skills: proximity to enterprise demand, cloud regions, research institutions, hiring base and operating partners.
- Resilience: exposure to coastal hazards, flooding, heat, grid events, transport disruption and single points of failure.
A new region can improve portfolio diversity only if the underlying supply chain is ready. A second campus on paper does not create redundancy if it depends on the same transmission corridor, water source or fibre duct as the first.
Who may participate in the policy ecosystem?
Reporting on the policy says it covers data-centre units and park developers, operators, cloud service providers, edge data centres, submarine cable and cable-landing-station infrastructure, and allied participants. Some demand-centre support may extend to companies, research institutions, start-ups or manufacturers that use data-centre services or contribute to the supply chain. The precise beneficiary and registration rules need confirmation in the operational guidelines.
Data-centre developers and operators
For a campus developer, the policy could influence site choice, power procurement, cooling design, water treatment, reporting systems and the financial model. The work is to convert a high-level benefit into a documented application path: eligibility, required investment, start date, commissioning milestone, performance period, audit and reimbursement timing.
Cloud and AI service providers
A cloud company may be a tenant, customer or service provider without owning the land or shell. The policy’s definition of eligible entities and any requirement for a Karnataka registered office could affect who files for an incentive. A tenant should ask the landlord which party owns meters, supplies water data, files applications and receives any benefit passed through in pricing.
Suppliers, MSMEs and research partners
Electrical equipment, cooling, water-treatment, fibre, monitoring, controls, construction and testing suppliers may see opportunities as projects move from policy to design and procurement. Policy mention alone is not a purchase order. For a sales plan, separate an announced initiative from a funded tender, a qualified vendor list, a released specification and an awarded contract. R&D or skilling support should likewise be checked against the final applicant rules.
Landowners and park developers
The park model can aggregate land and common infrastructure, but it also creates coordination risk. A land parcel is valuable to an operator only when utility capacity and delivery timing are credible. Park developers should publish clear status—identified land, acquired land, permitted land, serviced land, or operational site—rather than use a single generic “available” label.
A due-diligence checklist for projects and suppliers
Use this checklist before counting a policy benefit in a bid, investment case or site-comparison model:
- Get the controlling document. Record the policy notification number, approval date, version, amendments and current application guidelines. Save the source PDF or official circular.
- Confirm the applicant. Identify the legal entity that owns the facility, operates it, provides cloud services, or pays eligible costs. Check registration and local-office requirements.
- Map the project boundary. State whether the application covers one building, an expansion, a campus, a park or a cable facility. Avoid claiming the same cost or capacity under multiple schemes.
- Build a benefit schedule. For each incentive, record eligible expenditure or metric, rate, cap, duration, start date, payment date, evidence and responsible agency.
- Specify measurement. Agree meter locations, data frequency, PUE/WUE boundary, renewable-energy certificates or contracts, water categories, audit method and correction process before construction.
- Validate resource supply. Obtain written power and water availability, connection/upgrade scope, delivery milestones, tariff and source. Treat a public resource map as screening information until the utility confirms a project connection.
- Validate the site. Confirm title or lease, zoning, permits, environmental conditions, drainage, flood risk and local water conditions. A policy park announcement does not settle these.
- Check fibre and redundancy. Obtain route maps or carrier attestations for physically diverse circuits. Count ducts and rights of way, not just the number of logos on a connectivity brochure.
- Model downside cases. Test a delayed incentive, lower utilisation, power-upgrade slippage, water limits, changed cooling design and a lower ramp of customer demand.
- Keep claims traceable. Store source, page, date checked, calculation and owner for every policy statement in a project tracker.
What the policy does not prove
The policy’s importance is real, but it should not be over-read. It does not prove that Karnataka has already reached 1 GW of operational IT load. It does not confirm that every planned data park is financed, powered or under construction. It does not make every data-centre project eligible for every incentive. It does not establish that the maximum benefit will be paid, nor that the project’s electricity is carbon-free or its water source locally sustainable.
The public reporting also does not provide a complete, independent baseline for all existing facilities. The Hindu describes gaps in water-consumption data and notes that measured facility ratios can hide local impacts. That matters because project risk is local: water conditions can vary by neighbourhood and season; a grid connection can depend on a specific substation; and fibre resilience depends on the actual routes into the building.
Finally, the reported ₹1,300.45 crore framework should not be added to private investment commitments or data-centre capex. These are different categories. A disciplined investment map separates policy support, developer capital, tenant commitments, lender financing and operational assets. The policy can reduce friction or change project economics; it does not make execution automatic.
Frequently asked questions
What is Karnataka’s data-centre capacity target for 2031?
The policy is reported to target 1 GW of cumulative data-centre IT load by 2031. Treat this as a policy objective, not as current operating capacity or an unconditional construction commitment.
How much is the policy framework worth?
News reports describe a revised five-year budgetary framework of ₹1,300.45 crore. That is a policy-level programme framework, not an automatic grant to every developer and not a disclosed construction-cost estimate.
Is the ₹20 crore PUE incentive available immediately?
The Hindu and The News Minute report a one-time incentive for facilities within the stated PUE range after three consecutive years of demonstrated performance, with payment described in the fourth year. Applicants should confirm the measurement method, exact eligibility and application process in the current official guidelines.
Are the planned Karnataka data-centre parks already operational?
The reporting cited here describes proposed parks or zones and shared-infrastructure plans. A proposed park is not the same as an operational data centre. Verify land, approvals, power, water, fibre and construction status for each named site.
Does the policy guarantee Mangaluru a cable landing station?
No. Mangaluru is described as a strategic location with potential for cable-landing infrastructure. Potential and policy support do not establish that a station or international cable is built, commissioned or commercially available.
When should an investor include an incentive in a financial model?
Only after confirming the governing policy and guidelines, eligible entity, qualifying costs or performance metric, required evidence, cap and payment timing. Until then, show it as a conditional scenario rather than contracted revenue or assured subsidy.
Related Gridvik research
- India’s data-centre power bottleneck: grid readiness and state policy
- India data-centre investment map: commitments, finance and policy
- India’s market expansion: capacity, cities and AI infrastructure
- Why fibre is shaping India’s data-centre site choices
Sources and research note
This article was researched and checked on 10 October 2026. We did not locate a publicly accessible signed policy PDF or final operational-guidelines document on an official Karnataka government page during this review. The Cabinet decision and headline targets are supported by reporting on the government announcement; the incentive details below are attributed to news outlets reporting that they reviewed the policy text. Confirm the current government notification and guidance before relying on any term for an application, transaction or investment decision.
- The Hindu — Karnataka Cabinet approves Sustainable Data Centre Policy, 18 September 2026
- The Hindu — Karnataka’s drive to green data centres, 2 October 2026; reports it reviewed the policy text
- The News Minute — policy incentives, proposed parks and implementation interface, 30 September 2026
- Moneycontrol — Cabinet approval, 1 GW target and ₹1,300.45 crore framework, 18 September 2026
- The Hindu — earlier 1,000 MW park plan across Bengaluru, Mysuru and Mangaluru, 2026
Gridvik is an independent research firm. This article is informational and is not investment, legal, tax, engineering, energy-market or environmental advice. Policies and incentive conditions can change. Figures and project plans are attributed to their sources; verify material claims with the relevant government agency and project counterparties.