(The Weekend Insight) - Inside the Startup Economy Powering India’s Airports

In today’s deep dive, we will look beyond airlines and airport construction to examine the businesses that keep an airport functioning every day. This includes ground handling, passenger movement, baggage, cargo, retail, queues and airport operating software. India is building more airports, but the larger recurring market may emerge after the terminals and runways are ready.

India had 165 operational airports as of July 2026. The government wants this number to reach 350 to 400 by 2047, while the Modified UDAN programme proposes another 100 airports from existing unserved airstrips. The expansion is usually discussed through aircraft orders, new routes and terminal investments. Each new airport, however, also needs software to assign gates, deploy workers, track baggage, manage cargo, bill retailers and move passengers through the terminal.

That is the Airport Economy.

Building an airport is only the first step

An airport is a shared workplace for several organisations that do not report to the same management.

The airport operator controls the terminal, runway, gates, aircraft stands and commercial areas. Airlines control their flights and passengers. Ground-handling companies load bags, clean aircraft, move equipment and manage boarding. Security agencies control entry and screening. Customs and immigration handle international travellers. Retailers, restaurants, parking companies, cargo operators and transport providers run their own businesses within the same property.

A delay in one part quickly enters another.

A late aircraft changes the gate requirement. A gate change affects passenger movement. Delayed baggage unloading holds up the next departure. A crowded security lane can create missing passengers at the boarding gate. A grounded baggage tractor can delay several flights during the morning peak.

Most of these problems are coordination problems. The physical equipment may be available, but the right people may not know where it is, whether it is working or when it will be required.

On July 23, 2026, Indian airports recorded about 9.73 lakh domestic and international passenger footfalls in one day, along with more than 6,300 aircraft movements. At this volume, airport operations cannot depend on calls, radio messages, spreadsheets and manual registers.

This is where the software opportunity begins.

The ground operation behind a 45-minute turnaround

When an aircraft lands, a clock starts running.

Passengers must leave the aircraft. Bags have to be unloaded. The cabin must be cleaned. Food and water may have to be replenished. Fuel may be added. Waste has to be removed. The next set of bags must be loaded. Passengers need to board. The aircraft then has to be pushed back from the parking position.

Several teams perform these jobs, often through different contractors.

An airline may know when its aircraft arrived, but it may not have a live view of whether cleaning has finished, whether the baggage loader has reached the aircraft or whether the pushback vehicle is available. Ground-handling managers, meanwhile, may be deploying the same pool of workers and equipment across dozens of flights.

Rsmart Aviation Software is one Indian company building for this layer. Its systems cover aircraft turnaround management, ground-worker deployment, equipment utilisation, task tracking and service-level monitoring. A ground handler can record when each activity begins, receive alerts when a task is delayed and compare the actual turnaround with the airline’s service agreement.

This may sound like workforce software adapted for airports, but the operating conditions are different.

A factory shift has a relatively stable production plan. Airport demand changes with flight delays, weather, gate changes and aircraft substitutions. Workers also need different certifications for different tasks. A person cleared to drive one type of equipment may not be allowed to operate another. Staff and vehicles may need security permission to enter certain areas.

Ground-handling software therefore sits between workforce management, fleet management and flight operations.

Blunav is approaching the same market from the airport-operator side. Its Aerios platform brings together flight information, aircraft stands, gates, check-in counters, display systems, baggage belts, billing and lost-and-found operations. The company says two of its AAI-certified systems are live at Chennai International Airport. In one study covering 3,500 flights, its airside system was used to measure a 22 percent reduction in runway occupancy time.

The significance is not the percentage alone. Airport operators need to know whether an investment in a taxiway, rapid-exit route or operating process is actually reducing the time an aircraft occupies the runway. A software layer can convert an operational change into measurable data.

That gives it a clearer business case.

Passenger flow is a capacity problem

Airports cannot keep adding counters and security lanes every time passenger traffic increases.

A terminal has fixed walls, limited gates and limited space. During a morning peak, a security area may be overcrowded while another part of the terminal remains underused. The problem is often less about total capacity and more about knowing where passengers are gathering and how quickly the queue is moving.

Bengaluru Airport connected Industry.AI’s computer-vision platform to more than 500 live camera feeds at Terminal 2. The system was designed to monitor queues, identify congestion, track abandoned baggage and alert security teams about suspicious activity.

The same camera network that was installed for security can therefore become an operating tool.

