Amir Khan had already helped build a company that Cisco wanted to buy. Viptela’s acquisition was completed in 2017 for $610 million in cash and assumed equity awards. A perfectly respectable next move would have involved a quieter calendar. In 2018, he co-founded Alkira. Apparently, enterprise networking had left something unfinished.
The continuity matters more than the price tag. Viptela addressed how businesses connected their far-flung locations. Alkira addressed what happened when their applications and infrastructure spread across clouds. Each company began around a practical inconvenience that had grown large enough to become an industry habit. Khan kept asking how much of the assembly the customer ought to be doing.
There is an appealing impatience in that question. Networking can reward people for understanding complicated machinery. Khan’s business has been to understand it well enough to make using it less complicated. The expertise stays backstage; the customer gets a more manageable day.
The customer’s side of the desk
His route into the industry began before the founder titles. Khan grew up in Pakistan and moved to the United States in 1984. His education took him to the University of Mississippi, then the University of Colorado Boulder. Electrical engineering provided the formal preparation. Work would supply a rather less orderly syllabus.
At Ford, he deployed Cisco routers. Cisco subsequently recruited him. By 1991 he was inside the company whose equipment he had been using. That move carried a useful change of perspective: he had experienced the product from the customer’s side before helping the vendor build its business.
The later résumé runs through Cisco, Nortel, Procket and Juniper. Roles in product management sit alongside technical experience. That combination helps explain the shape of his eventual companies. A network has to function, but somebody must also buy it, operate it, understand its limits and live with it when requirements change.
At Juniper, he worked on enterprise routing. The word “enterprise” can drain the color from a sentence, yet it describes the setting that made his experience useful: organizations with existing systems, real obligations and limited appetite for replacing everything at once. Any promising new idea had to enter a room already crowded with old decisions.
A thirty-minute pitch that ran long
Viptela was founded in 2012. In its early encounter with Sequoia, a planned half-hour pitch became a two-hour working session. Khan and fellow founder Khalid Raza had spent years hearing customers describe their network problems. They arrived with something more substantial than an attractive diagram.
Their product applied software-defined networking to the wide-area network, or WAN: the connections spanning branches, offices and data centers. The engineering separated network control from traffic forwarding while retaining compatibility with existing routing protocols. It gave enterprises a way to change how they managed connections without requiring the rest of the internet to attend a renovation meeting.
The beginning included awkward limits. The early product needed work to handle scale. Customers also asked Viptela to operate control systems in the cloud, a service the company added within months. These details make the story more useful. Customer demand was changing the product while the company was still establishing itself.
“I started my first company when I was 48 years old.”
Amir Khan
Cisco completed the purchase on August 1, 2017. Its announcement placed Viptela within a shift toward software and subscriptions, with the team joining enterprise routing. Khan’s career had crossed the boundary between established vendor and startup repeatedly. Now a company he had helped create was entering the organization where he had spent earlier chapters of his working life.
August 2017
Acquisition completed July 2026
The cloud still needed plumbing
The next problem was hiding inside the promise of cloud computing. Businesses could obtain computing and storage as services, while connecting the resulting environments remained a project. Different clouds brought different network arrangements. A company might gain flexibility in where it ran applications and acquire a fresh collection of chores along with it.
Khan and Atif founded Alkira in 2018. Kleiner Perkins and Sequoia backed the company early. When its Cloud Services Exchange became public in 2020, the proposition was a unified way to connect and operate networks across clouds, with services, visibility and governance included.
In plain language, the customer would describe the network it needed, and Alkira would handle more of the work required to make it run. A visual design canvas replaced part of the customary assembly process. The ambition extended beyond drawing a tidier picture. The service had to manage the infrastructure beneath that picture.
That is an ambitious transfer of responsibility. The difficult work still exists, but the provider takes on more of it. For a buyer, the value lies in how much less coordination is required to make another location, application or business partner reachable. The useful unit of progress is a task removed from somebody’s week.
A brother in the next chair
Atif Khan is Alkira’s co-founder and CTO. His remit includes technology direction, engineering and product development. Their partnership gives the company a division of labor familiar to many technical businesses: commercial and organizational leadership alongside responsibility for making the system work.
It also comes with a sibling’s license to puncture a solemn interview. Asked which brother was older, Amir answered: “I’m older and he has less hair.” The brothers had shared accommodation in Boulder long before sharing another company. Some working relationships arrive with more background material than a reference check can reasonably contain.
The photograph offers a welcome change from the usual executive setting. Patterned shirts and sunglasses have temporarily displaced product architecture. The family connection is part of the company’s story, but their responsibilities remain concrete: a business has to win trust, and the technology has to deserve it.
When the customer buys a stake
One early Alkira customer became a financial backer. Koch Disruptive Technologies led the company’s $54 million Series B in October 2020. Koch had already used Alkira to rebuild its cloud network backbone. Its investment therefore followed a direct encounter with the product.
That sequence makes the funding more revealing than a list of investor names. A large organization had put the service to work, then committed capital to the business providing it. The customer relationship and the investment relationship carried different obligations, but they met around the same question: could this approach handle a complicated operating environment?
In May 2024, Alkira announced a $100 million Series C led by Tiger Global, taking the company’s reported funding total at that date to $176 million. Warner Music Group, another customer, described using the platform to simplify network management and redirect attention toward business growth.
Khan credited the team in the funding announcement. Raising capital bought room to develop the service and expand the organization. An infrastructure business cannot spend all its energy making the next demonstration attractive. It also has to support the customers who are already relying on yesterday’s promises.
The work between the announcements
Khan’s own writing broadens the picture beyond cloud diagrams. In 2021, he described remote workers as “branches of one,” applying the vocabulary of corporate networks to people working away from an office. His argument concerned a changing pattern of work and the connections required to support it.
By 2026, artificial intelligence had become another focus of his public conversations. In March, he sat down with Maria Martinez, the former Cisco COO and an Alkira customer advisory board member, to discuss enterprise networking, hybrid infrastructure, security and talent. The network question had acquired another demanding set of users.
These conversations return to a persistent tension in his work. Businesses want to move applications and data more freely. Their networks must preserve control while allowing that movement. More destinations create more decisions, and a service promising simplicity has to make those decisions easier to carry out consistently.
His aspiration, expressed in public biographies, is to deliver cloud networking as a utility. It is a useful way to judge the product. Utilities earn their place through dependable use. The grand occasion is less important than the ordinary morning when everything that needs to connect can connect.
The network gets a new owner
On May 5, 2026, Lumen announced an agreement to acquire Alkira for $475 million in cash. The planned combination joined Alkira’s cloud-native control plane with Lumen’s physical network and commercial reach. Lumen completed the acquisition on July 7.
For Khan, another acquisition brings a different engineering and business setting. Lumen has described a path toward integrating Alkira into Lumen Connect. Software that coordinates connections and infrastructure that carries traffic must work together in a way customers can use. The transaction is complete; the integration has its own timetable.
His letter to customers at the agreement stage concentrated on continuity: existing contracts, pricing, support and service commitments. The emphasis was practical. A customer celebrating its vendor’s acquisition still expects the network to work on Tuesday.
As of October 21, he is scheduled to speak at ONUG on October 29 about consuming networks in the agentic era. It is another version of the question running through this career: how much infrastructure should a business have to assemble before it can get on with its business? Khan has spent years learning the machinery. He keeps finding reasons to make it less of the customer’s concern.