New
What is your approach to managing thousands of edge devices?
Fleet management, updates, security patching and observability at the edge: what tools and practices have held up?
Evaluation guide
How to evaluate edge and IoT platforms
This guide is for IT, operational technology and engineering leaders deploying connected devices or computing outside the data centre, in factories, stores, vehicles, utilities or remote sites. It assumes devices will stay in the field for years and that IT and operations teams both have to sign off.
In short
Use this guide to compare edge and IoT platforms on what decides the outcome: device security and updates over a long life, fleet management at scale, integration with operational technology, offline operation, data ownership and total cost per device or site. Then shortlist three to five companies on Techarda and run a pilot at one real site.
What’s changing in Edge & IoT
Before you compare anyone, it helps to know what has shifted in the market, because it changes which questions matter.
IT and operational technology are converging
Factory and utility systems that were once isolated are now connected to enterprise networks and clouds. That brings analytics and remote management, and exposes systems that were never designed to face attackers.
Device security is becoming regulated
Governments are setting baseline security rules for connected devices, including the UK's product security regime, the EU Cyber Resilience Act and Australia's Cyber Security Act 2024, which provides for mandatory smart device standards. Expect questions about default passwords, updates and vulnerability handling.
AI inference is moving to the edge
Vision and sensor models now run on gateways and devices close to where data is created, cutting latency and bandwidth. Managing models across many devices adds a new kind of fleet work.
Connectivity options have widened
Private 5G, low-power wide-area networks and satellite links have joined Wi-Fi and wired options. The right choice depends on range, power, bandwidth and who operates the network.
What to judge vendors on
Those shifts shape the criteria below. Each one says why it matters and what to ask, so you can take it straight into a vendor call.
| Criterion | Why it matters | What to ask vendors |
|---|---|---|
| 1Device security and updates over a long life | Devices stay in the field for years. A device that cannot be patched securely becomes a permanent weak point. | “How are devices identified and updated securely, for how long will you ship security updates for the models we buy, and how do you handle vulnerability reports?” |
| 2Fleet management at scale | What works for ten devices fails at thousands. Provisioning, monitoring and updates have to run without site visits. | “How do we provision, monitor and update devices in bulk without visiting each site, and what happens to a device that misses an update?” |
| 3Integration with operational technology | Industrial protocols, safety systems and older equipment are where edge projects stall. | “Which industrial protocols and control systems do you support today, and how do you make sure the platform cannot interfere with safety functions?” |
| 4Connectivity and offline operation | Remote sites lose connectivity. Devices and edge applications need to keep working and catch up when the link returns. | “Which connectivity options do you support, what keeps working when a site is offline, and how is data synchronised afterwards?” |
| 5Data ownership and access | Device and operational data can be valuable and sensitive. Who owns it and who may use it should be settled before deployment. | “Who owns the data our devices produce, can we route it directly to our own systems, and does the vendor use it for any purpose of its own?” |
| 6Integration with your IT systems and clouds | Edge data is only useful once it reaches the systems where decisions are made. | “How does data reach our cloud, data platform and business applications, and which of those integrations do you maintain?” |
| 7Total cost per device or site | Hardware is only part of the cost. Connectivity, subscriptions, installation, site visits and replacements add up over the life of a device. | “What is the total cost per device or site over its expected life in the field, including connectivity, subscriptions, support and replacement?” |
| 8Product longevity and exit | If a platform is discontinued, devices tied to its cloud can stop working. | “What happens to our devices if the platform or product line is retired, can other software manage them, and how much notice will you give?” |
Trade-offs to settle early
No vendor does well on every criterion, and some pull against each other. Decide where you stand on these before the demos start, or the demos will decide for you.
Industry solution or general platform
A solution built for your industry comes with the right protocols and dashboards. A general platform can serve many use cases and needs more building.
Cloud-managed or locally managed
Cloud management is simpler across many sites. Local management keeps working when links fail and suits sites with strict security rules.
Process at the edge or in the cloud
Processing at the edge cuts latency and bandwidth, and adds devices to secure and maintain. Central processing is simpler and depends on the link.
One vendor stack or mixed devices
One vendor for devices, connectivity and platform simplifies support. Mixed devices avoid dependence on one supplier and need more integration.
Pilot speed or readiness for rollout
A pilot with a handful of devices proves the use case. Security, fleet management and support at scale decide whether it survives rollout, so test them early.
Red flags
As the answers come back, watch for these. One on its own isn’t a deal breaker, but it deserves a follow-up question in writing.
- No stated period of security updates for the devices you are buying.
- Default passwords or credentials shared across devices.
- Devices that only work with the vendor’s cloud, with no local or alternative management.
- Data terms that let the vendor reuse your operational data.
- No reference customer in your industry whose devices have been in the field for several years.
- Prices quoted per device without connectivity, installation or replacement.
Build your shortlist
Start with the use case and the sites, then use Techarda to narrow the field to three to five companies.
- Describe the use case, the sites, how many devices you expect and the systems the data must reach.
- Bring IT and operational technology security into the first conversation, not the last.
- Keep companies that support your protocols, connectivity and environment in production today.
- Read recent stories on Techarda for product retirements, acquisitions and security advisories, and plan questions around them.
- Pilot at one real site, check the practitioner questions below, then compare side by side.
Companies to consider in Edge & IoT
Listed by recent activity on Techarda (what people are reading, following and discussing). The order says nothing about quality, market share or fit for your needs.
Latest Edge & IoT stories
Once you have names, recent news is where pricing changes, acquisitions and outages show up first. These are the five newest stories in this category.
What practitioners are asking
News tells you what vendors announced. These open questions show what teams are still trying to work out, with the least-answered first.
Where evidence is thin
A shortlist is only as good as the evidence behind it, and ours is still growing category by category. Here is what’s missing in Edge & IoT right now.
20 of 20 companies have no published reviews
If you’ve run one of these in production, a short review helps the next team decide. Reviews are moderated before they appear.
1 question with no answers yet
An answer from someone who has made the same decision is often more useful than any guide. Share what worked, what didn’t and what you’d check next time.
Answer a Edge & IoT questionFrequently asked questions
What should I ask Edge & IoT vendors about device security and updates over a long life?
Devices stay in the field for years. A device that cannot be patched securely becomes a permanent weak point. Ask: How are devices identified and updated securely, for how long will you ship security updates for the models we buy, and how do you handle vulnerability reports?
What should I ask Edge & IoT vendors about fleet management at scale?
What works for ten devices fails at thousands. Provisioning, monitoring and updates have to run without site visits. Ask: How do we provision, monitor and update devices in bulk without visiting each site, and what happens to a device that misses an update?
What should I ask Edge & IoT vendors about data ownership and access?
Device and operational data can be valuable and sensitive. Who owns it and who may use it should be settled before deployment. Ask: Who owns the data our devices produce, can we route it directly to our own systems, and does the vendor use it for any purpose of its own?
What should I ask Edge & IoT vendors about product longevity and exit?
If a platform is discontinued, devices tied to its cloud can stop working. Ask: What happens to our devices if the platform or product line is retired, can other software manage them, and how much notice will you give?
New to some of the terms in this guide? The glossary explains Edge computing, Industrial IoT (IIoT) and Operational technology (OT) security.
This guide is written by Techarda editors to our editorial standards. No vendor paid to appear in it or saw it before publication. See our methodology, the trust dashboard or go back to the Edge & IoT hub.