Connectivity as public infrastructure
Cities increasingly treat connectivity the way they treat roads, water and power — as public infrastructure that underpins everything else. Public Wi-Fi in transit hubs, markets, parks, civic buildings and along streets gives residents and visitors access to information, government services, payments and education, and it does so most powerfully for the people least likely to have reliable connectivity at home. India’s PM-WANI framework was created to make this kind of public Wi-Fi practical at scale.
But delivering Wi-Fi across a city is a serious engineering and operational undertaking, very different from covering a single building. This guide looks at how cities and large public operators design, deliver and sustain public Wi-Fi — the architecture, the economics, the inclusion goals and the network design that makes a municipal-scale deployment actually work.
The PM-WANI framework in brief
PM-WANI deliberately lowers the barrier to offering public Wi-Fi by splitting the job into roles. Public Data Offices (PDOs) run the actual hotspots — a shop, a kiosk, a municipal site. PDO Aggregators (PDOAs) handle authentication, billing and the management behind a group of PDOs. App providers give users a single app to discover and connect to hotspots. This unbundling means a city does not need a telecom licence to enable widespread public Wi-Fi; it orchestrates these roles instead.
For a municipal programme, this is powerful: the city or its partner can act as or appoint aggregators, enable many PDOs across public and private sites, and present citizens with a consistent way to connect. Our guides on building a PM-WANI business and becoming a PM-WANI PDO cover the roles in depth; here the focus is doing it at city scale.
- PDOs — run the actual hotspots (a shop, kiosk or civic site)
- PDOAs — handle authentication, billing and management
- App providers — give users one app to discover and connect
- No telecom licence needed — the city orchestrates the roles
Designing the access layer for the outdoors
City Wi-Fi lives largely outdoors, and the access layer must be built for it. Outdoor-rated access points mounted on poles, building façades, transit shelters and public structures provide coverage across streets, plazas and platforms. They must withstand weather and heat, handle dense crowds at markets and stations, and cover open distances where there are no walls to contain or reflect signal — a different design discipline from indoor coverage.
High-traffic public spaces — a busy transit interchange, a festival ground, a popular market — are effectively high-density venues and need capacity planning to match. Immunity’s Lotus Alpha range includes hardened outdoor models built for exactly these public deployments, from a single plaza to a city-wide footprint.
Backhaul: getting traffic out of the streets
Every outdoor access point needs a path back to the core, and across a city that backhaul is a major part of the design. Where fibre exists it is ideal; where it does not, point-to-point and point-to-multipoint wireless links carry traffic from clusters of access points to aggregation points connected to fibre. Planning backhaul is often the hardest part of a city deployment, because it must follow the realities of existing ducts, rights of way and line-of-sight.
A pragmatic city design mixes media: fibre on the routes where it is available, wireless backhaul to reach the rest, and aggregation points that consolidate traffic before it hits the core. Getting this layer right determines whether the network is reliable and scalable or a patchwork of congested links.
Central control across thousands of nodes
A city network can involve thousands of access points across hundreds of sites, and managing that by hand is impossible. Cloud-managed control is essential: zero-touch provisioning so each new hotspot configures itself on power-up, central policy so every node enforces the same rules, and fleet-wide telemetry so operators can see the health of the whole city from one console. This is the only realistic way to run public Wi-Fi at municipal scale.
The choice of control model — explored in our piece on cloud versus on-prem controllers — is effectively decided for a city deployment: the distribution and scale demand a cloud control plane. Immunity’s Net Cloud is built for exactly this, managing large fleets of outdoor access points as one system.
The services layer: portal, identity and billing
On top of the network sits the services that users actually touch. A captive portal welcomes users, captures consent and handles authentication; within PM-WANI, the aggregator and app provider roles supply identity and access. Billing supports whatever model the city chooses — free basic access, paid premium tiers, time or data limits — and the whole thing must meet India’s public Wi-Fi log and compliance expectations.
This layer is where citizen experience and operator sustainability meet. A clean, fast onboarding encourages use and inclusion; a flexible billing and sponsorship model helps the network pay its way. Designing the services layer thoughtfully is as important as the radios on the poles.
Making the economics work
The hardest question for public Wi-Fi is how it sustains itself. Pure free access delivers maximum inclusion but no revenue; pure paid access funds the network but limits its civic value. Most successful deployments blend the two: a free basic tier for inclusion, paid premium tiers for heavier users, plus advertising or sponsorship on the portal and the broader economic value the city captures from a connected population.
PM-WANI’s low barrier helps the maths by enabling many small PDOs — shops and kiosks that host hotspots — to participate, spreading both coverage and cost. A city programme that thinks carefully about the revenue mix from the start is far more likely to be sustained beyond an initial grant than one that treats funding as an afterthought.
- A free basic tier for digital inclusion
- Paid premium tiers for heavier users
- Advertising or sponsorship on the portal
- Many small PDOs spreading both coverage and cost
Digital inclusion as the real return
Beyond direct revenue, the central return on public Wi-Fi is digital inclusion. For residents without home broadband, free or affordable public connectivity is a gateway to online education, government services, digital payments, job searches and information. A well-placed network in markets, transit hubs and civic spaces reaches exactly the people the digital divide leaves behind, which is why public Wi-Fi is a recurring pillar of smart-city and digital-India ambitions.
Measured this way, the value of a city network is not only the access fees it collects but the economic and social participation it enables. That broader return is what justifies public investment and partnership, and it is worth making explicit in any municipal business case.
Phasing a city rollout
No city lights up everywhere at once. A sensible programme phases the rollout: begin with high-impact, high-footfall locations — a major transit hub, a central market, a cluster of civic buildings — prove the model technically and commercially, then expand outward in waves. Each phase validates coverage, backhaul, the services layer and the economics before committing to the next, and early wins build the public and political support a larger programme needs.
Phasing also lets the design improve as it scales. Lessons from the first transit hub shape the template applied to the next twenty sites, and zero-touch provisioning means each new wave comes online with the refined configuration automatically. A city network grown this way is far more robust than one attempted in a single big-bang deployment.
Operating a public network day to day
A city network is a living service that needs running, not just building. Thousands of outdoor nodes face weather, power events, vandalism and the constant churn of public use, and the operator must spot and fix problems quickly to keep public trust. This demands fleet-wide monitoring, clear ownership of faults, and the ability to dispatch maintenance efficiently across a wide geography.
Cloud-managed visibility is what makes this feasible: a single console showing the health of every hotspot, alerting on outages, and pinpointing which node in which location needs attention. Without that central operational view, a network of thousands of public access points becomes unmanageable; with it, a modest team can keep a whole city connected.
Partnerships and the PM-WANI ecosystem
City-scale public Wi-Fi is rarely the work of one party. PM-WANI’s design positively encourages an ecosystem: the municipality or a lead partner may act as aggregator, local shops and kiosks become PDOs hosting hotspots, app providers connect users, and an OEM supplies and supports the hardware. Spreading the roles spreads both the investment and the coverage, and lets small local businesses participate in — and benefit from — the public network.
For a city, orchestrating this ecosystem is often more practical than owning every element directly. The framework provides the structure; the city provides the coordination, anchor sites and public spaces; partners provide reach and services. Designing the programme around these partnerships from the outset makes it both more affordable and more deeply rooted in the community it serves.
Future-proofing the public network
Public infrastructure is built to last, and a city Wi-Fi network should be specified with the future in mind. Outdoor access points and backhaul should have headroom for rising demand as more people and devices come online; the management platform should scale to many more nodes than the initial phase; and the services layer should accommodate new access models and uses, from civic IoT sensors to emergency communications, that ride on the same network.
Choosing a platform and a Make-in-India OEM partner that can grow with the programme protects the public investment. Immunity’s Net Cloud and outdoor wireless are built to scale from a single hub to a city, so the first phase and the tenth share one platform — and the network the city builds today still serves it well as demand and ambition grow.
Delivering it with a Make-in-India stack
A city-scale deployment touches everything: hardened outdoor access points, mixed backhaul, a cloud-managed core, and a compliant services layer — supplied, supported and ideally manufactured close to home. A Make-in-India OEM brings local stock for large rollouts, in-country support for thousands of distributed nodes, and engineers who understand the PM-WANI framework and Indian public-Wi-Fi context first-hand.
Immunity provides that end-to-end stack — outdoor Wi-Fi, switching, gateways and the Net Cloud platform — for public deployments from a single transit hub to a city-wide programme, aligned with our government and public-sector solutions. If your city or organisation is planning public Wi-Fi, our team will help architect it for coverage, scale, compliance and sustainability.