An airport can estimate how many people are waiting at a checkpoint, whether a queue has crossed a defined threshold and how long passengers are taking to move from one area to another. This can help managers decide when to open another security lane, move employees or change the allocation of check-in counters.

The next step is prediction.

An airport already knows the departure schedule, aircraft capacity and expected passenger load. It also has historical information about how early travellers arrive for domestic and international flights. Combining this data with live queue information can help estimate where congestion will appear 20 or 30 minutes later.

This matters because airport queues do not have a single owner.

Airlines manage check-in. Security agencies manage security checks. Immigration departments manage passport control. Airport operators control the terminal space. A passenger sees one journey, but the process is split between several institutions.

That fragmentation creates room for a neutral passenger-flow platform that gives every participant the same operating picture.

There is also a commercial reason to reduce queues. A passenger who spends 45 minutes at security has less time to eat, shop or use airport services. Faster processing can increase the time available inside the departure area, where most airport retail is located.

Passenger flow therefore connects operating efficiency with commercial revenue.

Digi Yatra solves identity, not the entire queue

India has already created a large digital layer around passenger identity through Digi Yatra.

The system allows enrolled passengers to use facial verification at selected airport checkpoints instead of repeatedly presenting a boarding pass and identity document. It can reduce friction at terminal entry and boarding, but identity verification is only one part of passenger movement.

A Digi Yatra gate may process passengers quickly while the security queue behind it remains crowded. An automated check-in machine may issue a boarding pass, but the passenger may still wait to drop a bag. A fast boarding gate does not solve congestion caused by late incoming aircraft.

The larger opportunity is therefore not another passenger identity app.

It is software that connects the flight schedule, expected passenger load, live terminal movement, staff availability, security lanes and gate operations.

The buyer may be the airport operator rather than the passenger. This is an important difference because consumer airport apps face a difficult usage pattern. Even a frequent traveller may visit an airport only a few times a month. Most travellers will not maintain several airport-specific apps.

Hoi is an example of the consumer and commerce layer. Its platform offers flight tracking, lounge checks, meet-and-assist services, food ordering, cabs and airport services, with the current website centred on Delhi Airport.

Such platforms can be useful when they combine several high-intent services in one place. Their challenge is distribution. The airport or airline often controls the most valuable passenger touchpoints, including booking messages, check-in communication, airport Wi-Fi and terminal screens.

A standalone app must either win an airport partnership or spend heavily to acquire passengers who may use it only occasionally.

Baggage remains the clearest gap

A checked bag passes through several hands before it appears on the arrival carousel.

The airline accepts it. The airport’s conveyor system moves it. Security equipment screens it. The ground handler sorts and loads it. Another team unloads it at the destination. The airport then allocates a baggage belt for delivery.

Each handover creates a possible failure.

A damaged paper tag may become unreadable. A bag may reach the wrong sorting area. A transfer bag may miss a connecting flight. A suitcase may be unloaded but remain on a trolley. A passenger may take a similar-looking bag from the carousel.

The present system depends heavily on barcodes, bag tags and manual scans. The opportunity is to create a stronger digital identity for the bag.

That could include an image of the suitcase, weight, colour, dimensions, tag details, scan history and its last known location. Computer vision could help identify an untagged bag. Software could warn a ground handler when a transfer bag is running out of time. The passenger could receive an estimated carousel delivery time before leaving the aircraft.

India has businesses in baggage logistics, but there is still no clearly visible Indian startup controlling this complete intelligence layer.

Dropty offers home-to-airport and destination baggage pickup and delivery, including booking and real-time tracking. This removes the need for a passenger to carry luggage through part of the journey, but it remains a managed logistics service rather than an airport baggage-reconciliation platform.

Blunav includes lost-and-found and baggage-belt functions within Aerios, while Industry.AI can detect abandoned baggage through airport cameras. These solve parts of the problem. They do not yet create a continuous digital record from check-in to delivery.

Baggage intelligence is difficult because the required data sits across airlines, airports and ground handlers. A startup cannot solve it with a passenger app alone. It needs operational integration and permission to enter critical airport systems.

That makes adoption difficult, but it can also make the product hard to replace after deployment.

Airport cargo may be the strongest Indian software category

Passenger baggage receives more public attention. Airport cargo may offer the stronger software business.

Air cargo involves airlines, freight forwarders, customs brokers, transporters, warehouses, ground handlers, exporters and importers. Documents and shipments must move between all of them. A missing approval can leave cargo sitting in a terminal even when aircraft capacity is available.

