PM-WANI (Prime Minister Wi-Fi Access Network Interface) is the Government of India framework that lets anyone — from a tea shop to a telecom operator — offer public Wi-Fi without a licence. For entrepreneurs and operators it is one of the most accessible connectivity businesses in the country. This guide breaks down how it works and what you need to run it well.
The four PM-WANI roles
The framework defines four participants. A Public Data Office (PDO) owns the hotspot — the local shop or venue that sells Wi-Fi. A Public Data Office Aggregator (PDOA) provides the platform, authorisation and accounting for many PDOs. An App Provider runs the consumer app that discovers hotspots and signs users in, and the Central Registry maintained by C-DoT ties it together.
The commercial point is simple: a PDOA can sign up hundreds or thousands of PDOs, each a revenue-sharing hotspot, with no telecom licence required. The technology has to handle onboarding, billing and compliance at that scale.
- PDO — runs the hotspot (shop, kiosk, civic site)
- PDOA — handles authentication, billing and management
- App provider — lets users discover and connect
- No telecom licence needed to participate
What you actually need to deploy
Three things make or break a PM-WANI rollout: certified hardware, a flexible captive portal, and compliant logging.
Certified access points. Your hotspots must be reliable in the field and meet Indian certification. Immunity offers India’s first PM-WANI certified access point in the Lotus Alpha range, built and supported in India.
A captive portal that converts. Users meet your splash page first. It needs app-based onboarding, vouchers or prepaid plans, and a clean branded experience. Our captive portal and Gateway Controller handle authentication, bandwidth tiers and billing.
Central IPDR logging. Public Wi-Fi in India carries a legal duty to retain Internet Protocol Detail Records. Net Cloud centralises tamper-evident IPDR with configurable retention so audits are straightforward.
Turning Wi-Fi into recurring revenue
The economics work when you can meter and monetise. Define free and paid tiers, sell time or data passes, and settle revenue across PDOs automatically. Done well, each hotspot becomes a small recurring-revenue node, and the PDOA platform is the business.
Where Immunity fits
We provide the full stack — certified APs, gateway, captive portal, billing and central IPDR — managed from a single console, with local Indian support. See how this runs in production in our public Wi-Fi case study, then talk to our team about your deployment.
The three PM-WANI roles in depth
PM-WANI works by splitting public Wi-Fi into clear roles so that almost anyone can participate. A Public Data Office (PDO) runs the actual hotspot — a shop, kiosk or civic site — and offers paid access. A PDO Aggregator (PDOA) sits behind a group of PDOs, handling authentication, billing and management. An app provider gives users a single app to discover and connect to hotspots anywhere in the country.
This unbundling is the framework’s genius: a small business can become a PDO without a telecom licence, leaning on a PDOA for the technical and compliance heavy lifting. Our step-by-step PDO guide walks the practical path.
Choosing between PDO and PDOA
The first strategic decision is which role to play. Becoming a PDO is the low-barrier entry: install a hotspot, partner with a PDOA, and earn from access. Becoming a PDOA is a bigger undertaking — you operate the platform that authenticates users, bills them and manages many PDOs — but it captures more of the value and lets you build a network of hotspots under your own brand.
Many successful operators start as PDOs to learn the model, then move up to PDOA once they understand demand and economics. Others partner: a local entrepreneur runs PDOs while an established player provides the aggregator platform.
The economics of a hotspot
A PM-WANI hotspot earns from access fees, typically small paid plans bought by users for an hour, a day or a data bundle. The economics turn on footfall, the price point, and how much of each rupee the PDO keeps after the PDOA’s share. A busy location — a transit hub, a market, a campus gate — can generate steady revenue; a quiet one will not.
The smartest operators blend models: a free basic tier to attract users and build habit, paid premium tiers for heavier use, and sometimes sponsorship or advertising on the portal. The low barrier to becoming a PDO means coverage and cost can be spread across many small participants.
Hardware and backhaul for a PDO
A PDO needs a PM-WANI-ready access point and a reliable backhaul connection to the internet. For a single shopfront that can be a quality indoor access point on a broadband line; for a larger or outdoor location it means weather-rated hardware and, where fibre is unavailable, a wireless backhaul link. The access point must support the captive-portal and authentication flow the PDOA platform expects.
Choosing hardware from a Make-in-India OEM helps a public-Wi-Fi operator with local stock for rollouts, in-country support for distributed sites, and engineers who understand the PM-WANI context first-hand.
Compliance and accountability
Because PM-WANI is public Wi-Fi, accountability is built into its design. Users are authenticated through the app and PDOA, sessions are logged, and the framework provides a structured approach to the identification and traceability that Indian rules expect — much of which a venue would otherwise have to assemble itself. For an operator, this is part of the appeal: you work within a framework built for compliance rather than improvising it.
That said, each operator should confirm the specific obligations for their role and scale; our guide to public Wi-Fi log compliance covers the underlying principles in detail.
Getting started as a PDO
For most newcomers the sensible entry is to start as a PDO at one good location, partner with an established PDOA, prove the economics, and expand from there. The capital is modest, the compliance burden largely sits with the PDOA, and you learn what footfall and pricing actually deliver before scaling.
- Pick a high-footfall location
- Choose a reliable PDOA partner
- Install a PM-WANI-ready access point and backhaul
- Start with a free + paid tier mix
- Expand once the economics are proven
The opportunity behind PM-WANI
Hundreds of millions of Indians still lack reliable, affordable internet access, and public Wi-Fi is one of the most direct ways to close that gap. PM-WANI was created to unlock exactly this — to let a vast number of small operators light up hotspots without the licensing and capital barriers that previously made public Wi-Fi the preserve of large telcos. For entrepreneurs, that represents a genuine ground-floor opportunity in a market with enormous unmet demand.
The framework’s design — open roles, no licence for PDOs, interoperable apps — is deliberately built to encourage participation at scale. Whoever moves early to build coverage and a trusted brand in their area is well placed as adoption grows, which is why understanding the model now is worthwhile even if you start small.
Building a PDOA platform
The more ambitious play in PM-WANI is to become a PDOA — the aggregator that authenticates users, handles billing, manages a fleet of PDOs and ensures compliance. It is a real technology and operations undertaking, requiring a reliable platform, payment handling, and the ability to onboard and support many hotspots, but it captures far more of the value than running individual hotspots and lets you build a branded network.
A PDOA lives or dies on the reliability and scalability of its platform, which is where cloud-managed networking and central control become essential — the same zero-touch and fleet-management capabilities that make any large network manageable. Choosing the right underlying technology partner is the foundation of a credible PDOA.
Scaling a hotspot network
Whether you run hotspots directly or aggregate others, growth brings the same challenge: managing many distributed, often unattended sites reliably. That demands central visibility of every hotspot’s health, the ability to provision new sites quickly, and fast detection and resolution of outages before users lose trust. A patchwork of individually managed access points does not scale; a cloud-managed fleet does.
This is where infrastructure choice shapes the business. Hardware and a platform built for fleet management — from a local OEM with the stock and support a rollout needs — let a small team operate a large network of hotspots. Scaling is as much an operations problem as a commercial one, and the operations are won or lost on the management platform.
Risks and how to manage them
Like any venture, a PM-WANI business has risks worth naming: revenue depends on footfall that may disappoint, hardware in public places faces weather and tampering, and compliance obligations must be met consistently. None is fatal, but each needs managing — by choosing locations on evidence, using rugged hardware and resilient backhaul, and leaning on a reputable PDOA so compliance is built in rather than improvised.
The operators who succeed treat it as a real business: test locations before committing, blend free and paid tiers to build habit and revenue, and invest in reliable infrastructure and management so the network earns trust. Approached that way, the modest barriers PM-WANI lowers become a genuine opportunity rather than a gamble.
Partnerships across the ecosystem
The most successful PM-WANI operations are rarely solo efforts; they are partnerships that play to each party’s strengths. A local entrepreneur who knows the area runs the PDOs, an aggregator provides the platform and compliance, an OEM supplies and supports the hardware, and app providers bring users. Spreading the roles spreads both the investment and the risk, and lets each participant focus on what it does best.
For someone entering the space, the practical lesson is to choose partners as carefully as locations. A reliable PDOA, dependable hardware from a local OEM, and a clear commercial arrangement turn a collection of hotspots into a coherent, sustainable network rather than a fragile side project.
The road ahead for public Wi-Fi
Public Wi-Fi in India is still early, and the direction of travel is clear: rising data demand, government backing for digital inclusion, and a framework deliberately designed to lower barriers. As more people come online and expect connectivity everywhere, well-placed public Wi-Fi becomes both a public good and a viable business. Operators who build trusted coverage and reliable operations now are positioning for that growth.
The infrastructure choices made today shape whether a network can ride that wave. Cloud-managed, scalable hardware that a small team can operate across many sites is what lets an operator grow with demand rather than being capped by operational overhead. PM-WANI opens the door; disciplined execution and the right platform are what carry a business through it.
Bringing it together
PM-WANI turns public Wi-Fi from a telco-only activity into something a broad range of operators can build a business on. Whether you start as a single PDO or aim to run a PDOA platform, the fundamentals are the same: choose locations on evidence, partner well, blend free and paid tiers, and invest in reliable, centrally managed infrastructure so a small team can run many sites. The barriers are low by design; execution is what separates a sustainable network from a stalled experiment.
Immunity supports public-Wi-Fi operators end to end — PM-WANI-ready hardware, cloud management and local support from a Make-in-India OEM. If you are exploring a public Wi-Fi venture, that combination of an open framework and dependable infrastructure is what makes the opportunity real.