Akash

AI agent startup funding October 2026

AI Agent Startup Funding October 2026: 10 Biggest Rounds

AI Agent Startup Funding October 2026: 10 Biggest Rounds AI agent startup funding October 2026 has already passed $1.8 billion across the ten biggest disclosed rounds, led by Legora’s $550 million Series E. IoT Insights Hub tracks every major deal, who raised, which investors led, and what the money means for connected and industrial systems. Key Takeaways AI agent startup funding October 2026: the ten largest disclosed rounds add up to more than $1.8 billion through October 26, by IoT Insights Hub’s tally of company and press reports. Legora’s $550 million Series E at an $8.8 billion valuation (announced October 21) is the largest. Manus, at more than $500 million, is second. Five of the ten rounds carry disclosed valuations of $1 billion or more. Agent security is now its own category: Armadin, Rein Security and Opsin raised $301.5 million combined. For IoT and industrial teams, the signal is practical: agents are heading toward connected systems, so identity, permissions and edge compute come first. AI October 26, 2026 9 min read By IoT Insights Hub Editorial Team AI agent startup funding October 2026 is running hot, and the month is not over yet. By October 26, the ten largest disclosed rounds had added up to more than $1.8 billion. That figure comes from IoT Insights Hub’s own tally of company announcements and press reports, so treat it as a floor, not a final count. Here is the short version. Legal, planning and mortgage agents pulled in the biggest cheques. Security startups built to watch other agents raised $301.5 million. Infrastructure for running agents reached unicorn status. Below, IoT Insights Hub walks through every round, the investors behind them, and what it means if you build or run connected systems. In this article Which AI agent startups raised the most money in October 2026? Why did Legora, Manus, Armadin and Pigment get the biggest cheques? Which investors are backing AI agent startups right now? What does AI agent startup funding October 2026 say about where agents go next? What does this mean for IoT and industrial teams? What do critics say about the AI agent funding boom? What do readers ask about AI agent startup funding October 2026? $1.8B+Ten largest rounds, Oct 1 to 26 (IoT Insights Hub tally) $550MLegora, the biggest round (company announcement) 5 of 10Rounds at $1B or higher valuations $301.5MRaised by three agent security startups Which AI agent startups raised the most money in October 2026? Short answer: Legora raised the most, at $550 million, followed by Manus at more than $500 million, Armadin at $255.5 million and Pigment at $250 million. Town, Daytona, Vesta, Flai, Rein Security and Opsin complete the top ten. Together the ten rounds total more than $1.8 billion, based on announcements made between October 1 and October 26, 2026. The 10 biggest AI agent funding rounds of October 2026 (as of October 26) # Company Round and date Valuation Led by / notable backers What the agents do Source 1 Legora $550M Series E, Oct 21 $8.8B post-money Atreides Management led; Accel, Benchmark, ICONIQ and others returned Legal work for law firms and in-house teams Legora; The Next Web 2 Manus (Butterfly Effect) More than $500M, Oct 8 Not disclosed Boyu Capital and IDG Capital co-led; Tencent, HSG, ZhenFund General-purpose agent for multistep tasks TechCrunch; CNBC 3 Armadin $255.5M Series B, Oct 1 Above $2.5B Ballistic Ventures among backers Agent swarms that attack networks to expose weak points SiliconANGLE; SecurityWeek 4 Pigment $250M Series E, Oct 21 $2.3B EQT-managed Scaleup Europe Fund led; Greenoaks, ICONIQ, IVP, Meritech Agents that build and run business plans i-scoop 5 Town $108M Series B, Oct 19 $1B Forerunner Ventures and Menlo Ventures co-led; Andreessen Horowitz, First Round Work assistants that hand tasks to one another TechCrunch; The Next Web 6 Daytona $60M Series B, Oct 20 $1B FirstMark led Sandboxed cloud where agents run code Fortune 7 Vesta $30M, Oct 8 Not disclosed Conversion Capital led; Andreessen Horowitz, Citi Ventures Agents for mortgage origination TechCrunch 8 Flai $27M Series A, Oct 6 Not disclosed Base10 Partners led; First Round, Toyota Ventures Phone, email and text agents for car dealerships TechCrunch 9 Rein Security $25M Series A, Oct 8 Not disclosed Glilot Capital and Sienna Venture Capital co-led Runtime security for enterprise AI agents SecurityWeek; PR Newswire 10 Opsin $21M, mid-October Not disclosed SYN Ventures and Race Capital co-led Governance and risk monitoring for enterprise agents FinTech Global Amounts are as announced. “More than” means the company gave a floor, not an exact figure. Valuations are post-money where the company said so. How IoT Insights Hub built this list: we counted rounds announced between October 1 and October 26, 2026, where the company markets AI agents as its core product and the amount was disclosed. Smaller rounds fell below the cut. For last month’s picture, read The Business Perspective’s AI agent startup funding September 2026 report and the September edition on IoT Mail Bridge. We will refresh this page once October closes. Why did Legora, Manus, Armadin and Pigment get the biggest cheques? Short answer: Most pair fast revenue growth or a proven founder with a clear enterprise use case. Legora reports more than $200 million in annual recurring revenue, Pigment reports more than $100 million, and Armadin is led by Mandiant founder Kevin Mandia. Manus is the exception: its round signals investor confidence after Meta’s acquisition was unwound. Legora: legal agents with fast revenue Legora announced a $550 million Series E on October 21, led by Atreides Management at an $8.8 billion post-money valuation, per the company. That is about 57% above the $5.6 billion it was worth roughly six months earlier, according to Startbase. Legora says its annual recurring revenue now tops $200 million and that more than half of the AmLaw 50 are customers. Those are company figures, not audited ones. Manus: a vote of confidence after the Meta unwind Manus is the odd one out. Its parent, Butterfly Effect, said on October…

Read Full News
cyber resilience act iot

Cyber Resilience Act IoT: 7 Must-Know Duties for Makers

