Doug Houghton, director of global channels at Alkira
There’s a line from this episode that’s worth leading with: “Networking is not sexy until it doesn’t work.” That’s Doug Houghton, Director of Global Channels at Alkira, and it’s a pretty concise summary of why his company exists.
Alkira was founded by the team behind Viptela – the startup that essentially created the SD-WAN category before being acquired by Cisco. The lesson they carried out of that experience is that SD-WAN, for all its promise, still ran into the limits of underlying infrastructure. You ended up with disparate networks, latency constraints, and complexity that didn’t disappear – it just moved somewhere else.
What they built in response is Network Infrastructure as a Service (NIaaS) – a cloud-native, consumption-based global backbone that abstracts multi-cloud connectivity into a single managed plane. The pitch to partners is concrete: consolidate 50 physical firewalls into virtualized functions, reduce total cost of ownership by 40-70%, and do it without a rip-and-replace cycle.
The timing matters, and Houghton is direct about why. AI workloads – distributed large language models, agentic workflows reaching across multiple clouds simultaneously – demand a level of network elasticity that legacy infrastructure simply wasn’t designed for. Alkira’s argument is that they’re the smooth road that makes AI-driven infrastructure actually work in practice.
For Canadian partners, Alkira has real resources on the ground: a solution architect based in Toronto, a dedicated channel account manager, and publicly referenceable Canadian customers including contact center provider ContactPoint 360. The Connect Partner Program, launched in March 2026, puts approximately 20 percent total margin on the table across base discount, rebates, MDF, and POC SPIFFs – with average initial deals around $500,000 USD and typical expansion of 4x in year one. Canadian partners interested in the conversation can reach the team at [email protected].
Read Full Transcript
Robert Dutt: Hello and welcome to In The Channel from ChannelBuzz.ca, bringing news and information to the Canadian IT channel community for the last sixteen years. I’m Robert Dutt, editor of ChannelBuzz.ca and your host for the show.
If you were around when SD-WAN was the big disruptive idea in networking – the promise of simplifying branch connectivity, cutting costs, getting smarter about traffic – you probably also remember it didn’t quite deliver everything it promised. Not because the technology was bad, but because the underlying network architecture couldn’t keep up. You still ended up with complexity. It just moved somewhere else.
That problem is essentially the founding insight behind Alkira. The company was built by Amir Khan and Atif Khan, the same team behind Viptela, the startup widely credited with creating the SD-WAN category before Cisco acquired it. What they learned in that experience is that SD-WAN, without a proper global backbone, just creates a different set of headaches. So they started fresh and built what they call NIaaS – Network Infrastructure as a Service – a cloud-native, consumption-based approach that abstracts the complexity of multi-cloud connectivity into something you could stand up, as my guest today puts it, with just a username and a password.
The timing is not accidental, because what AI demands from a network – elasticity, low latency, the ability to reach distributed workloads almost anywhere instantly – is exactly what legacy infrastructure wasn’t built to handle.
My guest is Doug Houghton, Director of Global Channels at Alkira. Doug has been in the channel a long time, knows the technology in a way that might genuinely surprise you coming from a channel chief, and has a lot to say about what it all means as a real business opportunity for Canadian VARs and MSPs.
Let’s get right into it, my chat with Doug Houghton.
Doug, thanks for taking the time. I appreciate it.
Doug Houghton: It’s my pleasure. Thank you for having me on today, Robert.
Robert Dutt: So you were part of the team that built up the SD-WAN market at Viptela back in the day. What did you learn there that told you the next big thing was going to be NIaaS, and why now?
Doug Houghton: First off, that’s a great question. I felt a bit like a passenger in a car racing a thousand miles an hour when we were doing software-defined wide-area networking.
What we learned was that without organizing your cloud infrastructure properly, your cloud bill gets ridiculously large – especially if you keep your control element decoupled from your data plane in the cloud with all these workloads churning. But what we really learned, and what’s applicable to what we’re now doing at Alkira, is that SD-WAN truly did deliver on its core promise. It allows customers to influence traffic based on link quality and improve the user experience. If you’re on a phone call and it starts to get goofy, you can move over to a better-performing link in real time without dropping the call. That’s powerful. And the same with data traffic.
What I hadn’t fully thought through was what happens as global companies start to adopt SD-WAN and disaggregate across locations in Southeast Asia, China, Latin America, and everywhere else. The latency back to the control element isn’t easy to contend with. So you ended up with organizations making decisions that effectively created four separate, disparate networks for latency purposes. And that was not part of the original promise.
What we learned was that you need a global backbone that’s high throughput and low latency. The edge can still be SD-WAN – there are real things in SD-WAN that people still want, whether that’s WAN optimization, deduplication, caching, policy-based routing, forward error correction. All of that still has practical application, and site-to-site communications are still needed in many use cases.
But Alkira was built inside the cloud first, employing the same principle of decoupling control plane from data plane for scale. By abstracting the cloud infrastructure, we were able to remediate the latency that those four geographically dispersed networks created. We’re the global backbone – that middle mile with high throughput and low latency – and then you connect these clusters of SD-WAN networks together and all of a sudden the promise of SD-WAN gets a lot more consumable. You have a singular network managed from a singular control plane and element management orchestrator, and you can still get all the benefits of SD-WAN at the local sites.
Robert Dutt So in plain language, a Canadian MSP or VAR is used to selling network hardware or managing someone else’s infrastructure. How is selling, deploying, and managing NIaaS different from what they’re already doing, and what makes that distinction important?
Doug Houghton: Let’s take a half step back and talk about what NIaaS actually is. It’s Network Infrastructure as a Service. What Alkira does is abstract the cloud infrastructure and build a routed overlay on top of it. We think of it as a virtualized colocation facility that connects and normalizes communications across your entire network. For managed service providers and service providers, our solution accelerates bringing their customers to cloud applications, cloud workloads, storage, and everything else the cloud promises.
The way I explain it to my mom – and I’ve told this joke once already today because I’m sitting in a partner’s office right now – is this: if you went to Russia, Japan, Argentina, and San Francisco all in one day and had to transact in each place, and you could speak the native language in each one, that would be ideal. What we focused on was normalizing communications regardless of the cloud service provider, colocation provider, data centre – private or public – or whatever type of router is at the branch office.
As an MSP or service provider that comes in, what we give to our customers and partners is a username and a password. That lets you come in and – for your old-school folks in the audience – essentially etch-a-sketch your network together. You can turn a couple of knobs, and it’s not that we’ve cranked the amp up to eleven, we’ve just removed all the numbers and automated everything. It just knows what you want to do.
It’s a routed BGP overlay with the control plane abstracted from it, so the forwarding plane can route around things like the CrowdStrike outage, or losing an AWS region – which happens more frequently than AWS would like to admit – or any cloud service provider incident. The multi-cloud reality has accelerated adoption, but it presents a new problem: you’ve got an AWS expert on staff, but you don’t have an Azure, GCP, OCI, or Alibaba Cloud expert. Those are all different languages. When I tell my mom that we normalize the communications between all the assets in the network and make it easy to connect to all of them, she gets that.
For the MSP looking to monetize something new or add another revenue stream, we offer a couple of compelling things. In the middle of our stack, we place a solution inside the cloud – sitting in a VPC, VNet, VCN, or Google VPC – right in the middle of all the cloud, SaaS, and WAN workloads. We’ve pleased a lot of customers by lowering total cost of ownership through the consolidation of network services they already have in their environment, in the form of virtualized network functions.
Take a Palo Alto firewall deployment – say you have fifty Palos out there, all talking to Panorama, with a security engineer managing policy centrally. Instead of having fifty firewalls on the ground, you consolidate them. You go from the ground – five to ten milliseconds to the nearest public cloud PoP – hop onto the Alkira fabric, and terminate that traffic on a virtual port on our exchange point. In the middle of that exchange point, sitting in a VPC or VNet, you place a Palo Alto virtualized network function. You get the IP address of the Panorama server, and if you didn’t tell the security engineer anything had changed, they would not know. The form factor changes, but not how they interact with Panorama, how they build policy, or anything about how they secure the traffic. That remains exactly the same.
We virtualize the instance and place it on a global high-throughput, low-latency backbone inside our exchange point. We deploy exchange points in HA pairs, anywhere from 100 Mbps to 40 Gbps. The customer or service provider consumes one, and we maintain the other on their behalf – because every thirty days we’re fixing bugs and doing maintenance. We swing production workloads to the backup, do the work on the primary, then reverse the order, all while keeping these customers up and running. Because we’re delivering this as a service, it has to always be on.
One of the most important architectural decisions we made from the start was ensuring those two exchange points are always running active-active in a full mesh configuration, buttressed by hundreds of other exchange points globally distributed – all synchronized and aware of each other’s states.
Robert Dutt: You’ve said that legacy networks can’t handle what AI demands, specifically in terms of elasticity. Can you unpack that a little? When an MSP’s customer starts deploying language models or agentic workflows, what is it that actually breaks?
Doug Houghton: Good question, and I’ll give you an honest answer. I’ve started to fall in love with Claude – I think it’s one of the coolest things in the world. I can do all sorts of creative things with it. But Claude isn’t talking only to me. He’s a bit of a flirt – he goes to a lot of different places to get knowledgeable about various things and produce the outcomes I’ve asked for. And those other places are where you run into problems.
I used to say the three biggest AI providers are GCP, AWS, and Azure. That’s still largely true. But the likes of Anthropic and other AI labs are distributing LLM workloads everywhere. Without the right network underneath that, it’s like buying the hottest car and driving it down a pothole-filled road.
What we offer is a high-throughput, low-latency, elastic network. If you need to turn it up in a heartbeat, you can. We helped complete the S&P Global and IHS Markit merger network integration in about a tenth of the time they expected, because we’re natively segmented. Think about those two networks as large datasets that AI agents need to access. You have to secure the traffic, and you need it to be elastic – able to reach anywhere, instantly, to produce the outcome the agent was asked for.
The ability to go anywhere on a road that’s smooth as glass, in the hottest car possible – that’s what we offer. Our network infrastructure solution is an abstraction: a forwarding plane that goes everywhere, and your imagination is really the only limitation. Speed, elasticity, and securing access – even for agentic, self-directed workflows – it’s still a critical element.
And nobody – I said this earlier today, so I’ll say it again – networking is not really sexy until it doesn’t work. If I have to get in and route-peer and manually configure transit gateways, I’m going to punch myself in the face repeatedly. I just don’t want to do it. It slows everything down. I can automate it with Terraform, sure. But I want to consume it now. I want to prompt it now. I want the outcome now.
Robert Dutt: You’ve launched Alkira NIA, your AI co-pilot and network infrastructure assistant, along with an MCP server last year. It’s interesting – you’re essentially putting AI on top of the infrastructure that’s enabling AI. What does NIA actually do for an MSP’s day-to-day operations?
Doug Houghton: Maybe I have a limited imagination, but I still use it like a utility. NIA is great because it allows you to search through all our documentation in a more organized way. We have amazing documentation – there’s a lot of it – and when you’re looking for a specific configuration or something captured in a knowledge base, that tool is really useful.
But continuing the utility theme: how do I do something? If I want to create a micro-segment to distribute to a bunch of business units, or build an isolated Layer 3 routing table and get it to various business units, and then set up billing with specific billing tags for each segment – I know how to do that because I’ve done it many times. But a new user may not. You can use the NIA agent to search the documentation, search previous implementation notes, best practices, all of that.
That’s real value. But you can also ask it something like “why is the sun bright” and it won’t return the answer you expect. I’ve done that too.
Robert Dutt: Let’s talk about the Connect Partner Program and the economics. You’ve got the Partner Profit Stack – tiered margins, quarterly rebates, MDF, SPIFFs, the Connect Pipeline Fund. It’s a full toolkit, and it’s stuff partners have seen before. What’s the real math? What does a Canadian MSP at the Premier tier actually walk away with on a typical deal after they’ve done the work?
Doug Houghton: Usually about nineteen percentage points – maybe a little more. On the pre-sale side, when we get into a POC, our Premier partners can earn a $1,000 SPIFF. We close about 85% of our POCs, so there’s real value in that. Add in the rebates and MDF access, and the total haul is closer to 20% on each deal.
Worth mentioning: we’ve been a 100% channel company since May 2022. My partner David Klubinoff, my technical counterpart – we worked together at Viptela and we started the Alkira channel together. It took a couple of weeks to convince our CEO that going 100% channel was the right call. I think he’s a believer now. We’ve driven significant revenue for the company, and our partners are our thought leaders – out in the market talking about our solution and solving customer problems.
I was in Chicago yesterday doing a technical enablement session with thirty-plus SAs and SEs. We had the classic SD-WAN questions, and a lot of questions about segmentation and M&A. There’s enormous consolidation happening in insurance, healthcare, and other sectors, and the overlapping IP address problem that comes with mergers is something MSPs face all the time. We’ve entirely simplified that. You build a NAT policy right in the solution and the overlapping IP issue is resolved within an hour.
In the case of S&P Global and IHS Markit, they thought their merger network integration was going to take a couple of years. The issue was largely the overlapping IP addresses – IHS couldn’t talk to the HR applications at S&P, and vice versa, plus all the other interdependencies. You need a fast way to solve the overlapping IP problem before you can even get to the real work. That’s been a core design element of our solution from the very start: take care of the small things, and people can move faster and get to market faster.
Our biggest MSP – and this is a publicly referenceable customer – is CEDA, a French-based organization that provides managed network services to 95% of the world’s airlines. For them, it means being able to turn up a new customer faster, connecting on-premises assets to their control elements so they can begin actually managing that network. Speed, and the efficiencies and cost reductions that come from it – that’s what it does for all MSPs. If you’re consolidating fifty firewalls into virtualized functions, you’re making a good commission, getting MDF support, quarterly rebates, and a SPIFF when you engage us collaboratively on a POC. All of that happens at an accelerated rate.
I’ve been screaming from the mountaintop about our solution for about four years. Invariably, you’d walk into a room, say “Hi, I’m Doug Houghton from Alkira,” and they’d say “Who?” That’s starting to happen a lot less, which is a genuinely nice thing. Over the last twelve to twenty-four months, the business has grown exponentially, the diversity of our partner ecosystem has increased, and partner margins have been very healthy. The tiered structure was really about celebrating partners who have invested in us.
Honestly, I’m waiting for the day my boss tells me to stop incentivizing partners – because when that happens, I’ll know we’ve hit the apex. Our partners will be generating so much revenue that someone gets uncomfortable with what we’re paying out. I can’t wait for that day.
Some of the more interesting things in the program came from actually listening. I went around and talked to a bunch of partners about their ideal partner programs and built from there. And one of the realizations – I thought it was significant – was what we were actually doing on the post-sale side. We white-glove every implementation right now, because it’s critically important to us. We haven’t lost a customer, and we intend to keep it that way. But that doesn’t scale forever.
So the question became: why don’t we help our partners productize the post-sale work? We built a product catalog, a pricing calculator, and a new partner portal we’re about to release, with its own AI agent for searching market assets. The product catalog was a light bulb moment. We pay healthy margins on the pre-sale side at every tier of Alkira Connect. But we had never touched the post-sale side at all.
We’re largely automated and NIaaS is as simple as possible to consume – a username and a password. My thirteen-year-old could configure a network, and she’s really smart. But there’s still some implementation work. You still need to build policies in Panorama. There’s still DDI work. There are still services that partners can benefit from – and all partner types, MSPs, VARs, master agents, sub-agents, service providers, now have a post-sale commission opportunity.
Robert Dutt: You mentioned services – you’ve got services attach plays around modernization assessments, segmentation design, migration sprints. Starting from zero, how long does it realistically take a partner to get their first deal with those services attached through the door, and what does the ramp look like?
Doug Houghton: There’s a lot in that question. Let’s take a half step back. We have virtual sales and go-to-market training – three modules – and then five or six technical training modules. We’ve got a lab-in-a-box environment, foundational and advanced technical training, and DDI training. Partners typically start there. Then we run regular in-person and virtual sessions – one partner has regular office hours with me, my SE counterpart David, or our architect Christopher Arenas, and we just invite partners to come and ask questions. Getting partners genuinely comfortable with the technology is the most important thing we do, because nobody goes out and sells anything unless they’re confident they can explain how Alkira solves their customer’s problem. That’s what I’m doing in Chicago today.
Our customers tend to be fairly large. We’ve got our first Fortune 10 customer now. The more complex the network, the larger and more global the deployment – multiple countries, security vendors, firewalls, DDI providers, load balancers, service providers, colos. We sit right on top of all of that.
The average sales cycle is about 190 days – a little over six months. A newly enabled partner might encounter an M&A overlapping IP use case, recognize the problem, and say “I think we can solve this with Alkira.” They go through a POC together with us, the customer commits, and that first deal closes around 190 days. A little class week: it’s actually 190 and a half.
The average deal size is about $500,000 USD. We then see significant expansion: typically 4x growth in the first twelve months after the initial close, and around 8x in the second twelve months. Real incentive to stick with it. We’re loyal – if the customer doesn’t kick the partner out, we go to bat with that partner on every expansion deal. We land, then expand, with the same partner. BNSF, one of our other public references, has expanded several times to address more and more use cases. The solution gets sticky and customers are genuinely surprised by how easy it is.
On the post-sale side, we come in and help with implementation, especially early on. But we’re reaching the point where more capable partners can handle it themselves. We’re building a post-sale certification for Alkira right now. In the meantime, we ride shotgun through the first couple of implementations – virtually in Slack or in person – until partners are fully up to speed.
All partners have access to our Slack channel, along with our entire solutions architecture and SE staff. One partner working on a Fortune 10 engagement has a great habit of putting a subject header in Slack and starting a conversation. He’s been on services at this customer for three or four months – a significant engagement. He’s the one who originally described the network as a “spaghetti mess,” which I still chuckle about. I actually built the product catalog based on those Slack headers – pulled them together, socialized them with a group of partners, got input, and built from there.
To directly answer your question: you’ve got to get through that first deal, and we’re going to ride shotgun with you through the first couple of implementations. The partner learns, gets comfortable, can monetize it, and can deliver independently from there. We have no illusions about going back to being a direct company after May 2022. It’s ride or die – 100% channel, and we enable our partners to solve their customers’ problems and support them while they do it. Because our partners have been our biggest growth engine.
Robert Dutt: You’ve talked about a goal of doubling revenue through partners. What does the ecosystem look like when you get there? This sounds like it could primarily be a GSI or large integrator play, given the customer complexity you’re describing. Or do you genuinely see a path for mid-market MSPs and VARs to build a meaningful NIaaS practice?
Doug Houghton: Another tough question. Yes, I do have GSIs as partners. We have a fairly robust and diverse partner ecosystem, and we see small shops rising up while larger shops are moving a bit more slowly, honestly. We’re still in that brand awareness honeymoon period – people are realizing our technology is compelling, getting themselves enabled. Some large partners we’ve recently brought on are still ramping. The biggest and most established organizations aren’t yet as capable as they will be, but we’re working diligently on that.
Some of our smaller partners, on the other hand – I’m thinking of a friend of mine in Utah who is just an absolute champion. He knows our solution better than almost anyone. He closed six or seven deals in the past year, supported the implementations, did it largely on his own, because he’s curious, motivated, read all the documentation, and has been through full implementation cycles with us. He works at a ten-person shop. They just happen to have really good customers, and he knows the solution cold.
So we’re at different stages with different partners in terms of maturity. The answer to your question is genuinely both. The small shop in Utah and the large national partner dedicating more resources as they see more customer problems Alkira can solve – we see wins across both. In the networking space, a six-month sales cycle is about as fast as it gets. I’m giving you a username and a password and you’re going in and connecting all of a customer’s assets together. The path exists for partners of every size.
Robert Dutt: You’ve called out Canada specifically in your expansion plans, alongside the UK, EU, and the Middle East. What does that look like operationally – localized support, a Canadian channel team – or is it more of a global platform available to Canadian partners?
Doug Houghton: Let’s talk personnel. We have a dedicated rep in eastern Canada, based out of New Hampshire, and a brilliant solutions architect just outside of Toronto. We’ve got a channel account manager – very capable teammate of mine, Savannah Stone – and the entire global solutions architecture staff accessible via Slack.
We recently closed a very significant logo in Canada – a large insurance company – and our publicly referenceable Canadian customer is ContactPoint 360, a contact centre and BPO provider. They wanted to connect their Latin American operations back to Canada and couldn’t find an effective way to do it without us. We route them through the US West region, and the results have been excellent. We’ve also added CDW Canada as a partner, and I’ve got a value-added distributor that helps with field events.
It’s not a massive footprint yet – it’s a bit of “they come first, then we build” – but there is a tremendous amount of opportunity in Canada and in Latin America that I’m genuinely excited about. Nobody’s told me no yet on spending budget, so here we go.
A great story on the Canadian side: a gentleman named Chris Thelosinos, an architect and consultant who works with others in our space, is a member at a wine shop in Toronto. During the Toronto International Film Festival last year, we hosted a wine event right next to TIFF. I don’t drink alcohol, so it was entirely about the conversations for me – and I had the best time. We had significant customers come out, and the demand for simplicity, ease of implementation, and everything Alkira does well was just as strong in Canada as anywhere else. The market need is real.
We talk about global backbone as a service all the time. Connecting China to San Francisco carries a distance and time tax, but it’s easy to configure. For organizations navigating geopolitical complexity around China access, or needing GPU connectivity in and out, we just abstract the Azure and AWS mainland China instances. They operate the same way as their Canadian or US equivalents. And you can consume it pay-as-you-go – stop using it, stop paying for it. That’s a compelling model for MSPs looking to grow into different regions.
Robert Dutt: Last question then. For that Canadian MSP who’s listened to this and is thinking, “This sounds like a real opportunity” – what’s the one thing you’d want them to take away and act on?
Doug Houghton: I’d ask them to go to [email protected] and send us a note. And I will ply them with all sorts of content – videos, learnings, deal registration information, everything they need to get started in the space.
Tongue in cheek, and also completely seriously: [email protected]. If you’re looking to grow your business as a managed service provider – managed network, managed security, managed load balancing, managed DDI, managed connectivity – we’re a really great place to start. Because it’s never unpopular to walk into a customer and solve their problem quickly and say, “I can help you with X, Y, and Z, and I can do it in the next couple of hours – and that’s going to drive a total cost of ownership savings of 40 to 70%.” Nobody ever kicks you out of the office when you say something like that.
Robert Dutt: Amazing. Doug, I appreciate you taking the time. Thank you very much.
Doug Houghton: Robert, thank you for the engaging conversation. I hope your listeners get some good stuff out of it.
Robert Dutt: There you have it – Doug Houghton from Alkira.
I’d like to thank Doug for his time, and honestly for being one of the more entertaining guests I’ve had on in a while. “Networking is not sexy until it doesn’t work” is a line I’m going to be thinking about for a while.
Thanks to you for listening as well. If this conversation sparked something – whether it’s curiosity about NIaaS, the AI infrastructure angle, or what roughly 20% total margin on a $500,000 average deal could do for your business – Doug made it easy for you to take the next step. Drop a note to [email protected]. That’s the front door. And from what I heard today, they will absolutely get back to you.
Here’s the thing that stuck with me most in this conversation: the argument that the AI moment isn’t just a software or services play. It’s going to force a reckoning with network infrastructure that a lot of organizations have been deferring for years. The partners who treat that reckoning as an opportunity rather than a fire drill are probably going to look very smart in about three years.
If you’re finding the In The Channel podcast from ChannelBuzz.ca useful, the best thing you can do is follow or subscribe wherever you get your podcasts. We’re on Apple Podcasts, Spotify, YouTube, and most major directories. And if you’re enjoying the show, ratings and reviews are genuinely appreciated – they help other people in the Canadian channel find us.
Until next time, I’m Robert Dutt for ChannelBuzz.ca, and I’ll see you in the channel.