Terminal-grade passenger Wi-Fi, a captive portal that doubles as the airport’s front door, and hard separation of airline, operational and tenant systems — on one Make-in-India stack with NetWave access points, NetForce switching and NetGuard controllers.
Trusted where uptime is non-negotiable
A terminal is the hardest wireless environment most buyers will ever specify: thousands of unfamiliar devices arriving in waves, an open volume with almost no walls to shape the signal, and airline, ground-handling and retail systems under the same roof that must never share a broadcast domain with a passenger’s phone.
Immunity designs by concurrent devices per zone rather than square metres, covers aprons and kerbsides with ruggedised outdoor units, and enforces separation in switching hardware with policy at the NetGuard controller. NetCloud Central runs every pier, satellite and cargo shed from one console.
Passengers judge the airport by whether Wi-Fi works at the gate. Operations judge it by whether nothing leaks. Both have to be true.
Gate hold rooms, security queues and immigration halls concentrate devices into small footprints for short, predictable peaks.
High ceilings, glass facades and long sight lines need APs mounted on gantries, soffits and columns, not a convenient false ceiling.
Baggage handling, CUTE/CUPPS check-in, the airport operational database and ground handling stay off the passenger network.
A portal that works on an unfamiliar device, in the passenger’s language, and gives something back.
Lounges, retail and F&B concessions get their own SSID, VLAN and bandwidth policy with no visibility of each other.
MTCTE, TEC and WPC status confirmed in writing for the exact SKUs in the bill of materials, ready for the tender file.
Each capability links to the product that delivers it.
Lotus Alpha indoor units for concourses, gates and lounges; ruggedised outdoor units for aprons, stands, kerbside canopies and perimeter roads.
Explore NetWave WiFi →Branded captive portal with live flight information, wayfinding to the right pier, announcements and language options — plus sponsorship and tenant offers.
Explore NetGuard Controller →Passenger, operational and tenant domains on distinct VLAN sets carried by NetForce L2 and L3 switches, with inter-domain policy at the gateway.
Explore NetForce switching →NetCloud Central manages every pier, satellite, cargo shed and car park with zero-touch provisioning and per-zone dashboards.
Explore NetCloud →From the kerb to the gate — and exactly what we put behind each moment.
They expect: A full flight’s worth of devices online at once, for 40 minutes, then gone.
We deliver: Density-led AP placement per hold room, airtime fairness and client isolation on the passenger SSID.
They expect: No routed path from a passenger device into baggage, check-in or the operational database.
We deliver: A separate operational domain with its own addressing and policy owner, enforced in NetForce switching hardware.
They expect: Their own network, their own branding, their own bandwidth — billed and reported per tenant.
We deliver: Per-tenant SSID and VLAN with bandwidth tiers and portal branding from the NetGuard controller.
They expect: Coverage for ground crews, taxi ranks and cargo areas in heat, dust and monsoon.
We deliver: IP-rated Lotus Alpha OD units on poles and canopies, fed over PoE from managed edge switches.
They expect: No moment when the terminal is empty; installation cannot disrupt operations or security.
We deliver: Zone-by-zone cutover planned with airport operations, zero-touch provisioning so units go live on power-up.
They expect: Per-model certification evidence, Make-in-India documentation and an OEM that answers within the bid window.
We deliver: Written per-model MTCTE / TEC / WPC confirmation, OEM authorisation letters and certificate mapping to your RFP checklist.
Jump to the products behind this solution.
No. Passenger traffic sits on its own VLAN set enforced in NetForce switching hardware, with policy applied at the NetGuard controller. There is no routed path from the passenger domain into baggage handling, common-use check-in platforms, the airport operational database or ground-handling systems, and client isolation stops passenger devices reaching one another.
Yes. Each tenant gets its own SSID mapped to its own VLAN, with its own bandwidth and access policy and no visibility of other tenants or the passenger network.
Yes. The splash page is served by the NetGuard controller as a web page, so it can carry live flight status for the passenger’s own flight, wayfinding, announcements and language options, alongside sponsor or tenant offers.
With ruggedised, IP-rated Lotus Alpha outdoor units on poles, canopies and parapets, powered over PoE from managed edge switches and managed from the same console as the terminal.
The Broadband India Forum’s 2026 report recommends integrating institutional Wi-Fi across airports, railways, hospitals and campuses into the national PM-WANI framework. Immunity is a certified PDO Aggregator and separately a Public Wi-Fi Partner with BSNL; our Managing Director co-authored that report as Co-Chair of the BIF Wi-Fi Committee. See the PM-WANI page.
Written, dated confirmation of MTCTE, TEC and WPC status per model in the bill of materials, OEM authorisation letters through our partner programme, and certificate numbers mapped to your RFP checklist. Start on the certifications page.
Tell us the terminal footprint, the piers and satellites in scope, the systems that must stay separate and where passengers complain today. Our engineers will return a zone-by-zone coverage plan and datasheets, with model specifications confirmed in writing.
See how this runs in production. Each case study covers the environment, the exact Immunity stack and the outcomes delivered.
Real Immunity deployment — challenge, stack and outcomes.
Read case study →AviationReal Immunity deployment — challenge, stack and outcomes.
Read case study →HealthcareReal Immunity deployment — challenge, stack and outcomes.
Read case study →Tell us about your sites and users — our India-based engineers will recommend the right stack and send across datasheets and pricing, usually within one business day.