Key Takeaways The Cyber Resilience Act IoT reporting rules began on 11 September 2026. Per the European Commission, makers must now report actively exploited vulnerabilities and severe incidents. The clock is short: an early warning within 24 hours, a notification within 72 hours, then a final report. Reports go through ENISA’s Single Reporting Platform. The main obligations, including CE marking and secure-by-design duties, apply from 11 December 2027. The Act entered into force on 10 December 2024. The top fine tier is up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher (Article 64). Micro and small firms get a carve-out for the 24-hour deadline only. Support devices for at least five years, or the expected use time if shorter. Critics worry about pre-patch disclosure and open-source burdens, and a 2026 survey found 66% of 843 organisations unfamiliar with the Act. IoTOctober 23, 202613 min readBy IoT Insights Hub Editorial Team Cyber Resilience Act IoT: 7 Must-Know Duties for Makers Cyber Resilience Act IoT rules stopped being a future problem on 11 September 2026. From that day, anyone selling a connected product in the EU has had to report actively exploited vulnerabilities and severe incidents, and the first deadline is 24 hours. This guide from IoT Insights Hub sets out what the Act covers, the dates that matter, seven duties for makers, the reporting clock, the fines and the criticism. We read the Commission’s pages and the regulation text, and we say where a source is commentary or a news report. Not legal advice, just a plain-English map. Already building secure devices? Our guide to IoT security risks and how to fix them covers the technical side. In this guide What does the Cyber Resilience Act IoT rule set cover? When do the Cyber Resilience Act IoT deadlines apply? What are the 7 Cyber Resilience Act IoT duties for makers? How does the CRA reporting clock work? What are the penalties under the Cyber Resilience Act? What should IoT makers do this quarter? What do critics say about the Cyber Resilience Act? Cyber Resilience Act FAQs Is your team ready for the Cyber Resilience Act? 24 hoursdeadline for the early warning on an exploited vulnerability (European Commission) 5 yearsminimum support period unless expected use is shorter (Regulation 2024/2847) EUR 15Mtop fine tier, or 2.5% of worldwide turnover if higher (Article 64) 11 Dec 2027date the main obligations apply (European Commission) What does the Cyber Resilience Act IoT rule set cover? The Cyber Resilience Act, Regulation (EU) 2024/2847, sets mandatory cybersecurity rules for “software or hardware products with digital elements” sold in the EU. That covers connected devices such as baby monitors and smart watches, plus apps and programs. Manufacturers must build, maintain and report on security across the product’s life. The European Commission says the duties apply at every stage of the value chain and that national market surveillance authorities enforce them. Compliant products carry the CE marking, and some products of particular cybersecurity relevance need a third-party assessment by a notified body before sale. Who is in scope? Any connectable product sold in the EU, including from makers based elsewhere. TechTimes reports that non-EU manufacturers are covered and must name an authorised EU representative, which fits Article 64, since it lists authorised representatives among the roles that can be fined. The same report says reporting also reaches products already on the market, a point a commentary site, cyberresilienceact.eu, ties to Article 69(3). The Commission published non-binding guidance on 27 July 2026, with 67 practical examples, flowcharts and graphs. It explains when remote data processing and free and open source software fall in scope, what counts as a “substantial modification” and how support periods work. It pays particular attention to microenterprises and SMEs. For a wider picture of what these devices do, see our beginner guide to IoT. For the wired industrial side, where exposed controllers raise similar worries, read what is Modbus. When do the Cyber Resilience Act IoT deadlines apply? The Act entered into force on 10 December 2024. Reporting obligations began on 11 September 2026, and the main obligations, including secure-by-design duties, CE marking and conformity assessment, apply from 11 December 2027. The Commission published practical guidance on 27 July 2026 to help manufacturers prepare. Date What happened or applies Source 10 Dec 2024 Act entered into force European Commission 11 Dec 2025 Delegated act adopted on when a CSIRT may delay passing on notifications European Commission 27 Jul 2026 Non-binding practical guidance published European Commission 11 Sep 2026 Reporting obligations began European Commission 11 Dec 2026 Member States should strive to have enough notified bodies by this date (Article 35) Regulation text, via cyberresilienceact.eu 11 Dec 2027 Main obligations apply European Commission One small trap. Wikipedia lists the entry into force as 12 November 2024, while the Commission and EUR-Lex metadata say 10 December 2024. We use the Commission date, and Wikipedia itself flags parts of that page as needing updates. The gap between 2026 and 2027 is where many teams will slip. Reporting is live now, but the design, documentation and conformity work has a year left. In IoT Insights Hub’s view, treating the first date as a dress rehearsal for the second is the safest reading. The Cyber Resilience Act at a glance: key dates, products covered, maker duties and enforcement. What are the 7 Cyber Resilience Act IoT duties for makers? The Act does not number its duties, so this list is IoT Insights Hub’s grouping of Articles 13 and 14: design security in, vet third-party components, handle vulnerabilities, support devices for five years, report exploited flaws, keep documentation including an SBOM, and complete CE marking and conformity steps. Each duty below comes from the regulation text as reproduced by Springlex and cyberresilienceact.eu, checked against the Commission’s pages. Paragraph numbers differ between those two reproductions, so confirm exact wording on EUR-Lex before citing it. Design security in from the start. Article 13 says products must be designed, developed…

Read Full News
IoT Protocols_ Connected Workshop Innovations

IoT Protocols: 7 Best Options Compared for 2026 Projects

