Capex vs Opex Framing for Government AI

Procurement had a capital ceiling and an easy professional-services head. The vendor offered a three-year 'managed AI' invoice that looked like opex. The GPUs would sit in a Mumbai hall the department would never enter. The CISO asked where the traces lived. Finance asked whether a three-year lock was really revenue expenditure. The file had used capex-versus-opex as a slogan to avoid both questions.

This explainer is for procurement officers who are being bounced between a capital freeze and a cloud subscription. GFR, your State rules, and the Government Accounting Rules still decide what may be charged where. We will not restate those books. We will show you how AI projects abuse the words, and how to stop.

Accounting is not architecture. A card in your SDC can be leased (opex-like) and still be on-prem (architecture). A cloud hour can be prepaid (looks capital-ish in a naive note) and still be a transfer (architecture). Write both axes.

Not accounting advice. Your PAO and CGA mappings win. Hedge.

Two axes, four rooms

Axis one: who holds the pen on the machine and the traces — you, a programme cloud, a hyperscaler, a vendor hall. That is architecture and data class.

Axis two: how the treasury pays — capital plant, revenue subscription, professional services, grant. That is finance.

Four rooms appear. On-prem capital. On-prem lease or managed rack charged as revenue. Empanelled cloud hours as revenue. Vendor-managed everything bundled as a service. Each room has a GFR and a CISO conversation. Do not let the cheaper conversation cancel the harder one.

Say the room out loud. Committees mix them.

Room	Architecture	Typical pay frame	Usual hidden risk
Buy and hold	Your SDC / air-gap	Capital + AMC revenue	No operate money
Lease / managed on-prem	Your hall, someone else's asset	Revenue / service	Exit and lien on the boxes
IndiaAI / empanelled hours	Their cloud, your eligibility	Revenue; subsidy if any	Data class + RFE movement
Vendor SaaS agent	Their app, their traces	Revenue, looks easy	You bought a conversation, not a packet

What GFR-shaped questions actually look like

Is this a new service or an existing one? Are we splitting a job to stay under a delegation? Is a three-year prepaid cloud a multi-year commitment that needs a higher sanction? Is a 'free' GPU with a locked AMC a designed vendor lock? These are old questions. AI does not mint new answers. It mints new invoices that try to look like stationery.

Managed services can be legitimate. They become illegitimate when the SoW hides that you cannot export the packet, or when the rate assumes a subsidy you do not have. Put the architecture sentences in the SoW so finance is not buying a mystery.

Opex is not a synonym for agile, and capex is not a synonym for sovereign

Opex can be a five-year SaaS that you cannot leave. Capex can be a card you own and cannot staff. Sovereignty lives in traces, tools, and who can be compelled. Payment cadence is a different file.

A capital freeze is a real constraint. The adult response is to lease a rack you still control, or to shrink year-one scope, not to pour production cases into the first opex-shaped funnel that answers the phone.

IndiaAI hours are usually framed as a revenue spend plus a subsidy accounting story that the programme defines. They are not 'free capex'. They are not an exemption from delegation. Read the sanction that lets you apply.

Write both sentences in the note

Sentence one: we will pay for this as [capital / revenue / mixed], under heads [x], for [n] years, with [sanction level]. Sentence two: the machines and traces will live at [place], under [who], with [export]. If either sentence is missing, the note is a slogan.

Two framings

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.

If it is a service, we do not need an architecture note.

You especially need one. Services hide machines. The note is how you remember they exist.

Lease versus buy is just NPV.

NPV is the finance layer. Lien, exit, and who holds traces are the other layer. Run both.

GFR does not mention GPUs.

GFR mentions procurement, sanctions and expenditure. GPUs are plant or a service depending on the contract. Apply the book you have.

The vendor said this is opex-friendly worldwide.

Worldwide is not your PAO. Ask your PAO.

Ten days to a two-sentence note

Sit finance and CISO on the same draft. If they will not share a page, you do not have a project.

1. Day 1–2: pick the room from the four. Do not pick two and pretend it is one.
2. Day 3–5: finance writes the pay sentence with heads and sanction level.
3. Day 6–8: CISO / DPO writes the place-and-traces sentence.
4. Day 9–10: glue them. If they fight, change the room, do not blur the sentences.

File note you can paste

Subject: Capex / opex frame and architecture frame for [project].

Payment will be treated as [ ] under heads [ ] as advised by finance on [date]. Architecture: machines and traces at [ ], export test [ ]. These sentences are independent. A change to one does not silently change the other. This is not accounting advice.

What we will put on which axis

Prcept AI can be bought as plant on your rack or as a managed pair in your cage. We will not relabel a hosted conversation as on-prem because the invoice is monthly. We will not relabel a card purchase as a service to dodge a ceiling without finance in the room.

Use us on both axes, or use someone else. Do not use us to blur them.

This article is informational field guidance for Indian public institutions, not legal, language-policy, procurement, finance or engineering advice. Confirm against the live Gazette, Official Languages Act and Rules, your State's official-language law, MeitY / IndiaAI notices, GFR, GeM terms, DPDP text, departmental manuals and your counsel before you file it.

How to put this in the finance note

A P2 Procurement searching “capex opex government IT” needs a number a CFO can defend, not a GPU brand. “Capex vs Opex Framing for Government AI” belongs in a cost model with people, power, idle time, AMC and the cost of a failed pilot.

A secretary who says 'we have no capex, so we will take cloud' has made an accounting remark, not an architecture decision. Frame both. Then let finance and the CISO each hold their pen. 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 “Capex vs Opex Framing for Government AI” 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 P2 Procurement, not “the vendor.”

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

What must be true before you file this

If “Capex vs Opex Framing for Government AI” is only a heading, it will not survive a file inspection. A P2 Procurement should be able to attach one artefact that proves “capex opex government IT”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “capex opex government IT” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.

What the next file must contain

“Capex vs Opex Framing for Government AI” earns a line in the noting only if a P2 Procurement can attach proof of “capex opex government IT.” 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 “capex opex government IT.”
• 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.