Sep 30, 2026 · 50 min · 12 segments
Deploying AI at the edge is no longer limited to organisations with vast engineering teams and multimillion-pound budgets. In this episode, Nick Earle speaks with Neil Cresswell, Co-founder and CEO of…
Nick EarleHost
Neil CresswellGuest
Well, it's more the promises to the new model, as you pointed out, but two questions here.

One is, presumably, it makes scaling to hundreds, thousands, potentially millions of devices so much easier because it's more consistent.

So I assume one of the benefits is Scaling deployment, security patching, making sure you've got consistent compliance, device lifecycle management.

Are they the sorts of things that are benefits? But they really become benefits because when we're talking IoT, we're talking millions.

So is that one of the reasons why these two technologies, IoT as a use case at the edge and containers for the software at the edge are natural bedfellows, so to speak, because of the fact that you can set a framework for all of those things and then do mass deployment scaling?

Yeah, when you learn the inner workings of a software container and how an image is constructed, like an image is basically just a zip of files and a bunch of configs on top of it, right? And so the software creator, so the vendor or an internal developer, creates the software package, creates an image, which bundles it up into an image file, which is then hosted centrally somewhere, and then devices out in the field, when they are commanded to go and run the container, they seek the image, pull the image, and then extract it and run it.

Every single device in the field, hundreds, thousands, millions of them, all refer back to the one base image.

Now, what's really cool is the software vendor says, oh my goodness, there's a bug, I'm going to push a new version.

Assuming these devices have the right control software, they will then detect there's a new version of the image and then immediately update themselves over the year by pulling the updates or the changes to the image and then deploy and go.

Because you might have 100 or 1,000 servers, and let's say you're a large enterprise and you've got 50,000 servers.

The benefits of this mechanism in a data center is X, but the benefits of the same technology deployed at the far edge is probably 100 times X.

That's what I think has rapidly accelerated the use of containers at the far edge.


Well, it's more the promises to the new model, as you pointed out, but two questions here.

One is, presumably, it makes scaling to hundreds, thousands, potentially millions of devices so much easier because it's more consistent.

So I assume one of the benefits is Scaling deployment, security patching, making sure you've got consistent compliance, device lifecycle management.

Are they the sorts of things that are benefits? But they really become benefits because when we're talking IoT, we're talking millions.

So is that one of the reasons why these two technologies, IoT as a use case at the edge and containers for the software at the edge are natural bedfellows, so to speak, because of the fact that you can set a framework for all of those things and then do mass deployment scaling?

Yeah, when you learn the inner workings of a software container and how an image is constructed, like an image is basically just a zip of files and a bunch of configs on top of it, right? And so the software creator, so the vendor or an internal developer, creates the software package, creates an image, which bundles it up into an image file, which is then hosted centrally somewhere, and then devices out in the field, when they are commanded to go and run the container, they seek the image, pull the image, and then extract it and run it.

Every single device in the field, hundreds, thousands, millions of them, all refer back to the one base image.

Now, what's really cool is the software vendor says, oh my goodness, there's a bug, I'm going to push a new version.

Assuming these devices have the right control software, they will then detect there's a new version of the image and then immediately update themselves over the year by pulling the updates or the changes to the image and then deploy and go.

Because you might have 100 or 1,000 servers, and let's say you're a large enterprise and you've got 50,000 servers.

The benefits of this mechanism in a data center is X, but the benefits of the same technology deployed at the far edge is probably 100 times X.

That's what I think has rapidly accelerated the use of containers at the far edge.

The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.