IoT BasicsOctober 16, 202611 min read IoT Protocols: 7 Best Options Compared for 2026 Projects By IoT Insights Hub Editorial Team Key Takeaways IoT protocols come in two layers. MQTT, CoAP and HTTP shape messages. LoRaWAN, NB-IoT, Zigbee and Bluetooth LE shape the radio link. MQTT is an OASIS standard (v5.0 approved 7 March 2019) with three delivery levels, per OASIS. CoAP is RFC 7252 (June 2014) and runs over UDP for very small devices, per the IETF. Range and battery figures are mostly claims. The LoRa Alliance cites up to 15 km rural, and GSMA says NB-IoT can support 10+ years of battery life. Most projects mix protocols. Pick by range, power and data size, then test on site. Ask five engineers which of the IoT protocols is best, and you will get six answers. That is not because they are confused. It is because the question is incomplete. IoT protocols do different jobs, and comparing MQTT to LoRaWAN is a bit like comparing a courier to a road. Here is the plain version. This guide compares seven widely used IoT protocols, shows what each is good at, and flags where the claims come from the vendors themselves. At IoT Insights Hub, we would rather you pick a protocol you can test than one that merely sounds modern. In this article What they are The 7 compared MQTT, CoAP, HTTP LoRaWAN, NB-IoT, Zigbee, BLE How to choose What critics say FAQs Bottom line 5B+Bluetooth products shipped each year, per the Bluetooth SIG 1B+Zigbee devices deployed, per the Connectivity Standards Alliance 15 kmLoRaWAN rural range claimed by the LoRa Alliance 10+ yrsbattery life NB-IoT can support, per GSMA What are IoT protocols, and why do they matter? Short answer IoT protocols are the agreed rules that let devices send data to each other and to the cloud. They matter because the wrong choice drains batteries, drops messages or locks you into one vendor. The right choice fits your range, power budget and data size. New to the basics? Start with our guide on what IoT is, in a simple beginner guide. Then come back here to choose between the IoT protocols below. IoT Insights Hub keeps the basics guide and this comparison side by side. Think of two layers of IoT protocols. The first is messaging, meaning how a message is written and delivered. MQTT, CoAP and HTTP live here. The second is the link, meaning how bits travel through the air. LoRaWAN, NB-IoT, Zigbee and Bluetooth LE live here. A real project usually picks one from each layer of IoT protocols. A sensor may talk Bluetooth LE to a gateway, and the gateway may speak MQTT to the cloud. Our piece on multi-protocol IoT systems covers that mix. How do the 7 best IoT protocols compare? Short answer MQTT, CoAP and HTTP handle messaging, while LoRaWAN, NB-IoT, Zigbee and Bluetooth LE handle the wireless link. MQTT suits live telemetry, CoAP suits tiny devices, LoRaWAN and NB-IoT suit wide areas, and Zigbee and Bluetooth LE suit short range. The table shows each one’s best fit. Seven IoT protocols compared (sources named under the table) Protocol Layer How it works Best for MQTT Messaging Publish/subscribe through a broker, usually over TCP/IP Live telemetry to the cloud CoAP Messaging Request/response over UDP, with optional reliability Very small devices, lossy networks HTTP Messaging Standard web request/response Web apps and APIs LoRaWAN Radio link Star-of-stars network of gateways Wide-area, low-power sensors NB-IoT Radio link Low-power wide-area service on mobile networks Rural and deep indoor coverage Zigbee Radio link Self-healing mesh, 2.4 GHz and Sub-GHz Smart homes and buildings Bluetooth LE Radio link Point-to-point, broadcast or mesh in 2.4 GHz Phones, wearables, short range Sources: OASIS (MQTT v5.0), IETF RFC 7252 (CoAP), LoRa Alliance, GSMA, Connectivity Standards Alliance (Zigbee) and Bluetooth SIG. The “best for” column is our editorial judgement. Source: IoT Insights Hub, based on the standards bodies named above. Which IoT protocols should you use for messaging: MQTT, CoAP or HTTP? Short answer Use MQTT for steady telemetry to a cloud broker, CoAP for very small devices on unreliable networks, and HTTP when your devices talk to existing web apps and APIs. MQTT and CoAP are built for constrained devices. HTTP is heavier but familiar to every developer. 1. MQTT MQTT is a client-server publish/subscribe protocol, per the OASIS specification. It normally runs over TCP/IP and has three delivery levels: at most once, at least once and exactly once. The current OASIS Standard, version 5.0, is dated 7 March 2019. Devices publish to a broker, and other clients subscribe. That makes it neat for many sensors feeding one dashboard. Read what MQTT is and how it works for a full walkthrough. 2. CoAP CoAP is defined in RFC 7252 (June 2014) as “a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks.” It runs over UDP and uses DTLS for security, per the RFC. The RFC notes such nodes often have 8-bit microcontrollers with small amounts of ROM and RAM. If your device is that small, CoAP deserves a look. 3. HTTP HTTP is the web’s own request/response protocol. Every developer knows it, and every cloud supports it. It carries more overhead than MQTT or CoAP, so it suits devices with power and bandwidth to spare. See our notes on APIs for IoT device connectivity. Whatever you pick, think about what happens to the data next. At IoT Mail Bridge, the team writes about how machine messages turn into alerts. Their guides on a reliable SMTP relay for IoT and M2M fleet alerts and how to set up IoT email automation the right way cover that last mile. Which IoT protocols suit long range or short range: LoRaWAN, NB-IoT, Zigbee or Bluetooth LE? Short answer LoRaWAN and NB-IoT suit wide areas and low power, while Zigbee and Bluetooth LE suit homes, buildings and short range. LoRaWAN uses your own gateways, and NB-IoT uses a mobile network….

Read Full News
digital twin examples

Digital Twin Examples: 7 Real Uses in Factories and Cities

