Key takeaway
- AI edge analytics runs models on or near sensors and devices. See how it works, how Azure IoT Edge and AWS IoT Greengrass do it, and how to start.
AI edge analytics is the practice of running analytics and machine learning models on or near the devices that generate data, such as sensors, gateways and local servers, instead of sending all raw data to the cloud first. Decisions happen close to the source, and only the useful results travel onward.
This guide is for architects, IoT leads and operations teams deciding what to run at the edge and what to keep in the cloud. It covers how edge analytics works, what the main platforms provide, the trade-offs, and where AI agents fit. For the wider picture, see artificial intelligence with edge computing and the overview of edge analytics platforms and tools.
Why does edge analytics matter?
Sending every reading to a central cloud adds delay, uses bandwidth and fails when the connection does. Processing locally addresses all three. Microsoft's Azure IoT Edge documentation describes bringing analytics closer to devices for faster insights and offline decision-making, and gives two examples: running anomaly detection at the edge to respond quickly to emergencies on a production line, and cleaning and aggregating data locally so that only the insights are sent to the cloud.
How does AI work at the edge?
The pattern is usually the same across vendors. A model is trained where compute is plentiful, packaged, and deployed to devices that run it against local data. The device acts on the result, sends a summary upstream, and receives updates from the cloud.
The Azure IoT Edge page describes three parts: modules, which are containers that run Azure services, third-party services or your own code on the device; a runtime on each device that installs and updates modules and reports their health; and a cloud interface to monitor and manage devices remotely. Modules can pass data to one another to form a processing pipeline, and the page notes that machine learning, image recognition and complex event processing can be deployed directly at the edge.
The AWS IoT Greengrass documentation describes an open source edge runtime and cloud service for building, deploying and managing IoT applications. It says devices can act locally on the data they generate, run predictions from machine learning models, and filter and aggregate device data. Applications are built from components and can run as Lambda functions, Docker containers, native processes or custom runtimes. The same page notes that AWS ended support for Greengrass Version 1 on 7 October 2026, so new projects should target the current version.
How do edge, cloud and hybrid designs compare?
| Question | Edge | Cloud | Hybrid |
|---|---|---|---|
| Where does inference run? | On or near the device | In a central region | Edge for fast decisions, cloud for heavy work |
| What happens offline? | Local processing can continue | Processing waits for the link | Edge continues, cloud syncs later |
| What data leaves the site? | Summaries and exceptions | Raw data | Summaries by default, raw data by exception |
| What is harder? | Managing many devices and updates | Latency and bandwidth | Keeping models and policy consistent |
Most real deployments are hybrid. The practical question is which decisions need a local answer, and the usual candidates are those where delay, bandwidth or connectivity matters. Related reading includes real-time decision-making and predictive analytics.
Where is edge analytics used?
The common fit is any site with sensors and a need for fast local action. Examples include equipment monitoring on production lines, as in the Azure documentation, and store operations, covered in Edge AI in retail. Healthcare, city infrastructure and agriculture follow the same pattern: collect locally, decide locally, report centrally. XenonStack's edge AI and vision AI solutions page covers these areas in more detail.
What are the main challenges?
- Fleet management: updating models and software across many devices, which both platforms address with cloud-side deployment and monitoring.
- Data governance: deciding what stays local, what is sent, and who can see it. See modern data governance.
- Model quality at the edge: smaller models on limited hardware need testing against local conditions. AI models differ widely in size and cost.
- Security: devices sit outside the data centre, so identity, updates and network paths need explicit design.
- Learning without centralising data: approaches such as federated learning, and in some designs blockchain for audit trails, are being explored. Connectivity such as 5G can also affect where processing is placed.
How do AI agents change this topic?
Edge models detect and classify. AI agents add the next layer: they combine a local detection with context from other systems, decide which action is allowed, and hand over to a person when it is not. That needs inference close to the data and clear limits on what each agent may do. XenonStack's NexaStack is inference infrastructure for edge, vision and robotics workloads. The IoT edge analytics and trends guide gives further background.
What should you do first?
- List the decisions that must be made in seconds or without a connection.
- Pick one device type and one model, and measure accuracy on local data.
- Choose a runtime and plan how updates and rollbacks will work.
- Define what data stays on site and what is sent, with an owner for each rule.
- Pilot at one site before scaling. For help, contact us or talk to a specialist.
To map one decision your agents make, and the data and policy it depends on, book a Context Workshop. See what happens in the workshop.
Next Steps for AI Edge Analytics Implementation
Talk to our experts about implementing AI Edge Analytics systems. Learn how industries and different departments utilize AI-powered edge analytics to enhance decision-making, optimize workflows, and drive real-time insights. Leverage AI to automate and improve operational efficiency, ensuring faster and more responsive processes.
Frequently asked questions
What is AI edge analytics?
It is running analytics and machine learning models on or near the devices that generate data, so decisions are made locally and only the useful results are sent to the cloud.
How is edge analytics different from cloud analytics?
Cloud analytics sends data to a central region for processing. Edge analytics processes it on or near the device, which reduces delay and bandwidth use and lets local processing continue without a connection.
Which platforms support edge analytics?
Azure IoT Edge and AWS IoT Greengrass are two documented examples. Both let you deploy and manage code, including machine learning models, on devices from the cloud.
Is AWS IoT Greengrass Version 1 still supported?
No. The AWS documentation says AWS ended support for AWS IoT Greengrass Version 1 on 7 October 2026.
What should stay in the cloud?
Model training, fleet-wide reporting and any work that needs data from many sites usually stays in the cloud, while time-critical decisions run at the edge.
Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.
Ready to put AI agents to work? Explore ElixirClaw, the agentic OS platform to build, orchestrate and govern AI agents.
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