Financing Options for State AI Infrastructure

The question how do we finance a state GPU hall is usually a question about courage dressed as a question about instruments. Most states can already buy a small inference node on an IT head they have used for ten years. What they cannot do is invent a para-fiscal scheme, a vendor-financed cluster that is a loan in all but name, or a central subsidy they have not been granted, and still expect the Advocate General to smile.

This guide walks the instruments that actually exist: voted budget, centrally sponsored or central sector schemes where the purpose fits, IndiaAI hours as a substitute for owned silicon, NICSI / GeM routes, external assistance when a live project already has a component, and — carefully — opex models that GFR now recognises as a category of purchase. It will not invent a state AI bond as if one were waiting in the Gazette.

It is not financial advice. Finance departments write the rules you will actually use. Bring them this map, not a fintech slide.

Start from the head, not from the GPU

Name the demand, the major head, and the object head you will debit. If the work is a citizen service already funded, the honest path is often an additionality on that scheme, not a new AI mission line that will fight for existence in the next budget. New lines are speeches. Old lines that already survive PAC are financing.

GFR's capital-versus-revenue test decides whether a purchase of nodes is capital and a purchase of hours is revenue. That test is about the nature of the asset, not about what you wish the politics of the announcement to be. A three-year prepaid cloud that creates no asset is still usually revenue, and it will hit the same ceiling conversation as any other recurring IT. DFPR competence decides who can approve which size of what. An AI emergency does not create a new competent authority. Write the serial.

Instruments that exist, with their real constraints

Voted state budget. Slow, legitimate, renewable if year two is honest. Still the default for standing inference you will own. Central schemes. Only when the scheme guidelines can bear an AI component without violence to purpose. Do not hide a GPU farm under a training head because the training head has money. Audit has seen this movie.

IndiaAI compute. Hours, not a hall. Financing by not buying silicon. Eligibility and subsidy are not automatic for every state directorate. NICSI / GeM / empanelled SI. These are procurement doors, not sources of funds. They change how you buy, not whether the money exists.

External assistance (World Bank, ADB, and similar) when a live project already has an ICT component and a procurement framework. Opening a new loan to buy four GPUs is theatre. Adding a well-specified component to a project that is already open can be sane. Opex / managed-service models recognised conceptually in GFR's vocabulary: the seller keeps the asset, you pay a periodic charge. These can be honest. They can also be a loan with a service wrapper. Read residual value, lock-in, and whether you are paying for capacity you cannot turn off.

Match the instrument to the thing you are actually acquiring.

Need	Instrument to try first	Do not
Standing on-prem inference	Voted IT / scheme capex, small node	A 10-year vendor finance against a demo
A dated training burst	IndiaAI or reserved hours on revenue	A capital cluster for a two-week job
A multi-department pool	SDC capex with showback, or a finance-secretary allocation	Informal contributions without a head
A campus lab	University capital + a grant route (next article)	A state loan to the campus for one server

What is not an instrument, however fashionable

A vendor who will put the cluster and you pay from savings is proposing a shared fantasy about savings and, often, a borrowing you are not authorised to take. If it is a PPP, it needs a PPP process. If it is a purchase, it needs a purchase process. If it is a loan, it needs the finance department and, often, the legislature.

CSR from a hyperscaler is not a financing plan. It is a gift with a press note and a termination clause. Treat gifts as gifts: nice, temporary, not a basis for a citizen-facing duty. Token credits and startup coupons expire. Do not put them in Ledger A as if they were a voted grant.

Opex is not a window around a ceiling

When capex is frozen, vendors offer opex as if GFR had opened a skylight. Opex still hits a head. It still needs competence. It still recurs in year two. Sometimes it is the right instrument — hours, a managed service you can turn off. Sometimes it is a loan that was not taken to the legislature. The test is residual value, lock-in, and whether you can stop paying when the duty stops.

If you cannot stop paying, you have bought an asset with extra steps. Take it to finance as an asset, or do not take it.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Other states are using innovative finance

Ask for the instrument's legal name and the cabinet note. Innovation that cannot be named is usually a vendor term sheet.

Capex is frozen, so we must opex

Opex still needs a head and a ceiling. It is not a magic window. Sometimes a smaller capex is the honest path.

The centre will pay; it is a mission

Missions pay for what their guidelines name, to whom they name. Read the guideline. Do not spend first.

We can mortgage future AMC to get more GPUs now

That is a loan-shaped story. Take it to finance as a loan-shaped story, or do not take it.

A three-week financing map

1. Week 1: write the thing you are buying in one sentence (hours, a small node, a hall, a service). List heads that already pay for similar ICT.
2. Week 2: test IndiaAI eligibility, any live central scheme guideline, and any open externally aided ICT component. Discard mismatches in writing.
3. Week 3: sit with finance on capex versus opex and DFPR. Pick the dull instrument. Kill the vendor-financed hall unless finance wants it as a named PPP or loan.

How this shows up in the file

Subject: Financing path for [AI infrastructure].

Acquisition: [hours / node / pool / managed service]. Proposed head: [demand, major, object]. Capital or revenue: [GFR test applied]. Other instruments considered and rejected: [list, with reason]. DFPR competence: [serial]. Year-two cash path: [head]. No unnamed savings-linked repayment is proposed.

This guide is not legal or financial advice. A vendor-financed rack is not a PPP until a PPP process says it is.

This article is informational field guidance for Indian public institutions, not legal, procurement, tax, accounting, tariff or engineering advice. Confirm against the current Gazette, GFR, GeM term, SERC tariff order, IndiaAI portal rule, CAG mandate, DPDP text, departmental finance manual and your counsel before you file it. Figures are methods and order-of-magnitude illustrations, not a dataset of real deployments and not a substitute for a live quote.

How to put this in the finance note

A P1 CIO/CTO searching “financing government IT infrastructure” needs a number a CFO can defend, not a GPU brand. “Financing Options for State AI Infrastructure” belongs in a cost model with people, power, idle time, AMC and the cost of a failed pilot.

States do not need a special AI bond. They need a legal head, a capex-or-opex decision, and an instrument that GFR and the legislature can recognise. IndiaAI subsidy, if you use it, is a live notice — not a permanent discount. On-prem TCO includes ops headcount. Do not invent Rs/hour. Cite the source of every rupee.

• Separate capex, opex, and one-time cleanup.
• Show utilisation, not just peak GPUs.
• Price the human fallback, not only inference.
• Date every tariff and subsidy assumption.

Close this loop before the next CAB

Put “Financing Options for State AI Infrastructure” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P1 CIO/CTO, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “financing government IT infrastructure” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What the next file must contain

“Financing Options for State AI Infrastructure” earns a line in the noting only if a P1 CIO/CTO can attach proof of “financing government IT infrastructure.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “financing government IT infrastructure.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.