IoT and AutomationOctober 15, 202612 min read Digital Twin Examples: 7 Real Uses in Factories and Cities By IoT Mail Bridge Editorial Team Key Takeaways A digital twin stays linked to a real asset. That live link is what separates it from a one-off simulation. BMW planned its Debrecen plant virtually. Production was running virtually more than two years before series launch, per BMW Group (2023). Unilever reported about $2.8 million saved at a virtual factory in Brazil, per a 2019 report in SDCExec citing the Wall Street Journal. Cities appear in digital twin examples too. Singapore and Helsinki test solar, flood and planning ideas before building. Most savings figures are self-reported. Start with one machine and measure your own result. Imagine a plant manager near Pune asking a simple question: what if we could break the line without actually breaking it? He is a made-up character, but the question is real. Digital twin examples answer it by giving a machine, a factory or even a city a live virtual copy. You test the risky idea on the copy first. Here is the thing, though. Plenty of articles list twins without saying who built them, when or what they saved. This guide sticks to examples we could check against a named source, and it tells you where the evidence runs thin. At IoT Mail Bridge, we write about the sensor and alert side of IoT every day. That is exactly what keeps a twin honest. In this article What it is Factory examples Machine example City examples Hospital and farm How to start What critics say FAQs Bottom line $2.8Msaved at Unilever’s virtual Brazil factory, per a 2019 report 50%longer time between maintenance on some Rolls-Royce engines (up to) 2+ yrsBMW ran Debrecen virtually before series production 140 t/hatomato yield in 2023 using a digital twin for irrigation, per IRTA What are digital twin examples, and what makes something a twin? Short answer A digital twin is a virtual model of a real machine, building or place that keeps updating from live data. The link to the real asset is the key. Without it, you only have a simulation. Real digital twin examples range from jet engines to whole cities. NASA is widely credited with the idea, mirroring spacecraft on Earth. Today, factories, hospitals, farms and city offices use it. If you want the basics first, read our guide on digital twin examples that start with IoT sensors, and for wider background see digital twin technology and smart operations. Use the table below as a shortlist of digital twin examples to copy, then read the detail under each one. The seven digital twin examples below are the ones we could trace to a named company, agency or study. Dates are shown, because a 2019 result is not a 2026 result. Source: IoT Mail Bridge, from the company and agency sources named in this article. Seven digital twin examples at a glance Example Sector What it models Reported result BMW Debrecen Automotive A whole factory, planned virtually Virtual production started 2+ years before launch Unilever Consumer goods Plant production and energy use About $2.8M saved at one site (2019) Rolls-Royce Aerospace Each engine individually Up to 50% longer maintenance intervals on some engines Virtual Singapore City The island in 3D with live data Tool for solar, flood, planning tests Helsinki City The city as a 3D model Used for planning, solar, flood and noise checks Mater Private Hospital Radiology department workflow Layout redesigned; no figures published Spanish tomato farm Agriculture Irrigation on 15 hectares 140 t/ha in 2023 on 413 mm of water Which digital twin examples show up in factories? Short answer BMW and Unilever are the clearest factory digital twin examples. BMW planned and validated its Debrecen plant entirely virtually. Unilever built virtual copies of plants and reported about $2.8 million saved at one Brazilian site. Both show the twin working before or beside real production. Example 1: BMW plans a whole factory virtually BMW Group said on 21 March 2023 that Debrecen would be its first plant planned and validated entirely virtually. Vehicle production was already running in the virtual plant more than two years before series production, per BMW. Behind it sits NVIDIA Omniverse. Since November 2020, BMW has scanned more than 7 million square metres of indoor and 15 million of outdoor production space, per the same release. Planning tools such as Siemens Process Simulate and Dassault CATIA feed into one shared model. At IoT Mail Bridge, we read the release twice looking for numbers. What BMW did not give us is a savings figure. It says the approach makes planning faster and cheaper, with no percentage attached. Example 2: Unilever builds virtual copies of its plants Per a July 2019 report in SDCExec, which cites the Wall Street Journal, Unilever worked with Microsoft to build digital twins from machine data such as temperature and motor speed. It had eight twins at that time, with data streaming from 15 sites. A virtual factory in Brazil saved about $2.8 million through lower energy use and higher productivity, per the same report. That is a 2019 figure, so treat it as a proof of concept. For the sensor groundwork, see our checklist for deploying industrial IoT sensors. More on plant-floor gains is in our benefits of digital twin IoT for manufacturers, and the wider picture sits in manufacturing IoT from IoT Insights Hub. How does Rolls-Royce use a digital twin for jet engines? Short answer Rolls-Royce tracks each engine as an individual using flight data, then tailors maintenance to it. Per CIO.com in 2021, each flight generates about half a gigabyte of data, and for some engines the time between maintenance was extended by up to 50%. These are company-reported figures. Example 3: Rolls-Royce treats every engine as one-of-a-kind Stuart Hughes, then chief information and digital officer, described it as “truly variable service looking at each engine as an individual engine.” The company monitors how, where and…

Read Full News
IoT alert fatigue

IoT Alert Fatigue: 7 Proven Fixes for Factory Teams in 2026