Kale Logistics Solutions has built an airport cargo community system that puts these participants on a common platform. The company says its system is trusted by more than 120 airports and connects airlines, ground handlers, forwarders and customs authorities.

This is a useful model for the wider Airport Economy because Kale is not selling a small productivity feature to one employee. It is creating shared infrastructure for an entire trading community.

The value increases as more participants join.

A freight forwarder can submit documents before the truck reaches the terminal. A transporter can book a slot instead of joining an uncontrolled line outside the cargo gate. A warehouse can prepare for the shipment. Customs information can move electronically. The airport gains better visibility over incoming traffic and cargo volumes.

CargoFlash operates in another part of this market. Its products cover cargo reservations, revenue accounting, warehouse management, freight forwarding and other air-cargo workflows. IATA’s partner directory also lists its end-to-end cargo and warehouse systems.

These companies show that Indian airport software can travel outside India.

Cargo processes have local customs rules, but the underlying problems are similar across markets. Airports everywhere need to coordinate warehouses, handlers, airlines, trucks and documentation. An Indian company that builds a lower-cost system for domestic airports can take the same product to airports in Southeast Asia, Africa and the Middle East.

This export route may be easier than consumer aviation because the product does not depend on building a local passenger brand in every country.

The airport is also a retail landlord

Airports earn money from retailers, restaurants, lounges, parking, advertising and other commercial services.

Many concession agreements include a minimum payment or a share of the retailer’s sales, whichever is higher. This creates a basic data problem. The airport must know how much each store has sold and calculate its own revenue under different contract terms.

Retailers may use different point-of-sale systems. Some data may arrive late. Contract conditions may differ by terminal, store, category and time period. Manual reporting creates room for errors and revenue leakage.

GrayMatter’s StoreSense captures point-of-sale information from airport retailers, maintains concession contracts, calculates revenue share and provides store-level analytics. The company cites an implementation at Bengaluru Airport. Its product can also combine POS information with boarding-pass and passenger data to analyse purchases by destination or traveller profile.

This turns airport retail from a property-management activity into a software category.

The airport can compare sales by store location, flight bank, passenger nationality or destination. It can identify whether a food outlet beside one gate performs better because of passenger traffic or because its conversion rate is higher. It can detect whether reported sales suddenly fall even though footfall remains stable.

For a retailer, the software can improve inventory planning. An airport store does not see normal neighbourhood demand. Sales are influenced by flight schedules, delays, departure destinations, security restrictions and the time passengers have before boarding.

A restaurant may need more food before a large international departure. A convenience store may see higher sales when flights are delayed. A duty-free shop may need different inventory based on the mix of destinations.

Airport retail software therefore has two possible buyers. The airport wants accurate revenue and concession management. The retailer wants better sales and inventory planning.

The stronger platform may eventually serve both.

Regional airports need a different product

The systems used by Delhi, Mumbai or Bengaluru cannot always be copied into a small regional airport.

A metro airport can support large contracts, on-site implementation teams and expensive integrations. A smaller airport may operate a limited number of daily flights. It still needs flight information, gate allocation, billing, baggage-belt management and compliance, but it cannot carry the same technology cost.

This is where India’s airport expansion becomes relevant for startups.

AAI manages 125 airports, which gives it considerable influence over what systems are used across the network. At the same time, India also has private and state-government airports with different buying processes.

A startup selling one customised deployment at a time may struggle. The better opportunity is a modular cloud product that can be configured for several airports.

A small airport may begin with flight operations, billing and display management. It may later add ground-handling, retail and passenger-flow modules. Several airports could share a remote operating centre, technical support team and common software infrastructure.

Pricing would also need to change.

A regional airport may prefer to pay according to passenger traffic, aircraft movements or active modules rather than a large fixed licence. The vendor benefits as traffic grows, while the airport avoids paying metro-airport prices before it has metro-airport volumes.

Blunav’s positioning around a modular operating system for regional as well as larger airports fits this gap. The opportunity, however, will depend on whether such products can move beyond pilots and become standard systems across several locations.

Who will pay for this software?

The Airport Economy does not have one customer.

An airport operator may pay for gate allocation, passenger-flow analytics, billing and retail management. A ground-handling company may pay for workforce and equipment software. An airline may pay for baggage visibility or turnaround monitoring. A cargo terminal may pay for warehouse and documentation systems. A retailer may pay for inventory and sales analytics. A passenger may pay for fast-track access, baggage delivery or meet-and-assist services.

