Newboot Superset connects your PLCs, meters and sensors, deploys ready-made industrial solutions to every plant and lets you follow the whole fleet live from one console. Data is processed in the plant; the console is hosted in Europe.
Most projects stitch a gateway, a SCADA, a cloud IoT service and custom scripts together. Newboot Superset does the whole job, from the PLC to the console.
Catalog modules read your PLCs, meters and controllers where they are. Your existing systems stay as they are.
Supersets for compressed air, energy, tanks, production counts or vision, deployed in one go instead of built from scratch.
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.
Data is processed at the source, plants connect outbound only, and every plant and module has its own certificate, rotated automatically.
A superset bundles everything a use case needs into one versioned package: data collection, processing, AI models, digital twin, triggers and outputs. It is the unit you deploy, follow and replicate.
Example: corrosion watch on an industrial oven. Three cameras, a Newboot Vision model trained by the maintenance team, a broker and a digital twin, deployed as one superset on the oven’s cluster. When rust crosses a threshold, maintenance is alerted before the next shutdown is planned. Illustrative scenario.
Each use case starts from a ready-made superset you tune to your plant.
Collect tags from PLCs, meters and controllers, organize them in one namespace per plant, republish them locally over OPC UA or MQTT and forward them to the cloud.
Pressures, temperatures, levels and counts from all your plants in one console, from the fleet map down to one variable and its history.
Recipes for OEE, batch metering and condition monitoring. Transforms run next to the line; results flow to your teams.
Meter electricity, water, compressed air and fuel, collect the activity data behind emissions reporting, and watch cold-chain temperatures.
Camera modules from our field-proven Newboot Vision solution are coming to the platform, for defect detection, label OCR and assembly checks.
The same standard runtime hosts your own containers beside catalog modules, deployed and observed the same way.
Set a rule on any variable and choose where it runs. Edge triggers react in the plant, right next to the machine, even if the internet link drops. Cloud triggers compare sites, shifts and history.
In the plant, next to the machine. Keeps reacting if the internet link drops.
Then Alert maintenance and open a work order in your CMMS.
Then Notify the line lead and flag the batch in progress.
Then Warn the shift team before the line runs dry.
Across plants, shifts and history. Sees what no single site can see.
Then Report a probable leak to the energy manager.
Then Record the excursion for audit and alert quality.
Then Notify the production manager and compare with the other sites.
Connectors. Triggers publish their events to an event hub that you own; your tools subscribe to it. Newboot Superset never holds the keys to your business systems. Thresholds shown as examples.
Select a step to see it in the product.
Each approach covers part of the job. Newboot Superset covers the whole chain on a single foundation.
| Capability | Cloud IoT platforms | Gateways and SCADA | Custom integration | Newboot Superset |
|---|---|---|---|---|
| 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 |
| Alerts at the edge, sent to your own tools | Partial | Partial | Partial | 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.
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.
Everything the catalog is made of is available to your teams and integrators. Access to the documentation and code samples is granted on request.
TypeScript, Python and Rust, to write a module that reads, transforms or publishes data like the catalog ones.
A complete, ready-to-fork superset to start from, with its modules, data flows and triggers.
Automate the fleet: enroll clusters, deploy supersets and read live and historical data from your own tools.
Step-by-step guides, also built into the console, from the first cluster to your first custom module.
Bring your industrial operations into one console. Pick supersets, deploy them to your plants and follow them live.
For integrators, partners and teams that build their own edge solution. Your workloads run alongside catalog modules on the same runtime.
On request: PaaS for integrators and partners, or an on-premise installation.
An industrial edge platform. It connects the equipment of each plant, runs ready-made industrial solutions on a small Kubernetes cluster on site, and lets you operate the whole fleet from one console hosted in Europe.
A versioned package that holds everything a use case needs: data collection modules, transforms, AI models, digital twin, triggers and outputs. You deploy it to a plant in one go and replicate it to the next site.
Yes. Tags collected from your equipment are organized in one namespace per plant and republished on site over OPC UA or MQTT, so your applications read a single, consistent source.
No. Newboot Superset 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.
Modbus TCP, OPC UA and MQTT today, with Siemens S7, FANUC FOCAS, MTConnect, BACnet and serial RS-232/485 joining the catalog, to cover 95% of industrial protocols.
Install a supported Kubernetes distribution on the site’s hardware, run the enrollment command given by the console, then deploy the supersets you need. The new cluster appears in the fleet with its status.
No. Clusters, deployments and updates are driven from the console. Your IT team keeps a standard Kubernetes it can inspect with its usual tools if it wishes.
No. Plants connect outbound only. Modules are delivered by GitOps and each plant and module has its own certificate, rotated automatically.
Triggers publish events to an event hub that you own. Your CMMS, MES, ticketing or messaging tools subscribe to it, so Newboot Superset never stores credentials for your business systems.
Yes. An API lets you enroll clusters, deploy supersets and read live and historical data, and SDKs in TypeScript, Python and Rust let you write your own modules. Access is granted on request.
Yes. Newboot Superset is compatible with Azure IoT Operations, so plants that already use it can keep their setup and add supersets on top.
SaaS is the standard offer: you use the console, catalog and ready-made supersets, hosted by Newboot in Europe. PaaS, on request for integrators and partners, also lets you run your own workloads on the same edge runtime.
Tell us which machines and which plant you want to connect first. We will propose the supersets that fit.