Automation ToolsOctober 15, 202612 min read IoT Alert Fatigue: 7 Proven Fixes for Factory Teams in 2026 By IoT Mail Bridge Editorial Team Key Takeaways IoT alert fatigue is a design problem. People stop reacting when most alerts need no action. There is a benchmark. Guidance based on EEMUA-191 and ISA-18.2 targets under 288 alarms per operator per day, per Emerson. Too many alerts can cost lives. The UK HSE found an excessive number of alarms reduced operator response in the 1994 Texaco refinery explosion. Seven fixes cut IoT alert fatigue in order. Remove, tune, group, prioritise, route, digest and review. Delivery matters as much as detection. Throttle, escalate and track every message, especially email. Picture a night-shift supervisor whose phone buzzes forty times before midnight. Thirty-nine of those alerts say nothing useful. A sensor flickered, a gateway reconnected, a temperature crossed a line and came back. By the fortieth, he stops looking. That is IoT alert fatigue, and it is one of the quietest risks on a connected shop floor. The supervisor in this story is made up, but the pattern is real. The alert that matters arrives looking exactly like the ones that do not. At IoT Mail Bridge, we send and route machine alerts for a living, so we see this daily. This guide explains the problem, shows a benchmark you can check against, and gives seven fixes you can start this month. In this article What it is How many alerts is too many The 7 fixes Routing alerts Measuring progress What critics say FAQs Bottom line <288alarms per operator per day is the target, per Emerson 1-2alarms per 10 minutes is the target range >10new alarms in 10 minutes counts as a flood 87%of Pembroke refinery alarms were set to high priority, per Process Engineering What is IoT alert fatigue, and why does it hit factories? Short answer IoT alert fatigue is what happens when sensors and software send more notifications than people can act on, so they start ignoring them. Factories feel it hardest because machines raise alerts all day, and most of those do not need a human. The real fault then hides in the noise. It builds up slowly. A new sensor goes live, a threshold is set cautiously, and an alert is copied for a second team. Six months later nobody remembers why half the messages exist. The stakes are not small. The UK Health and Safety Executive’s case summary on the 1994 Texaco refinery explosion at Milford Haven lists this finding: “Excessive number of alarms in emergency situation reduced effectiveness of operator response.” Process Engineering magazine adds that 87% of the alarms at that refinery were set to high priority. Your plant is not a refinery, and a missed alert on a packaging line is not the same event. But the lesson carries over. When every message shouts, people hear none of them. If your sensor data is shaky to begin with, fix that first. Our checklist for deploying industrial IoT sensors covers the groundwork. How many alerts can one operator handle before IoT alert fatigue sets in? Short answer Guidance based on EEMUA-191, ISA-18.2 and IEC 62682 targets under 288 alarms per operator per day, or one to two every 10 minutes. Above 432 a day, or more than three per 10 minutes, calls for action, per Emerson. These are control-room benchmarks, so use them as a starting point. These numbers come from Emerson’s alarm management by numbers paper, which bases them on the three standards above. They were written for process control rooms, not every IoT setup. Still, they give you something to measure against, and that beats guessing. Alarm rate benchmarks per operator (source: Emerson, based on EEMUA-191, ISA-18.2, IEC 62682) Metric Target Action limit Alarms per operator per day Fewer than 288 More than 432 Alarms per operator per 10 minutes 1 to 2 More than 3 Share of time in alarm flood Below 1% Above 5% A flood is a burst. Under EEMUA-191, it starts in a 10-minute window with more than 10 new alarms and ends when a window has fewer than five. A simpler rule treats any 10-minute window with more than 10 new alarms as a flood. IoT Mail Bridge suggests a simple start: count your own alerts for one week before you start fighting IoT alert fatigue. Most teams are surprised by the answer. What are the 7 proven fixes for IoT alert fatigue? Short answer Remove alerts that need no action, tune thresholds and delays, group alerts with one cause, set real priorities, route each alert to its owner, send low-priority items as digests, and review monthly. Do them in that order, because each step makes the next one easier. Source: IoT Mail Bridge. The seven fixes in the order we suggest applying them. Fix 1: Remove alerts that need no action Ask one question of every alert: what will a person do when it fires? If the answer is nothing, delete it or move it to a quiet log. This single pass usually cuts more IoT alert fatigue than any new tool. Fix 2: Use smart thresholds and delays Fixed limits ignore normal swings. Set thresholds around real operating ranges and add a short delay, so a two-second spike does not wake anyone. Keep the delay small. A delay that is too long hides a real fault. Fix 3: Group alerts that share one cause One failed gateway can trigger forty alerts from forty sensors behind it. Link them so the root cause sends one alert and the rest stay quiet. This is where predictive models help, as covered in our guide on how predictive maintenance uses machine learning to catch equipment failures early. For the wider plant view, see this smart factory productivity guide. Fix 4: Set real priority levels Keep the top tier rare. A useful rule is that urgent means someone must act now. Everything else is a lower tier. The Pembroke figure above, 87%…

Read Full News
Industrial AI agents coordinating robots and machines on a smart factory floor

Industrial AI Agents: 5 Proven Shifts for Factories in 2026

Automation ToolsOctober 14, 202610 min read Industrial AI Agents: 5 Proven Shifts for Factories in 2026 By IoT Mail Bridge Editorial Team Key Takeaways Industrial AI agents act. Copilots only suggest. Siemens says its agents can “independently execute complete industrial workflows” at Automate 2025. Siemens, Emerson and IFS all have agent-style products. IFS reported 25% year-on-year ARR growth in industrial AI in H1 2026. Every big number is a vendor claim. Siemens aims for up to 50% productivity gains. We found no independent trial data. Safety rules are the real speed breaker. Interact Analysis (July 2026) found supplier readiness for new robot safety standards varies. Plan the alert before the agent. A fault found but not read saves nobody time. Start with one workflow, in advice-only mode. It is 2 am in a plant on the outskirts of Pune. A pump on line three starts running hot. In the old way, a sensor sends one number, a dashboard turns amber, and nobody looks until the morning shift. By then the bearing is already gone. Now imagine software that sees the same number, reads the maintenance history, raises the work order and asks the supervisor one question: approve the repair, yes or no. That is the promise of industrial AI agents. The plant in this story is made up, but the products behind it are real. Here is the thing, though. The sales decks are tidier than the shop floor. Per Crunchbase News, AI startups raised $102 billion in Q3 2026, which is 64% of all venture funding, as covered in The Business Perspective’s Q3 2026 venture funding analysis. But a well-funded idea is not a proven one. At IoT Mail Bridge, we read the launch notes so you do not have to. This guide separates what has shipped from what is still a slide, and shows you how to test it safely. In this article Agents vs copilots Who has launched them The 5 shifts Safety rules Who reads the alert A safe pilot What critics say FAQs Bottom line 50%productivity gain Siemens aims for (own target) 40%faster robotic machining set-up, per RoboDK 25%IFS industrial AI ARR growth, H1 2026 64%of Q3 2026 venture funding went to AI, per Crunchbase News What are industrial AI agents, and how are they different from copilots? Short answer Industrial AI agents are software programs that do tasks in a plant on their own, like raising a work order or sending an alert. A copilot only answers questions and suggests. An agent acts, inside limits people set. That changes how you test, approve and switch it off. Siemens explains the split clearly. The copilot is the screen you talk to, and the agents are the workers behind it. Rainer Brehm, CEO of Factory Automation at Siemens Digital Industries, said: “…we’re moving beyond the question-answer paradigm to create systems that can independently execute complete industrial workflows.” Siemens also says users pick which tasks to hand over. A wrong suggestion costs an engineer a few minutes, but a wrong action can stop a line. If your data side is weak, start there. Our guide on how predictive maintenance uses machine learning to catch equipment failures early covers the groundwork every agent needs. Which companies have launched industrial AI agents so far? Short answer Siemens, Emerson and IFS have launched agent-style products. Siemens introduced Industrial AI agents at Automate 2025 in Detroit, and Emerson added Ovation AI Agents for power and water. IFS reported 25% year-on-year industrial AI revenue growth in H1 2026. All performance figures are company-reported. Industrial AI agent launches at a glance Vendor What was announced Where it fits Read with care Siemens Industrial AI agents on its Industrial Copilot (Automate 2025) Process and discrete manufacturing Users pick the tasks. The 50% aim is Siemens’ own. Emerson Ovation AI Agents on Ovation Automation Platform 4.0 Power and water Shows agents moving beyond assembly lines. IFS Industrial AI, including fault prediction for field service Field service, asset-heavy industries The 25% growth is IFS-reported. Source: IoT Mail Bridge, from vendor announcements and Interact Analysis (July 2026). The startup side is just as busy. The Business Perspective’s AI agent startup funding report for September 2026 headlines 56 record rounds, and Rise of Startups tracks founders. If you sell into plants, reaching the engineer who runs the pilot is a job of its own. ARS B2B Social Bridge helps B2B technology teams reach verified decision-makers, for example through ARS TargetBridge account-based campaigns. What are the 5 shifts industrial AI agents bring to factories? Short answer Five things are changing. Agents move from answers to workflows, spread into power, water and field service, and cut set-up time through physical AI. Safety rules become the speed breaker, and alerting is the missing layer. Each shift has a catch. Shift 1: From answers to workflows Agents now chain steps: spot an anomaly, check the maintenance history, open a ticket. This works where the process is written down. It fails where the know-how sits in one senior engineer’s head. Shift 2: Into power, water and field service Emerson built Ovation AI Agents for power and water, while IFS aims at field service, where its tool predicts faults and cuts downtime. Shift 3: Physical AI cuts set-up time MarketScale reported in July 2026 that physical AI is squeezing year-long automation projects into months. RoboDK says its software cuts robotic machining set-up time by 40%, a vendor figure. Faster set-up does not mean faster safety approval. Shift 4: Safety rules become the speed breaker Suppliers are not equally ready for tighter robot safety standards. Shift 5: Alerting is the missing layer Most demos end at “the system found a fault”. Who reads it? Why do safety rules slow down factory AI agents? Short answer Because an agent that moves equipment needs the same safety proof as any other machine. A July 2026 Interact Analysis report on incoming industrial robot safety standards found supplier readiness varies. Ask each supplier for its certification status and…

