India’s AI stack, built together.

AICFI is being formed to flesh out India’s AI stack, from the energy beneath the silicon to the agents above it. It brings together the companies and institutions that will build it, and keeps the commons they share: the open specifications, tests and resources no single company would build alone.

The stack, layer 7 at the top to layer −2 at the base, with the foundation models it serves beside layers 6 to 2 7Agents and users 6Model router 5Inference gateway 4Orchestration 3Engine-side routers 2Inference engine 1GPUs and facilities 0Power orchestration −1Grid interface −2Energy supply FOUNDATIONMODELS
01The stack

Between a chip and a working AI product sit seven layers. Three more sit beneath the silicon.

A GPU on its own does nothing useful. Software runs the model, decides which machine runs it, and decides which model to use at all; applications sit on top. Beneath the plant, power is orchestrated, traded with the grid and bought. Each layer is a real business, with its own customers, and companies exist that do nothing but one of them.

India is building the silicon. Most of the stack around it is open.

  1. The software is free

    The layers that run and coordinate models are open source. What is scarce is people who can operate them well, and that is a hiring and training problem.

  2. The standards are unfinished

    The interface every layer will have to meet is being written now, in the open. A standard being written is one you can shape.

  3. Nobody has solved the hardest layers

    The Western stack was assembled for one model, one tenant and chat-shaped traffic. The parts that matter most for agents were built last, or not at all.

  • 38,231GPUs onboarded to the IndiaAI compute portal
  • 93 lakhsubsidised GPU-hours sanctioned across 237 projects
  • 26.3 GWof new power demand from AI datacentres projected by 2031–32

Government figures: MeitY in Parliament, March and August 2026; Ministry of Power, July 2026.

02Above the silicon
Layers 7 to 2, and foundation models

The software that turns capacity into answers.

Three of these layers are open source and can be adopted here today. The two that route work, the gateway and the model router, decide where work lands and what it is worth, and they have almost no Indian participant. Beside them sit the foundation models the stack serves.

7

Agents and users

The applications and agents that do the work. The only layer that knows what a request is for.

Built withAgent frameworks, harnesses, applications

In India
Apps strong, infra thinIndian application work is strong. The infrastructure under it is not.
What is open
Agent identity: on whose authority an agent acts. There is no settled standard anywhere.
6

Model router

Picks a model and a provider for each request, and so reads every request in the clear.

Built withOpen routers such as vLLM Semantic Router; commercial routing platforms

In India
OpenOne India-focused router has appeared. It is thin and commercially young.
What is open
Today’s routers route on price because they see nothing below them. One built now can be hardware-aware and private by design.
5

Inference gateway

Model-aware load balancing, priority and fairness. It is hardening into the formal boundary between applications and engines.

Built withKubernetes Gateway API Inference Extension, Envoy AI Gateway, llm-d

In India
OpenDeployable here, specified elsewhere. No Indian participant found.
What is open
The specification is being written now, in open working groups anyone can join. Taking part shapes it; arriving later inherits it.
4

Orchestration

Spreads one model’s serving across many machines: splits prompt processing from generation, tiers the cache, and places work where its cache already is.

Built withNVIDIA Dynamo, given away free

In India
AdoptableAdoptable today, thinly staffed.
What is open
Young everywhere. A build starting today starts disaggregated. The scarce input is people who can run it.
3

Engine-side routers

Choose a replica within one fleet.

Built withvLLM production-stack router, sgl-router

In India
AdoptableAdoptable today.
What is open
What a fleet reports upward, such as cache hit rate and queue depth, has no shared format.
2

Inference engine

Runs the model on each replica: continuous batching, paged attention, prefix caching.

Built withvLLM, SGLang, TensorRT-LLM

In India
AdoptableAdopt it; do not rebuild it.
What is open
Mature. The work is operating it well, and serving Indian languages efficiently.
M

Foundation models

What the stack serves. A model is run at layer 2 and chosen at layer 6, and depends on data, language resources and tokenizers, and on evaluation that tells a buyer what it can do.

Built byIndian foundation-model labs, publicly funded and private; open-weight models from abroad

In India
Being builtIndian foundation models are being trained with public and private funding. On one large routing platform, two-thirds of paid usage runs on open-weight models.
What is open
Evaluation that outsiders believe, especially in Indian languages. Indian languages cost on average about eight times as many tokens as English.
AICFI’s support
Open evaluation in Indian languages, maintained data and language resources, tokenizer efficiency, compute access, and deployment practice for the organisations building models.
03The silicon
Layers 1b and 1

The plant, and the layer that makes it a cloud.

This is the hardest layer to build and the one India is building. Tenancy, sitting just above it, decides whether that capacity is sold as machines or as a service.

1b

Tenancy

