Chandigarh 01 is one of two operating sites in Sify’s AI Edge programme, alongside Lucknow 01. It is published at up to 4.8 MW of modular IT capacity, with a 10-layer security model, a national long-distance fibre backbone and a design aimed at low-latency AI inferencing rather than hyperscale training. The important word is up to. 4.8 MW is the maximum of a modular product, not a measurement of what is energised — and the identical sentence is used for Lucknow. The registry counts 4.8 MW here and 4.8 MW there, so 9.6 MW of the national 2,420.37 MW comes from one product specification stated twice. It is the smallest and least verifiable figure in this folder, and it is also the one that tells you where Sify thinks its next decade of demand is.
1At a glance
24.8 MW is a product, not a measurement
| Field | Chandigarh 01 | Lucknow 01 |
|---|---|---|
| Record | PRJ-229 | PRJ-230 |
| Status | Live | Live |
| Capacity | up to 4.8 MW | up to 4.8 MW |
| Architecture | Modular | Modular |
| Security | 10 layers | 10 layers |
| Qualifier | Up to | Up to |
| Counted | 4.8 MW | 4.8 MW |
Two facilities in two states, opened months apart, published with identical capacity. That is not a coincidence and it is not an error: 4.8 MW is the modular unit Sify builds. The site is a pod count, and every site is quoted at the maximum pod count.
Which means the number tells you about the product, not the site. A facility with one pod installed and a facility with four pods installed both publish 4.8 MW. Nothing in the public record distinguishes them.
An up to figure is a ceiling on a modular product. It is useful for sizing the site and useless for sizing the load.
The registry counts 4.8 MW on both records because it is the only capacity either operator has published, and because understating a market that is already counted as a floor is the more dangerous error. Both records are flagged as ceilings here and in the source register.
When two identical site figures appear, the honest reading is that neither has been measured. The figure is a specification, and a specification repeated is still one specification.
3What an edge facility is actually for
The reason Sify is building 4.8 MW pods in Chandigarh and Lucknow rather than 130 MW campuses is latency and land. A training cluster wants cheap power and space; an inference service wants to be within a few milliseconds of its users, and users are in tier-two cities.
| Dimension | Hyperscale campus | Edge facility |
|---|---|---|
| Capacity | 100 MW and above | up to 4.8 MW |
| Workload | Training, large data platforms | Inference, caching, latency-sensitive services |
| Land | Dozens of acres | A floor or a small plot |
| Build time | 24 to 36 months | Months, in modular pods |
| Customer | Hyperscalers and GPU clouds | Enterprises, government, regional banks |
| Example here | Noida 02, Chennai 02, Rabale | Chandigarh 01, Lucknow 01 |
The 10-layer security and the carrier-neutral fibre backbone are the parts that make an edge site sellable to a bank or a government department. Those customers will not put core workloads in a hyperscale campus 300 km away, and they will not accept a colo cage in a commercial building either. A small, certified, carrier-neutral pod in their own city is the product they have been waiting for.
Chandigarh is a sensible first address for it. The city is the administrative capital of two states, has a large government and banking presence, and sits at the northern end of the national fibre map with no hyperscale campus of its own. The entire counted capacity of Chandigarh in this registry is this one 4.8 MW facility — which says as much about the gap in tier-two India as it does about Sify.
4Where the edge programme tops out
| Stage | Sites | MW at full 4.8 | % of 2,420.37 MW |
|---|---|---|---|
| Live today | 2 | 9.6 | 0.4% |
| Including those under construction | 4 | 19.2 | 0.8% |
| Stated plan, low end | 10 | 48.0 | 2.0% |
| Stated plan, high end | 12 | 57.6 | 2.4% |
The arithmetic is deflationary and it is the most useful thing on this page. Even a fully built twelve-site edge network adds 57.6 MW — 2.4% of the national counted capacity. Sify’s stated ambition to be in every state with edge data centres is real, but it is a distribution strategy, not a capacity strategy.
That matters for anyone valuing the company on megawatts. The edge programme will not move Sify’s capacity number. What it can move is revenue per megawatt, because an inference pod in Chandigarh sells at a very different rate to a wholesale hall in Navi Mumbai — and Sify has not published rents for either.
The comparison worth holding in mind: one Rabale tower is 43.3 MW, or 1.4 times the entire twelve-site edge plan. The edge network exists for coverage, latency and public-sector relationships. The campuses exist for the megawatt count.
5Procurement
6Limits and open questions
- 4.8 MW is an “up to” figure from a portfolio page. No installed capacity is published.
- The figure is identical to Lucknow 01, which means it describes a modular product rather than either site.
- No rack count, floor area, PUE or substation class is published for this facility.
- No opening date, tenant or investment figure is published for Chandigarh, unlike Lucknow which has a groundbreaking date.
- Chandigarh is a union territory; the registry records the state field as Chandigarh, UT and Punjab, and this record is the only one in it.
- Counting 4.8 MW is the operator’s ceiling. If actual installed capacity is a single 1.2 MW pod, the national total is overstated by 3.6 MW.
- What would close it. One sentence from Sify: energised IT load at Chandigarh 01 on a stated date.
7Sources
Sources: the Sify AI Edge data centre page with the up-to-4.8-MW modular specification, 10-layer security and the list of live and planned edge sites; the Sify data centre portfolio page; Sify Infinit Spaces portfolio page; the Sify manufacturing brochure of July 2026; and Blackridge Research on the Chandigarh edge facility.