Read Full News
5 Reasons NB-IoT Is the Future of Smart Connectivity

5 Reasons NB-IoT Is the Future of Smart Connectivity

Tech Innovations 5 Proven Reasons NB-IoT Is the Future of Smart Connectivity 6 August 2026 8 min read IoT Mail Bridge Editorial Quick Answer NB-IoT (Narrowband Internet of Things) is a low-power wide-area network protocol built for large-scale device deployments. It connects sensors over ranges up to 15 km on a single battery lasting up to 10 years, running on existing LTE and 5G infrastructure. Core applications include smart metering, smart cities, agriculture monitoring, cold-chain logistics, and industrial asset tracking. Key Takeaways Narrowband IoT devices run for up to 10 years on one battery — the longest in any cellular standard. It penetrates deeper into buildings and underground than standard LTE — a 20 dB coverage advantage. Narrowband IoT runs on existing LTE and 5G towers — no new infrastructure investment required. A single cell supports 200,000+ connected devices per square kilometre for dense smart city rollouts. Licensed spectrum means guaranteed Quality of Service, not the shared-band risk of LoRaWAN or Sigfox. 10 yrs Battery life on a single cell 15 km Range in open rural areas 180+ Operators in 70+ countries $1.15B Chipset market by 2030 (per GSMA) What Exactly Is Narrowband IoT? Narrowband Internet of Things (NB-IoT) is a licensed-spectrum LPWAN standard built by 3GPP to connect millions of low-data sensors over long distances on minimal power. It runs on existing LTE and 5G towers, covers ranges up to 15 km, and powers devices for up to a decade on a single battery. Picture a water meter buried under a pavement in Mumbai, a soil sensor sitting in a wheat field in Punjab, or a cold-chain tracker sealed inside a pharmaceutical container. Each of these devices needs to send a handful of bytes every few hours — reliably, cheaply, and without anyone swapping batteries for a decade. That is precisely the problem this technology was built to solve. Standardised under 3GPP Release 13, narrowband IoT is a licensed-spectrum LPWAN protocol that runs on existing LTE and 5G infrastructure. It trades raw speed for three things: extreme power efficiency, deep indoor penetration, and scalability across millions of devices. With over 180 operators deployed across 70 countries and a chipset market projected to grow from $105 million in 2023 to $1.15 billion by 2030 (per GSMA Intelligence), this is not a niche experiment. At IoT Mail Bridge, we track this market closely — it is fast becoming the default fabric for large-scale wireless deployments worldwide. How Narrowband IoT Works — The Simple Picture 📡 Sensor Wakes Device wakes from deep sleep to collect data 📶 Narrowband Uplink Sends tiny packet over 180 kHz licensed channel 🗼 LTE / 5G Tower Existing cell tower receives — no new infra needed ☁️ Cloud Platform Data routed to an IoT platform for processing 💤 Device Sleeps Returns to PSM sleep — battery saved for years 5 Proven Reasons NB-IoT Is the Future of Smart Connectivity Narrowband IoT consistently outperforms competing LPWAN protocols for large-scale, static-device deployments because of five structural advantages: decade-long battery life, deep building penetration, no new infrastructure cost, support for 200,000+ devices per cell, and guaranteed Quality of Service on licensed spectrum. There are dozens of wireless protocols competing for wireless device deployments — LoRaWAN, LTE-M, Sigfox, Zigbee, Wi-Fi HaLow. So why does narrowband IoT keep pulling ahead for large-scale, mission-critical rollouts? Here are five reasons that hold up under scrutiny. Reason 01 of 05 Ultra-Low Power Consumption — Devices That Last a Decade Narrowband IoT devices use Power Saving Mode (PSM) and extended Discontinuous Reception (eDRX) to spend the vast majority of their operating life in a near-zero power state. When a device only needs to report once an hour — say, a gas meter — it can survive on a standard battery for 10 years or longer. Replacing batteries across thousands of deployed sensors in remote locations is expensive and logistically painful. It also introduces service gaps. Narrowband IoT essentially removes battery management as a concern for most static sensor deployments, which is why utilities love it. ⚡ Up to 10-year battery life Reason 02 of 05 Deep Indoor and Underground Penetration This protocol achieves a 20 dB improvement in coverage gain over standard GPRS. In practical terms, that means signal reaching roughly 100 times further into obstructed environments — basements, underground parking, elevator shafts, and sub-surface utility tunnels are all covered reliably. For smart metering — where meters are often inside buildings or underground vaults — this is the difference between a deployment that works and one that does not. No other LPWAN technology on licensed spectrum matches this penetration depth at equivalent power budgets. 📶 20 dB extra coverage gain Reason 03 of 05 Runs on Existing LTE and 5G Infrastructure Most LPWAN technologies require dedicated base stations or a proprietary network overlay. Narrowband IoT does not. It was built into the 3GPP LTE standard and carried forward into 5G New Radio specifications, so it can run directly on spectrum already deployed by mobile operators via in-band or guard-band deployment. For enterprises, this means no upfront network infrastructure investment. For operators, it means monetising existing spectrum with new device services. This is why over 180 operators worldwide now support this technology commercially — and why it is future-proof against 5G network upgrades from day one. 🏗️ No new infrastructure needed Reason 04 of 05 Massive Device Density — One Tower, Thousands of Sensors This standard is specifically optimised for Massive Machine Type Communication (mMTC) — connecting enormous numbers of simple devices in a concentrated area. A single narrowband IoT cell can theoretically support over 200,000 connected devices per square kilometre. This makes it the natural fit for smart city deployments: thousands of parking sensors, street lights, environmental monitors, and waste bins — all reporting to a single base station without congestion. No other LPWAN technology achieves this density on licensed spectrum with the same reliability guarantees at scale. 🏙️ 200K+ devices per sq km Reason 05 of 05 Licensed Spectrum — Guaranteed Quality of Service…

