A car rolls off a cargo ship in a new country. The wheels are familiar; the software paperwork is not. Its embedded SIM may need a local profile. Its data must obey local rules. The automaker still wants one dashboard, one service policy and one coherent bill. Somewhere between the vehicle and the driver's first tap on “remote start,” a small diplomatic mission has to occur among carriers, clouds, consent systems and corporate back offices.
This is AIRLINQ's territory. The privately held California company sells enterprise software that connects and manages large populations of things - cars, utility meters, factory equipment, retail devices - over multiple networks. The radio signal is only the beginning. AIRLINQ's platform also provisions SIMs, watches usage, diagnoses faults, applies security and roaming policies, feeds data into other systems, and helps customers charge for whatever service the connection makes possible.
That makes the company less like a carrier and more like an air-traffic controller for connected products. Mobile operators, automakers, utilities and industrial businesses use it to see disparate fleets through a common interface. Open APIs let their own applications issue commands. Cloud-agnostic deployment leaves room for AWS, Azure, Google Cloud or private infrastructure. The business sits in a dense market beside Aeris, Cisco IoT Control Center, Ericsson IoT Accelerator, Tata Communications MOVE, Soracom, floLIVE, KORE and the internal platforms of major operators.
The problem begins after “connected”
An IoT demo is usually cheerful: a sensor sends a reading, a map gains a dot, an engineer applauds. Production is where the complications arrive. A company may have several device models and contracts with several carriers. One SIM is active but silent; another is roaming expensively; a third belongs to a machine retired six months ago. Usage records have to meet billing systems. Security teams want policies. Customer-support teams want diagnostics. Finance wants to know why the data bill jumped in Chile.
Scale multiplies every exception. AIRLINQ's public Jio case study, published in 2020, described a platform benchmarked for more than 50 million devices. At that level, “single pane of glass” is not merely dashboard poetry. An operator needs to activate and suspend connections in bulk, isolate abnormal behavior, split charges among parties, and expose services to enterprise customers without handing over the keys to its network.
One connected object, three operating worlds
The platform's practical promise is abstraction. A unified API can shield an enterprise application from the peculiarities of each underlying network. An eSIM can receive a local carrier profile without a technician replacing plastic in thousands of cars. Policy automation can flag a usage spike before it becomes a surprising invoice. Real-time diagnostics can tell support staff whether the failure sits in the device, the network or the service behind it.
“Global IoT scale is no longer limited by technology, but by regulation.”Sunil Kaul, AIRLINQ CEO
Four products, one piece of plumbing
AIRLINQ packages its common platform around different buyers. The naming is almost unusually helpful. Mobilinq is the broad IoT and connectivity-management core for mobile operators and enterprises. Autolinq specializes in the connected vehicle, where location, diagnostics, infotainment, remote commands and over-the-air updates have to coexist with consent and data-residency requirements. Utilinq applies similar controls to electric, gas and water infrastructure. Marketlinq provides a storefront through which connectivity and IoT services can be procured, tested and deployed.
This is a recognizable vertical-software strategy: build a shared engine, then translate it into the language and workflow of each industry. An automaker cares about vehicle uptime and subscription features. A utility talks about meter fleets, grid resilience and long device lives. A carrier wants multi-party billing, enterprise self-service and a faster route to new revenue. Underneath, all three are trying to manage identities, connections, policies, data and money.
The useful trick
AIRLINQ does not ask customers to treat connectivity as a separate technical chore. It attaches connectivity controls to the commercial lifecycle of the product - from activation and support to billing, renewal and retirement.
Who pays, and what they buy
AIRLINQ is a business-to-business platform. It does not publish a price list, and its contracts are likely shaped by device volume, modules, integrations, geography and service requirements. The economic pitch is easier to see than the invoice: replace a patchwork of carrier portals and internal tools, reduce manual operations, shorten launches, prevent bill shock, and create services that can be sold after the hardware leaves the factory.
For a mobile operator, that may mean selling more than raw megabytes. Mobilinq can support an operator-branded IoT offer with enterprise access, analytics, vertical applications and billing. For an automaker, Autolinq can enable paid Wi-Fi, infotainment, remote controls, usage-based insurance inputs or predictive maintenance. For a utility, the product value is less theatrical: fewer truck rolls, faster fault isolation, better inventory control and early warning when meters or networks behave oddly.
Where the platform reaches
The border is the product test
Cross-border deployment is where AIRLINQ's positioning becomes most specific. Permanent roaming is restricted or treated differently in some markets. Local licensing, data handling and lawful-intercept requirements vary. A manufacturer cannot assume that a connectivity arrangement designed in California will behave the same way in Tokyo, São Paulo or Riyadh. The technical device may travel freely; its telecom identity does not.
In March 2026, AIRLINQ and NTT DOCOMO BUSINESS announced a partnership aimed directly at this problem. Their plan combines AIRLINQ's connectivity management platform with NTT DOCOMO BUSINESS's mobility experience and local carrier coordination. Customers are meant to receive unified SIM visibility across countries, remote eSIM profile switching and help aligning deployments with local rules. For makers of cars, construction machinery and agricultural equipment, a profile swap in software is preferable to touching every physical machine.
The partnership is also a clue to AIRLINQ's place in the market. It does not need to own every radio network. Its leverage comes from coordinating networks and making their differences less visible to the enterprise. That can be valuable, but it also requires deep integrations, dependable partners and the credibility to sit inside operational systems that customers expect to run for years.
AI arrives in the network room
AIRLINQ has added AI-assisted analytics throughout its product language, from anomaly detection and predictive maintenance to billing analysis. Its 2026 AI-NOC material makes the more interesting claim. Traditional monitoring software predicts that a node may fail, then leaves a human to translate the warning into an approved change. AIRLINQ describes a closed loop: observe, diagnose, recommend, approve, act and verify, with agents operating inside defined policy boundaries.
The human approval step matters. Telecom operations are full of tempting automations whose mistakes can disconnect a city block or misroute a flood of traffic. A useful AI system here is not the loudest chatbot in the room. It is the quiet colleague that correlates a thousand alarms into one cause, proposes a bounded response, records the decision and checks that the repair worked.
Recognition has followed the product push. Kaleido Intelligence ranked AIRLINQ the number-one Champion vendor in its 2025-26 connectivity management platform assessment, which evaluated 29 vendors. AIRLINQ also cites a 2025 leadership placement from Counterpoint Research, a Frost & Sullivan connected-vehicle award, and 21 patent applications with six grants. Awards do not keep a meter online, but in a conservative enterprise market they help a smaller platform survive a procurement meeting crowded with telecom incumbents.
The invisible company behind visible features
AIRLINQ's customers span mobile operators, vehicle makers, fleets, utilities, manufacturers and connected-product businesses. Its public materials name Reliance Jio in a deployment case study; they otherwise tend to describe customer categories more readily than contracts. That discretion is common in infrastructure software, where the consumer recognizes the automaker or carrier but rarely the platform making a button work.
The company's 2014 founding and its 2020 change from the Globetouch identity track the market's own evolution. Connectivity once looked like the entire IoT sale. Now it is the first layer in a longer operating system. The harder work is governing the fleet, interpreting its data, supporting the user and deciding who earns what when a physical product becomes an ongoing service.
That is the durable idea inside AIRLINQ: a connected object is never just connected. It is provisioned, observed, secured, charged, updated and eventually retired. Each verb belongs to a different corporate department until a platform puts them on the same screen. That mundane coordination is precisely what lets the visible customer experience feel simple. The car keeps moving. The software makes the border crossing look boring. In this market, boring is a feature.