This creates several possible business models.

Ground-handling software can be charged per flight, airport or active worker. Baggage systems can be priced per bag. Passenger-flow systems may use a licence plus charges for cameras or processing volume. Airport retail products can charge per point-of-sale device or take a share of additional commercial revenue. Cargo platforms can charge subscriptions, document fees or transaction fees.

The quality of revenue matters more than the size of the first airport contract.

A startup may announce a large implementation, but much of the value could be hardware procurement, installation and custom development. These are useful revenues, though they do not automatically create a repeatable software business.

The stronger company will be able to deploy the same core product at another airport without rebuilding it.

It will also have recurring revenue after implementation. Airports need continuous support because systems run through nights, weekends and public holidays. Updates, integrations, security monitoring and operational support can become long-term contracts.

Once a product controls gate allocation, billing or cargo documentation, replacing it becomes risky. That can lead to low customer churn.

The cost is a slow sales process.

The airport buyer is difficult to reach

Airport software must work with old equipment, several agencies and strict security rules.

A product may perform well in a demonstration but fail when connected to existing baggage systems, airline databases, access controls or display boards. A small error in normal business software may delay a report. A small error in airport software can disrupt passengers or flights.

Airports therefore ask for trials, certifications, references and integration work.

The first commercial deployment may take years. Startups may need to partner with larger system integrators that already qualify for airport tenders. This can help them enter the market, but it can also leave the startup as a small technology supplier while the larger contractor controls the customer.

Customer concentration is another risk.

India may have 165 operational airports, but procurement power is held by a smaller number of operators. AAI alone manages 125 airports. Large private groups operate several major airports. Losing one group can close access to a large part of the market.

The product also needs aviation knowledge.

A general workforce platform may not understand aircraft turnaround rules. A normal retail system may not understand airport concession contracts. A logistics platform may not understand customs, air waybills or dangerous-goods requirements.

Founders will need airport professionals who understand how the work is actually done. The technical product and the domain knowledge have to be built together.

Where the real startup gaps remain

Ground handling and cargo are already proven categories.

Rsmart shows that specialised software can manage ground workers, equipment and aircraft turnaround. Kale and CargoFlash show that air-cargo systems can be built in India and sold internationally. GrayMatter proves that airport retail and concession management can become a software product. Blunav is attempting to bring several airport operating functions onto one modular platform.

The thinner categories are baggage intelligence and independent passenger-flow software.

India still lacks a visible specialist that creates a continuous baggage record across airline, airport and ground handler systems. Queue technology exists, but it is frequently supplied as part of a broader camera, security or airport-management project.

There is also room between these categories.

Airport workers need certification, roster and access-management systems. Ground equipment needs telematics and predictive maintenance. Lost-and-found departments need shared databases and image matching. Retailers need flight-linked inventory forecasting. Regional airports need common cloud infrastructure. Airport operators need neutral data layers connecting systems that were purchased at different times from different vendors.

These markets may not produce consumer brands. Most passengers may never know the company’s name.

That is normal.

The best airport software is often visible only when it fails. A passenger notices a lost bag, a long queue or a missing gate update. The system preventing these problems remains in the background.

The Airport Economy will be built one workflow at a time

India’s airport expansion creates a genuine startup market, but the number of airports alone does not guarantee large companies.

Some regional airports may handle limited traffic. Procurement will remain concentrated. Sales cycles will be slow. Global vendors and large IT companies will compete for core systems. Many startups may become project businesses because airports demand customisation.

The opportunity is strongest where the problem repeats across airports and the result can be measured.

Can the software reduce aircraft turnaround time? Can it process more passengers through the same terminal? Can it prevent baggage errors? Can it move cargo faster? Can it increase retail revenue? Can it allow a small airport to operate with fewer manual systems?

These are operating questions, not technology questions.

India has already produced credible companies in airport cargo, ground handling, retail analytics and airport operations. What it does not yet have is one clear company controlling the full software layer across its growing airport network.

That company may not begin by trying to replace every system.

It may begin with one expensive problem, such as delayed turnarounds, cargo congestion, missing bags or retail leakage. Once that product becomes part of the daily operation, it can enter the adjacent workflows.

A runway creates connectivity. A terminal creates capacity. The recurring business begins when somebody has to keep both of them working every day.