Read Full News
The 8 Best Neural Networks for Power Now

How Neural Networks Power Real-Time Defect Detection on the Factory Floor

Factory Automation Neural Networks for Defect Detection: How Factories Catch Flaws in Real Time 6 August 2026 9 min read IoT Mail Bridge Editorial Quick Answer — Neural Networks & Defect Detection Neural networks — specifically convolutional neural networks (CNNs) — are trained on thousands of images of both acceptable and defective items, then deployed alongside production-line cameras to inspect every item in real time. They apply consistent visual standards at machine speed, catching micro-cracks, surface blemishes, and dimensional anomalies that tire a human inspector by the end of a shift. The key variables that determine whether the system works are training data quality, camera lighting consistency, and whether a human review step is kept for borderline cases. Key Takeaways Neural networks inspect every single item to the same standard — something a human inspector cannot sustain across an eight-hour shift. Convolutional neural networks (CNNs) are the standard architecture for image-based quality control because of how they process spatial visual patterns. Training data quality matters more than model complexity — a poorly labelled dataset produces poor results regardless of network architecture. Inconsistent camera lighting is the most common cause of performance drop after a successful pilot deployment. Most successful deployments keep a human review step for borderline cases rather than fully automating rejection from day one. 90% Reduction in defect escape rate reported in Deloitte 2025 AI in Manufacturing survey 5–50ms Typical neural network inference time per image on GPU hardware $4.5B Global AI quality inspection market projected by 2030 (per MarketsandMarkets 2025) Manual visual inspection has a fundamental problem that has nothing to do with the skill of individual inspectors. It degrades. Using neural networks for defect detection solves this at its root. The first hour of a shift and the eighth hour produce measurably different results, and some defects — a 0.1mm micro-crack, a subtle surface texture change, a dimensional variance of a few micrometres — are simply beyond what the human visual system can reliably catch at production line speed. At IoT Mail Bridge, we track how manufacturers are solving this. Neural networks trained on visual inspection data are increasingly taking over this specific task — not because they are impressive technology, but because they are a structurally better fit for the problem than the manual alternative. This article explains how neural networks work in this context, what separates deployments that deliver results from those that underperform, and where automated visual inspection fits into a broader factory automation architecture. How Visual Defect Detection Using Neural Networks Actually Works Defect detection systems are trained on thousands of labelled images — acceptable items and defective ones — then deployed alongside production cameras. Each image passes through the network in milliseconds. The network outputs a classification: acceptable, defective, or borderline. Items flagged as defective trigger a rejection or a manual review, depending on the confidence score. The visual inspection pipeline — how it flows 📸 Camera Captures High-resolution image taken as item passes the inspection station 🔧 Pre-processing Image normalised for brightness, cropped to inspection zone 🧠 CNN Inference CNN inference analyses spatial patterns in 5–50ms 📊 Confidence Score Model outputs probability of defect presence per category ⚡ Pass / Flag / Reject Decision triggers downstream action in real time The model at the centre of this pipeline is almost always a convolutional neural network (CNN). This architecture is specifically designed to process image data — layers of filters that learn to detect edges, textures, shapes, and patterns across different scales of the image, building up from simple features to complex defect signatures. What makes CNNs particularly well suited to this task is that they learn directly from examples. You do not need to manually code rules like “a crack appears as a dark line with this width range and this contrast.” You feed it ten thousand images with cracks labelled, and the model learns what a crack looks like across all the variations your production environment actually produces. Why Neural Networks Outperform Manual Inspection at Scale Neural networks apply identical visual standards to every item without fatigue, distraction, or shift-end degradation. Per Deloitte’s 2025 AI in Manufacturing survey, companies that deployed this technology for visual quality control reported defect escape rates dropping by up to 90% compared with pure manual inspection at equivalent line speeds. Factor AI Inspection (Neural Networks) Manual Visual Inspection Consistency across shift Identical — no degradation Degrades significantly after 4–5 hours Inspection speed Dozens of items per second Limited by human reaction time Subtle defect detection Catches sub-millimetre anomalies Unreliable at production speed Scalability Add a camera + model per line Requires proportional headcount increase Defect pattern logging Every decision logged automatically Depends on inspector logging discipline Upfront cost Higher — cameras, compute, training data Lower — just inspector wages Best for High volume, high-speed, consistent items Low volume, complex judgement calls, novel defect types Beyond individual defect catches, automated visual inspection generates something manual inspection never could at scale: a complete, timestamped log of every item inspected and every decision made. That data is what allows quality managers to spot that a specific defect type started trending upward at 14:30 on a Tuesday — which can be traced back to a raw material batch change, a maintenance window, or a temperature shift in the plant. Where Neural Networks Are Being Used for Factory Inspection Neural networks are currently deployed for visual quality control across electronics PCB inspection, automotive panel surface defect detection, pharmaceutical tablet and capsule integrity checking, textile weave defect detection, and food safety grading. Any production line where visual consistency is the quality gate is a candidate. PCB Solder Joint Inspection Automotive Paint & Panel Pharmaceutical Tablet Integrity Steel Surface Grading Textile Weave Defects Food Safety Visual Grading Glass Scratch Detection Packaging Label Verification Semiconductor Wafer Inspection Tyre Surface Analysis What Makes a Neural Network Deployment Actually Succeed The four factors that determine whether neural networks deliver consistent results in production are training data quality, camera lighting consistency, a human review…

