TrendOps Edge
The on-premise gateway that turns siloed plant-floor historian data into a live, gap-free feed the rest of your business can actually use.
Your historians hold decades of process data — but that data stays locked inside plant networks, in proprietary formats, unreachable from the cloud and invisible to the rest of the business.
TrendOps Edge is an on-premise industrial data gateway that connects directly to your historians and SCADA systems and delivers a live, gap-free time-series feed to the TrendOps cloud platform — across firewalled networks, without opening inbound ports, without touching your OT security posture.
Three layers. One outbound connection.
Each layer runs standalone or in combination — so TrendOps Edge adapts to your plant's network topology rather than requiring a specific one. Everything communicates over MQTT, a lightweight protocol built for constrained industrial networking.
Edge Connectors
Sit right next to the historian or data source. Read tag values using the source's native protocol, checkpoint progress to prevent gaps, and publish data upstream over MQTT. One connector plugin per source type — pluggable, not hard-coded.
Edge Relays
OptionalBridge firewalled network segments for plants with multiple OT zones. Pass data from Connectors to the Gateway without opening any inbound ports. Can be chained for multi-hop DMZ traversal.
Edge Gateway
The top-level node that hands data off to TrendOps via Azure IoT Hub or any standard MQTT broker. Manages the node registry and tag catalog, and is the single outbound MQTT connection leaving the plant.
Built for real plant environments
The capabilities that make TrendOps Edge production-ready — not just a proof-of-concept that works in the lab.
Every connector checkpoints exactly how far it got. After a network outage or service restart, polling resumes from that exact point — no missing intervals, no duplicate rows. The data the platform receives is always contiguous and correct.
If a connection goes down, the TrendOps platform can remotely instruct the connector to fill that specific window once it's restored. No manual intervention — the gap fills itself automatically when the site reconnects.
TrendOps Edge makes only outbound MQTT connections. No inbound ports, no VPNs, no network changes that require OT team approval. The plant's security posture doesn't change.
Every connector continuously reports its own status upstream: running, erroring, tag count, data volume sent. The TrendOps platform shows a live view of every deployed node across every site — without calling the plant.
Connectors enumerate all available tags from the source historian and advertise that catalog to the platform automatically. No manual tag-list spreadsheets to build, maintain, or reconcile after a historian upgrade or plant expansion.
Local collection continues whether or not the cloud platform is reachable. Data queues at the edge and flushes automatically when the connection restores. Nothing is lost to a cloud-side maintenance window or internet event at the plant.
One TrendOps Edge install can take on multiple jobs at once — say, pulling from a historian, a SQL server, and an MQTT feed, all from the same node. Sites don't need a separate install for every data source; one deployment flexes to cover whatever's actually on-site.
Tags can be filtered by deadband and compressed at the edge before any data leaves the plant — reducing volume on constrained industrial links at scale without losing meaningful signal changes.
Works with your existing systems
Nine first-party connectors ship today, covering the most widely deployed historians and industrial data platforms. If your source isn't listed, the SQL, MQTT, or OPC UA connector almost certainly covers it — or the Connector SDK lets you build your own.
OPC UA unlocks almost everything else
OPC UA has become the de facto standard interface across the DCS, SCADA, and PLC landscape — and the OPC UA connector means TrendOps Edge's reach extends well beyond the named historians above. Siemens WinCC, ABB System 800xA, Honeywell Uniformance PHD, GE Digital Proficy Historian, Yokogawa Exaquantum, Kepware / KEPServerEX, and most current-generation PLCs and DCS platforms all expose a native OPC UA server. If it speaks OPC UA, TrendOps Edge can already connect to it today.
Edge is the on-ramp. The Platform is the destination.
TrendOps Edge is the data collection layer of the TrendOps platform — built specifically to feed a unified cloud environment where historian data becomes genuinely useful to the business.
Once data is in the platform, it's accessible through the TrendOps Web API — a REST endpoint AI platforms can call via tool definitions, function calls, or Custom Connector actions. Every tag Edge collects is instantly queryable from a Copilot agent, an OpenAI assistant, or any other AI integration without additional pipelines.
TrendGuru is TrendOps's own AI agent, deployed directly in Microsoft Teams. It already has full access to everything Edge delivers — operators can ask questions about plant data in plain language and get answers instantly, without anyone building a custom integration or writing a line of code.
The same data Edge collects feeds Power BI dashboards, Excel workbooks, and any tool that can call a REST API or connect via Power Query. One pipeline to the platform means one integration to maintain — not one per tool, per site, per historian.
An open platform, not a black box
TrendOps Edge is designed to be extended, not just installed. New connectors are added by dropping a plugin DLL into a folder — the runtime discovers and loads it automatically, with no changes to the core product. The TrendOpsEdge.Connectors.SDK is available today, so system integrators, ISVs, and enterprise customers can build connectors for niche, proprietary, or homegrown systems without waiting on TrendOps to build them first.
A public connector registry and marketplace is on the roadmap — a directory of certified, compatible connectors with one-click deployment. The SDK model today is the foundation that makes that possible.
Experience TrendOps Edge in action
See how TrendOps Edge keeps your historians connected, delivers gap-free time-series data, and feeds the TrendOps platform with outbound-only connections and enterprise-grade observability.
Book a Demo