Turns a fleet of GPUs into a cloud: provisioning machines, an isolated cluster per tenant, sandboxing between workloads, metered billing.

Built withInfrastructure-tenancy platforms; hyperscalers’ in-house stacks

In India
PartialIndian GPU clouds sell self-serve instances. Isolation per tenant at hyperscaler standard has not been checked.
What is open
This layer decides whether an operator sells machines or sells a cloud.
1

GPUs and facilities

The plant that produces tokens. It needs land, power, capital and time, which the software layers do not.

Built withDatacentre operators, colocation, the IndiaAI compute programme

In India
Being builtFunded, deployed and growing. 38,231 GPUs onboarded to the national compute portal.
What is open
Without the layers above it, capacity competes on hourly rate alone.
04Below the silicon
Layers 0 to −2

Power, the grid, and energy.

In the West, separate software businesses now sit beneath the plant. In India, this is where the binding constraint is. The numbering runs down from the plant so that layers 1 to 7 keep their names.

0

Power and thermal orchestration

Runs power, cooling and compute together inside a fixed power envelope.

Built withFacility-orchestration software, early-stage

In India
OpenNo Indian participant identified.
What is open
Power already paid for becomes capacity that can be sold, and capacity can be split into firm and flexible.
−1

Grid interface

The facility as a flexible load on the grid: shifting work in time, and between sites, when the grid is constrained.

Built withGrid-flexibility platforms

In India
OpenThe rules exist: CERC made demand response a paid reserve in 2022, and Maharashtra has required it since 2024. Use is at pilot scale, with no datacentre taking part found.
What is open
Power becomes a placement input. Where work lands is decided from below as well as from above.
−2

Energy supply

Where the power comes from and how it is bought: generation, long-term contracts, captive plants, storage.

Built withUtilities and independent power producers

In India
MappedActive, and the binding constraint. Firm, round-the-clock power now decides where datacentres go. AI datacentres are projected to add 26.3 GW of demand by 2031–32.
What is open
On the map because it sets the ceiling for every layer above. AICFI does not work on energy or take positions on power policy.
05Across every layer

Solved inside each layer. Unsolved between them.

Five concerns run through the whole stack. Each is handled within a layer and breaks at the boundary between two organisations, which makes each one open ground for a shared specification.

  1. Evaluation and observability

    Tracing and evaluation tools are converging on the OpenTelemetry conventions for generative AI. Evaluation in Indian languages and Indian conditions is still thin.

  2. Guardrails

    Each guardrail enforces policy inside one layer. Nothing carries a policy across layers.

  3. Agent identity and authority

    Not just which request, but on whose authority. There is no settled standard anywhere.

  4. Metering and cost

    The telemetry exists at the bottom of the stack. No shared contract carries GPU time, batch position or real cache reuse back up across an organisational boundary.

  5. Accelerator observability and isolation

    Telemetry and security at the level of the GPU itself. It matters to anyone selling shared GPUs: tenants on the same silicon have been shown to learn what a neighbour is serving.

06What AICFI does

Four functions, all of them open.

Alongside them, AICFI improves access to computing and data, maintains the shared software, data and language resources the stack depends on, and supports the organisations building India’s foundation models.

  1. Standards and protocols

    Open specifications for how the parts of the stack connect, written with the companies that will implement them, and tests anyone can run to show an implementation conforms.

  2. Evaluation and certification

    Benchmarks and evaluation methods for AI systems, models and agents included, in Indian languages and Indian conditions. Certification against criteria published in advance, decided by an independent board and open to members and non-members on the same terms.

  3. The Lab

    AICFI’s own researchers and engineers, on the shared problems no single company will staff: evaluation suites, Indic datasets, tokenizer efficiency and deployment practice. What they build is published openly.

  4. Policy

    Research and assessment of AI policy and public programmes, resting on published evidence, and advice to government when asked. It does not represent members’ commercial interests.

07Who builds it

A community of builders.

AICFI maps the stack, brings the builders together, specifies what sits between them, and measures and certifies what they build. Members and others build the products.

  1. Charter members

    Companies and academic institutions that join at incorporation and shape the work from the start.

  2. Members

    Operators, vendors, model labs, applied AI companies, services firms, start-ups and research institutions, joining as the work grows.

  3. Researchers and academics

    Academic institutions join at nil or nominal dues. Researchers sit on the Technical Council and the Research Advisory Board, and work with AICFI’s Lab as staff, fellows and visitors, free to publish what they find.

  4. Contributors

    Individuals take part in working groups in a personal capacity, with no dues. The tests and outputs are open to everyone.

  5. Government Advisory Council

    People with experience in government and public policy advise AICFI as individuals. Government bodies are not members.

08Join

Charter membership is forming.

Companies and academic institutions interested in joining AICFI as charter members are welcome to get in touch.