- CO2, temperature, humidity, level, gas flow, speed and power sensors connected
- MES and PLC data collected alongside, over Modbus and pulse inputs
- Data pushed securely to Azure data lakes, Power BI and Grafana
Run the edge of every plant like cloud software.
Connect PLCs, meters and sensors, deploy ready-made industrial solutions to each site, and follow your whole fleet live from one console. Your data stays in the plant.
Industrial connectivity, ready-made solutions and fleet operations, in one product.
Most projects stitch a gateway, a SCADA, a cloud IoT service and custom scripts together. Edge Management does the whole job, from the PLC to the console.
Connect without rewriting
Catalog modules for Modbus TCP, OPC UA, MQTT, Siemens S7, FANUC FOCAS, MTConnect and RS-232/485. Your existing systems stay as they are.
Start from a ready-made solution
Supersets for compressed air, energy, tanks or production counts, tuned to your plant instead of built from scratch.
Every plant in one console
Live telemetry, history, logs, a fleet map and a digital twin of each site. Drill down from the map to a single variable without opening the plant network.
Secure by design
Data is processed at the source, plants connect outbound only, and every module has its own identity with rotated credentials.
From the fleet map to a single module, in a few clicks.
Select a step to see it in the product.
One platform where other approaches need four.
Each approach covers part of the job. Edge Management covers the whole chain on a single foundation.
| Capability | Cloud IoT platforms | Gateways and SCADA | Custom integration | Newboot Edge Management |
|---|---|---|---|---|
| Native connectivity to industrial equipment | Not covered | Covered | Partial | Covered |
| Ready-made solutions per use case | Partial | Not covered | Not covered | Covered |
| Plant fleet operated like cloud software | Partial | Not covered | Not covered | Covered |
| Runs in your perimeter, outbound-only | Partial | Covered | Covered | Covered |
| Replication across sites without starting over | Covered | Partial | Not covered | Covered |
| Open runtime for your own applications | Partial | Not covered | Covered | Covered |
Indicative positioning by category of solution.
Choose. Compose. Run.
Integrations are packaged as modules. Modules are bundled into supersets: a ready-made solution for one job, such as compressed-air monitoring on one line.
Start from the industrial catalog
Pick modules for Modbus, OPC UA and MQTT, or a ready-made superset for air, energy, tanks or production counts.
Link acquisition, processing and outputs
A superset chains a collector, a transform and its outputs: a local OPC UA server, MQTT or the cloud. Each module exposes typed variables, mirrored in a live digital twin.
Deploy to every plant as one unit
Supersets run on a small cluster at each plant and report to the cloud. Follow the whole fleet, live, from one console.
One platform, every line.
Each use case starts from a ready-made superset you tune to your plant.
Connect your machines
Collect tags from PLCs, meters and controllers, republish them on a local OPC UA server or MQTT, and forward them to the cloud.
Monitor processes live
Pressures, temperatures, levels and counts from all your plants in one console, from the fleet map down to one variable and its history.
Measure what the line produces
Recipes for OEE, batch metering and condition monitoring. Transforms run next to the line; results flow to your teams.
Track energy and utilities
Meter electricity, water, compressed air and fuel, collect the activity data behind emissions reporting, and watch cold-chain temperatures.
Bring vision to the line
Camera modules from our field-proven Computer Vision library are coming to the platform, for defect detection, label OCR and assembly checks.
Run your applications next to ours
The same standard runtime hosts your own containers beside catalog modules, deployed and observed the same way.
Standard Kubernetes at the edge, delivered by GitOps.
A Modbus module polls the line. A transform scales the values. An OPC UA server republishes them on site while the cloud keeps them live and in history. Each module is a container with its own identity, bundled into one superset and deployed as one unit.
- RuntimeRKE2 with Rancher, or K3s with Azure Arc
- DeliveryGitOps, outbound-only from the plant
- IdentityPer-module identity with rotated credentials. Nothing talks unauthenticated.
- OperationsModules observed like any other workload: logs, metrics, health
- HardwareYour industrial PCs or edge servers, on site
Your plants. Your hardware. Your choice of model.
Newboot Edge Management® SaaS
Bring your industrial operations into one console. Pick supersets, deploy them to your plants and follow them live.
- Industrial catalog and ready-made supersets
- Live telemetry, history, logs and fleet map
- Digital twin of every site
Newboot Edge Management® PaaS
Make it the foundation of your own edge solution. Your workloads run alongside catalog modules on the same runtime.
- RKE2 with Rancher, or K3s with Azure Arc
- GitOps delivery, outbound-only from the plant
- Per-module identity with rotated credentials
Proven on 62 industrial sites in 20 countries.
- Live PLC data and furnace context streamed by Newboot Edge
- AI recommendation sent back to operators
- Rolled out to 5 more sites · Saint-Gobain Digital Award 2025
Questions from plant and IT teams.
Do we need to replace our SCADA or MES?
No. Edge Management connects to your existing PLCs, meters and systems, and republishes data over OPC UA or MQTT on site. Your current systems keep running as they are.
Which protocols are supported?
Modbus TCP, OPC UA, MQTT, Siemens S7, FANUC FOCAS, MTConnect, BACnet and serial RS-232/485 through catalog modules, covering 95% of industrial protocols.
Does the plant need inbound connections from the internet?
No. Plants connect outbound only. Modules are delivered by GitOps and each one has its own identity with rotated credentials.
What runs at each plant?
A standard Kubernetes cluster, RKE2 with Rancher or K3s with Azure Arc, on your own industrial hardware.
What is the difference between SaaS and PaaS?
With SaaS you use the console, catalog and ready-made supersets. With PaaS you also run your own workloads on the same edge runtime.
Start with one line, then connect the fleet.
Tell us which machines and which plant you want to connect first. We will propose the supersets that fit.
- 1Scoping workshopMachines, protocols and the first use case.
- 2First plantDeploy a superset and follow it live from the console.
- 3Fleet rolloutReplicate to other lines and sites from the same catalog.