Read Full News
Cloud Computing Unlocks Secure Data Privacy Solutions Now

Edge-to-Cloud Data Security for IoT Fleets

Most IoT deployments don’t keep data in one place — it moves from a device, through an edge gateway, and into the cloud, often crossing several networks along the way. Each hop is a potential point of exposure, and securing “the cloud” alone isn’t enough if the edge-to-cloud journey itself isn’t handled properly. This guide covers where IoT data is actually vulnerable along that path, and what closes the gaps. Mapping the Path Data Actually Takes A typical IoT data flow looks like: sensor collects a reading, an edge gateway aggregates and sometimes pre-processes it, then the result travels over a network — often public — to a cloud platform for storage and analysis. Each of these three stages needs its own security consideration; treating it as a single “secure the cloud” problem misses where a lot of real exposure happens. Securing Each Stage The Device Itself Devices need unique credentials rather than a shared fleet-wide password, along with firmware that’s kept current. A compromised device with weak security is an entry point into everything downstream of it. The Edge Gateway Gateways aggregate data from multiple devices, which makes them a higher-value target than any single sensor. Access to the gateway should be tightly controlled and separately monitored from general network access, since a compromised gateway can expose an entire cluster of devices at once. The Network in Between Data moving from edge to cloud should be encrypted in transit, without exception — this is the segment most exposed to interception, particularly when it crosses public or cellular networks rather than a controlled private connection. The Cloud Platform Once data arrives, encryption at rest and least-privilege access control determine how contained a breach stays if the cloud environment itself is ever compromised. Cloud providers generally secure the underlying infrastructure well — configuration on the customer’s side is usually the weaker link. Why Processing Data at the Edge Helps Processing more data locally, and sending only summarized or actionable results to the cloud, reduces how much sensitive raw data actually travels the exposed network segment in the first place. Fewer bytes crossing a public network means less to intercept, alongside the latency benefits covered in our piece on how edge computing powers faster, safer self-driving cars. Frequently Asked Questions Which stage of the edge-to-cloud path is most vulnerable?The network segment in between tends to be the most commonly exploited, particularly when encryption in transit is skipped or improperly configured. Do edge gateways need the same security attention as cloud servers?Yes, arguably more — a gateway aggregating data from many devices is a higher-value target than any single endpoint, and is sometimes under-secured relative to its importance. Does edge processing replace the need for cloud security?No — it reduces how much sensitive data crosses the network, but data that does reach the cloud still needs proper encryption and access control there. Getting Started Securing IoT data end-to-end means treating the device, the gateway, the network, and the cloud as four separate points needing attention — not one problem solved by securing the cloud alone. Map your specific data path, and check that each stage actually has the protection it needs. Related Reading When to Use Edge Computing: 7 Proven Signs You Need It Now Edge Computing Speeds Up Smart Tech Solutions Edge Computing Boosts IoT Security and Data Privacy Today More on this topic from IoT Insights Hub Follow the biggest startup funding rounds (The Business Perspective)

Read Full News
9 Brilliant Hardware Ideas for Power Now

A Practical Checklist for Deploying Industrial IoT Sensors

Deploying industrial IoT sensors sounds straightforward — attach a sensor, connect it, start collecting data — but a rushed rollout often produces unreliable data or sensors that fail within months in a harsh environment. This checklist covers what actually matters before, during, and after a sensor deployment. Before You Deploy During Installation After Deployment Common Mistakes to Avoid The most common failure isn’t a hardware problem — it’s deploying sensors before deciding what decision they’re meant to support, which leads to data nobody actually uses. A close second is underestimating the physical environment and choosing hardware that fails within months. Piloting on a small, representative area before a full rollout catches both problems early and cheaply. Where This Fits Into the Bigger Picture A well-planned sensor deployment is the foundation for the predictive capabilities we cover in our piece on using machine learning to catch equipment failures early — the model is only as good as the sensor data feeding it. Choosing the right underlying platform to manage all of this also matters significantly, which we cover in our buyer’s guide to choosing the right IoT platform. Frequently Asked Questions Should sensors be deployed all at once or gradually?A small pilot in a representative area, before a full rollout, catches environmental and platform issues while the cost of a mistake is still low. How do you choose between wired and battery-powered sensors?It depends on the location — if reliable power is nearby, wired sensors avoid battery maintenance entirely; remote locations usually require a battery or energy-harvesting solution instead. What’s the most overlooked step in a sensor deployment?Setting up alerting for sensor failure itself, not just the conditions it monitors — a silently failed sensor can go unnoticed for a long time otherwise. Getting Started A successful IoT sensor deployment starts with a clear decision the data needs to support, not with the hardware itself. Get the planning right, pilot small, and the rest of the rollout goes far more smoothly. Related Reading Industrial IoT: 7 Proven Ways to Cut Factory Downtime How Predictive Maintenance Uses Machine Learning to Catch Equipment Failures Early Industrial Automation Solutions for Growth More on this topic from IoT Insights Hub Track the biggest startup funding rounds (The Business Perspective) Selling industrial solutions? See why sales ignores marketing leads (ARS B2B Social Bridge)

Read Full News