The Economics of Air-Gapped vs Connected

Air-gap is a network fact: no general route from the runtime to the public internet, and a controlled, logged path for anything that enters. It is not a personality. It is not sovereignty by itself. It is expensive in the ways that do not show up on a GPU invoice — people who bag updates, a second environment that cannot just pip install, evals you cannot send to a crowd, and hardware that cannot burst to IndiaAI on a bad afternoon.

This study prices the premium as a method. We will not give you a single air-gap costs 2.7× multiplier. Multipliers like that are how connected vendors sell fear and how air-gap vendors sell romance. Your premium is a stack: ops headcount (see the companion piece), media and registry process, slower CVE response, duplicate tooling, and the option value you give up.

If the data class does not need a gap, do not buy one to look serious. If it does, do not pretend a connected private region is the same control at a discount.

Three postures, three bills

Connected on-prem: the rack is yours, outbound exists, you can pull a patch, you can burst. Cheaper ops, weaker story if someone asks who can reach the model. Managed private / empanelled cloud: you rent a tenant. Ops are cheaper still. Control plane is not yours. Fine for many departmental workloads. Not a gap.

Air-gap: inbound is a bag, outbound is a deny, break-glass is a ceremony. Ops are a team. This is the posture for data classes and threat models that cannot tolerate the other two. It is not the default for a tourism FAQ.

Where the premium actually sits. Magnitudes are directional.

Cost line	Connected on-prem	Air-gap increment
GPU silicon	Sized to concurrency	Often similar; sometimes +1 for a dark eval twin
Ops people	A slice of SDC / NIC	Named bag, admit, and rebuild roles — the large increment
Patch / model update	A pull and a window	A courier or sneaker-net calendar; slower CVE clock
Eval	Can use extra tools, even hours elsewhere	Must be inside; gold set labour rises
Burst option	IndiaAI / reserved cloud	Usually none; you own the peak
Support	Vendor can see a replica	Vendor sees what you bag out; AMC should price that

A worked premium, labelled as illustration

Take a one-workflow inference node that, connected on-prem, costs you on the order of a crore in first-year cash (hardware + modest SI + gold set + power). The air-gap increment is rarely another full node. It is often: a second smaller eval host or a time-sliced dark twin; 0.5–2 extra skilled people or a dedicated SI ops retainer; a media/registry regime; a slower change calendar that eats officer time. That increment can sit in the tens of lakhs to low crores depending on whether you already have a high-side hall.

If you do not already have an air-gapped hall, the first gap is a facility project — cages, diodes or bag procedures, identity, logging — and the increment jumps a class. Do not hide a hall inside an agent quote. Compare that increment to the loss you are buying down: a class of data that must not ride a connected control plane, a threat model that includes the vendor's admin path, a statutory or cabinet-level isolation instruction. If you cannot name the loss, the increment is a hobby.

False economies on both sides

False economy of connected: skipping the gap on a data class that later appears in a newspaper. The retrospective premium is infinite in political terms and large in inquiry terms. False economy of air-gap: gapping a helpdesk that uses public circulars, then discovering you cannot update the circular corpus without a three-week bag. You will either break the gap or freeze the corpus. Both are expensive.

False economy of almost air-gap: a rack with a hidden outbound for licences and crash reports. You pay the ops of a gap and keep the risk of a connection. Pay for one posture. Prcept will run in a true gap. We will also tell you when a connected on-prem tenant is the grown-up choice. The premium is real. It should be earned.

Split the workflows or pay twice

The expensive mistake is one posture for the whole department. Personnel files, disciplinary drafts and OT-adjacent logs may earn a gap. Public GRs, tourism FAQs and already-published circulars rarely do. Split them. Two small bills beat one large religion.

If you cannot staff two postures, gap only what must be gapped and leave the rest un-automated. An un-automated public FAQ is cheaper than a frozen corpus that officers bypass on their phones.

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.

Air-gap is required for all government AI

No statute we will cite says that. Some data classes and some threat models require it. A blanket gap is a budget decision pretending to be law.

Connected on-prem is basically the same

It is the same silicon. It is not the same admin path. If the admin path is the risk, the premium is the point.

We will save money by gapping and using old cards forever

Old cards are fine if the eval still holds. A gap does not exempt you from CVEs. Budget the bag.

Give us the multiplier

We will build your stack. We will not tattoo 2.7× on a slide.

A three-week premium file

1. Week 1: classify data and threat. Write one sentence on why a gap is required or not.
2. Week 2: if required, list what you already have (hall, bag, identity). Price only the increment.
3. Week 3: compare increment to a connected on-prem and to an IndiaAI burst for the parts that can leave. Split workflows if the FAQ does not need the gap the personnel file needs.

How this shows up in the file

Subject: Air-gap premium for [workflow].

Requirement: [required / not] because [data class, threat, instruction]. Baseline connected on-prem cash: [Ledger A]. Air-gap increment: people, twin, bag, lost burst — [table]. Workflows split: [list]. Almost-air-gap with hidden outbound is rejected.

This study is not a security accreditation and not legal advice. The premium is people and process, not a mystical GPU multiplier.

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 “air gapped cost premium” needs a number a CFO can defend, not a GPU brand. “The Economics of Air-Gapped vs Connected” belongs in a cost model with people, power, idle time, AMC and the cost of a failed pilot.

The air-gap premium is mostly people and process, not extra GPUs. Count bagging, a second environment, idle, and the eval you can no longer crowdsource. 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 “The Economics of Air-Gapped vs Connected” 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. “air gapped cost premium” 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 “The Economics of Air-Gapped vs Connected” is only a heading, it will not survive a file inspection. A P1 CIO/CTO should be able to attach one artefact that proves “air gapped cost premium”: 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 “air gapped cost premium” 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.