Connectivity
Every System You Already Run, Connected
Fuuz reaches the shop floor and the cloud from one platform: native drivers for PLCs, historians and SCADA on one side, purpose-built and generic HTTP connectors for the enterprise stack on the other. This is the map of what connects today and how — kept current as new connectors ship.
Two domains, one platform
Shop Floor And Enterprise, The Same Way
The Fuuz Device Gateway handles on-premise and shop-floor integration. Cloud connectors handle SaaS and enterprise applications. Both land in the same data model.
Edge & OT — the shop floor
PLCs, SCADA, historians and industrial gateways, reached through the Fuuz Device Gateway: an on-premise agent with native OPC UA, MQTT/Sparkplug B, EtherNet/IP, Modbus and direct SQL drivers, plus a Fuuz module that installs inside the Ignition Gateway itself.
IT & Cloud — the enterprise stack
ERP, CRM, HCM, eCommerce, shipping and AI platforms, reached through purpose-built named connectors where one exists, and the standard REST/SOAP HTTP connector everywhere else — which, in practice, is most of the modern enterprise stack.
Recently added
What's New
Four additions worth calling out on their own.
Fuuz Ignition ModuleOT
An advanced connector that installs directly inside the Ignition Gateway, rather than polling it from outside. See Edge & OT.
Körber PAS-X MSIIT
A purpose-built connector publishing MSI messages to Körber PAS-X over its MSI Web Service. See IT & Cloud.
LM StudioIT
Point the standard HTTP connector at a local LM Studio server's OpenAI-compatible endpoint. See IT & Cloud.
Frontier LLMs, incl. ClaudeIT
Fuuz already talks to Claude.ai over the standard HTTP connector — the same path reaches every major model provider. See IT & Cloud.