Key takeaway
- Intelligent edge and edge AI explained for 2027: types, edge vs cloud, platforms, use cases, security, EU Cyber Resilience Act duties and adoption steps.
The intelligent edge is the practice of collecting, analysing and acting on data close to where it is created: on sensors, cameras, machines, gateways and local servers, instead of sending every reading to a central cloud first. AI models running at those sites detect events and trigger actions in milliseconds, while only filtered results, exceptions and model updates travel to and from the cloud.
For enterprise leaders, the question is no longer whether edge computing works but where it earns its keep. This guide covers the types of intelligent edge, how it differs from cloud computing, the platforms that matter in 2026, what has changed recently (including platform support dates and new EU reporting duties), use cases by industry, and an adoption sequence with the trade-offs.
What is the intelligent edge?
Intelligent edge describes systems that aggregate and analyse data at or near the point of capture in a network, then act on the result locally. It matters most for distributed estates such as factories, stores, hospitals, energy assets, vehicles and branch offices, where round trips to a central data centre add latency, bandwidth cost and exposure of sensitive data.
A useful way to frame it is the three Cs:
- Connect: devices, people and things join a network, creating new data streams.
- Compute: local systems process those streams, run AI models and reveal what is happening in the device and its surroundings.
- Control: the insight is used to act, for example adjusting a machine, raising an alert or changing a price on a digital shelf label, and to prompt wider business actions.
A retail example: a store connects chilled drinks cabinets and digital price displays. Local analytics track stock and sell-through, combine it with outside temperature and sales at other sites, and adjust prices or replenishment without waiting for a central batch job. Edge AI, meaning machine learning inference running on or near the device, is the compute layer that makes this kind of control possible.
What has changed in intelligent edge since this guide was first written?
The original version of this article quoted a 2025 market forecast and described platforms generically. The current picture, checked against vendor and regulator pages in November 2026, looks like this:
| Area | What has changed | Current status (Nov 2026) |
|---|---|---|
| Azure IoT Edge | Version 1.4 LTS reached end of life on 12 November 2024, and 1.5 LTS support ended on 10 November 2026. | 1.6 is the latest LTS release. Upgrade any remaining 1.5 devices. |
| Azure IoT Operations | Microsoft now offers a unified data plane for the edge on Azure Arc-enabled Kubernetes, with an MQTT broker, connectors and data flows. | Can operate offline for up to 72 hours, then resumes full functionality on reconnection. |
| AWS IoT Greengrass V2 | An open source IoT edge runtime and cloud service to build, deploy and manage device applications, including local ML predictions. | Current; V2 is the documented version. |
| Google Distributed Cloud | Fully managed hardware and software for data centres and edge locations, in connected and air-gapped forms. | Google states Gemini is available on GDC for on-premises generative AI. |
| Edge AI hardware | NVIDIA made Jetson Thor generally available on 25 August 2025, with up to 2,070 FP4 teraflops within a 130-watt envelope. | Developer kit from US$3,499; NVIDIA cites up to 7.5x the AI compute of Jetson Orin. |
| Networks | 3GPP Release 18 brings 5G-Advanced, with AI/ML among its new topics. | Applies as operators roll out 5G-Advanced features. |
| Regulation (EU) | The Cyber Resilience Act covers products with digital elements, including industrial IoT. | Reporting obligations applied from 11 September 2026; product design rules from December 2027. |
What types of intelligent edge are there?
Many enterprises run more than one type. Naming them helps decide who owns each, which platform fits and which security standard applies.
| Type | What it is | When it fits | Typical examples |
|---|---|---|---|
| Operational technology (OT) edge | Controllers and systems that already contain control logic but have historically had limited connectivity and compute | Plants and remote assets where control must keep running without the network | Power plants, offshore platforms, production lines |
| IT or enterprise edge | Local servers or small clusters in branches, campuses and stores | Many sites that need local apps, analytics and resilience | Retail stores, bank branches, hospitals, warehouses |
| IoT or device edge | Applications deployed to IoT edge-enabled devices and gateways, often combining OT and IT data | High-volume sensor or camera data that should be filtered locally | Smart cameras, vibration sensors, wearables, gateways |
| Network or telco edge | Compute placed in operator networks close to users, such as multi-access edge computing (MEC) | Mobile, low-latency services spread over a wide area | Connected vehicles, venue video, private 5G campuses |
How is intelligent edge different from cloud computing?
The two are complementary. The edge keeps time-critical decisions local; the cloud handles scale, training and cross-site views. For a longer comparison that includes fog computing, see cloud, edge and fog computing compared.
| Decision factor | Favours the edge when | Favours the cloud when |
|---|---|---|
| Latency | Actions are needed in milliseconds, such as stopping a machine or flagging a defect | Seconds or minutes are acceptable |
| Connectivity | Sites are remote, mobile or must keep working offline | Connectivity is reliable and cheap |
| Data volume | Raw video or high-frequency sensor data would be costly to send upstream | Volumes are modest or already aggregated |
| Data residency and privacy | Sensitive data such as patient vitals or video must stay on site | Data can be centralised under existing controls |
| Model training | Rarely; training usually needs pooled data and large compute | Training, retraining and cross-site analytics |
| Operating cost | Savings on bandwidth and downtime outweigh fleet management effort | A single central platform is cheaper to run |
Which technologies and platforms enable the intelligent edge?
An intelligent edge stack has five layers: devices and sensors, connectivity, local compute and storage, AI inference, and the fleet management and governance plane that keeps hundreds or thousands of sites consistent. The platform choice usually follows the cloud estate you already run, then the hardware your AI models need.
| Option | What it is | When it fits |
|---|---|---|
| AWS IoT Greengrass V2 | Open source edge runtime plus cloud service for deploying and managing device software and ML inference | AWS-centric estates with many gateways or devices |
| Azure IoT Edge 1.6 LTS | Microsoft runtime for containerised modules on devices | Existing Azure IoT Hub device fleets |
| Azure IoT Operations | Data plane on Arc-enabled Kubernetes with MQTT broker, connectors and data flows into Microsoft Fabric and Event Hubs | Industrial sites standardising on Kubernetes and Azure |
| Google Distributed Cloud | Managed hardware and software in connected or air-gapped form, with Gemini available on premises | Sovereignty, disconnected operation or on-premises generative AI |
| NVIDIA Jetson (Orin, Thor) | Embedded AI modules for robots, machines and smart cameras | Heavy on-device inference such as vision and robotics |
For a deeper platform comparison, read our review of edge computing platforms. Where edge sites run physical AI such as robots, cameras and machines, NexaStack is an agentic operating platform for physical AI that runs across on-premises, cloud and hybrid environments.
Where does the intelligent edge pay off?
| Industry | Edge use case | Why it runs at the edge |
|---|---|---|
| Manufacturing | Visual quality inspection, predictive maintenance, safety monitoring | Defects and faults must be caught on the line in real time |
| Retail | Shelf and stock monitoring, dynamic pricing, checkout analytics | Hundreds of stores, limited bandwidth, need to keep trading offline |
| Healthcare | Analysis of wearable and bedside device data with early warnings to caregivers | Patient data stays local and alerts cannot wait for a round trip |
| Energy and utilities | Asset monitoring at substations, wind farms and pipelines | Remote sites with intermittent connectivity |
| Transport and autonomous systems | Perception and decision making in vehicles, drones and robots | Safety decisions need millisecond responses |
| Public spaces and security | Camera analytics for incidents, crowd flow and safety equipment | Streaming all raw video centrally is costly and raises privacy concerns |
Video analytics is one of the clearest examples: each camera, or a nearby server, can act as an agent that interprets the scene and raises only meaningful events.
Video: how camera feeds become agents that act on events at the edge (XenonStack AI).
How do governance, security and cost fit into an intelligent edge programme?
- Security: edge devices are physically exposed and widely distributed. Industrial sites commonly align with the ISA/IEC 62443 series, which addresses the security of industrial automation and control systems. Use signed updates, device identity and least-privilege access by default.
- Regulation: manufacturers and suppliers of connected products sold in the EU now carry Cyber Resilience Act reporting duties, so supplier contracts and vulnerability handling need to reflect them.
- Data governance: decide what is processed, retained and discarded at each site, and how that is evidenced. Our guide to edge data management covers this in detail.
- AI governance: models making local decisions need versioning, monitoring for drift and a record of what was decided and why. AgentGRC keeps autonomous agent actions inside policy, with the audit trail risk teams need.
- Cost: bandwidth savings are real, but so are hardware refreshes, site visits and fleet tooling. Model the full lifecycle cost per site, not only the cloud bill avoided.
In what order should you adopt the intelligent edge?
- Pick one decision that needs to be local. Start from a latency, connectivity or privacy constraint, not from the technology.
- Map the data path. Define what is captured, what is filtered at the edge and what goes upstream.
- Choose the platform from your existing estate. Align with the cloud and device management you already run, and confirm support dates.
- Pilot at two or three sites. Measure response time, bandwidth, uptime and the business outcome.
- Build the fleet plane before scaling. Automate deployment, updates, monitoring and rollback for devices and models.
- Add governance and evidence. Record model versions, policies and decisions so audits and incident reports can be answered quickly.
- Scale by site template. Roll out a repeatable site design rather than bespoke builds.
For agent-based edge designs, see edge AI with agentic AI for distributed intelligence.
What are the trade-offs, and when is the intelligent edge not the answer?
| Trade-off | What it means in practice |
|---|---|
| Fleet complexity | Every site adds hardware, patching and monitoring; scale magnifies small inconsistencies |
| Limited local compute | Models may need to be compressed or quantised to fit device power and memory |
| Interoperability | Devices and protocols from multiple vendors need connectors and common data models |
| Skills | Teams need networking, OT security, MLOps and data skills together |
| Physical risk | Devices can be tampered with or stolen, so encryption and secure boot matter |
Skip the edge when latency is not critical, connectivity is reliable, data volumes are modest and there are no residency constraints. In those cases a cloud-only design is usually simpler and cheaper to operate.
What should leaders take away?
The intelligent edge is now a mature, hybrid pattern: local inference and control at the site, training and oversight in the cloud. The platforms have moved on, with Azure IoT Edge 1.5 out of support, Kubernetes-based data planes and powerful on-device AI hardware, and EU reporting duties for connected products now apply. Start with one decision that must be local, prove it at a few sites, and invest in fleet management and governance before scaling. To orchestrate and govern the agents that act on edge data while keeping humans in control, teams can use ElixirClaw.
To map one edge decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.
What should you plan for in 2027?
One regulatory date falls in 2027 for anyone building or buying connected edge devices for the EU market, and it affects hardware choices made today.
- Full application: the European Commission lists 11 December 2027 as the date of full application of the Cyber Resilience Act, after reporting obligations began on 11 September 2026.
- Design rules: Ireland's NCSC describes full technical product compliance rules as applying from December 2027, so device roadmaps, supplier contracts and vulnerability handling should be ready before then.
Frequently asked questions about the intelligent edge
What is the intelligent edge in simple terms?
It is the practice of collecting, analysing and acting on data close to where it is created, on devices, gateways or local servers, instead of sending everything to a central cloud first. AI models running at those sites make or support decisions in milliseconds, and only useful results go upstream.
Is intelligent edge the same as edge AI?
Not quite. Edge AI means running machine learning inference on or near the device. The intelligent edge is the wider operating model: connectivity, local compute, AI inference, local control actions and the fleet management, security and governance that keep many sites consistent.
Does intelligent edge replace the cloud?
No. Enterprise designs are usually hybrid. The edge handles time-critical inference, filtering and local control, while the cloud handles model training, fleet management, long-term storage and cross-site analytics.
Which platforms are used to run intelligent edge workloads going into 2027?
Common choices include AWS IoT Greengrass V2, Azure IoT Edge 1.6 LTS and Azure IoT Operations on Azure Arc-enabled Kubernetes, Google Distributed Cloud for connected or air-gapped sites, and NVIDIA Jetson modules such as Jetson Thor for on-device AI.
What regulations affect intelligent edge devices?
In the EU, the Cyber Resilience Act covers connected hardware and software. Its vulnerability and incident reporting obligations have applied since 11 September 2026, and its product design rules apply from December 2027. Industrial sites also commonly align with the ISA/IEC 62443 series for industrial control system security.
When should an enterprise not use the intelligent edge?
When latency is not critical, connectivity is reliable, data volumes are modest and there are no residency constraints, a cloud-only design is usually simpler and cheaper to run than a fleet of edge sites.
Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.
Explore the XenonStack platform family: ElixirData · ElixirClaw · ElixirHub · NexaStack · MetaSecure · Neural AI · AgentGRC · AgentSRE · AgentAnalyst · AgentInstruct · AgentRAI · AgentScrum · AgentSearch · AgentForce · AI Aviator · SAIF Aviator · CohortIQ · XenonStack AI · XenonStack UAE