Audience: Solution Architects, Enterprise Administrators, IT Infrastructure, Operations Directors, Integration Specialists
Module: Platform Architecture & Infrastructure
Applies to Versions: All Versions

1. Overview

The Fuuz Industrial Operations Platform supports three primary deployment methodologies, each designed to align with specific infrastructure requirements, security postures, network topologies, and operational resiliency needs. Whether an organization requires a fully managed cloud experience, a self-hosted Kubernetes cluster, or a lightweight single-instance deployment at a plant site, Fuuz delivers the same comprehensive operational capabilities — MES, WMS, CMMS, Quality Control, OEE, CIM, data modeling, enterprise integrations, data flows, and industrial applications — across every deployment model.

A critical architectural consideration across all deployment methods is edge-based resiliency — the ability for operations to continue functioning when cloud or wide-area network connectivity is interrupted. Fuuz addresses this through two complementary strategies: deploying edge infrastructure such as Inductive Automation Ignition or Litmus Edge alongside a cloud-hosted Fuuz instance, or running Fuuz itself on local infrastructure where it operates independently of external connectivity. For customers running Fuuz hosted by Fuuz in the cloud, the key question is: how much offline capability does my operation actually need? If all workflows can execute from the cloud with reliable connectivity, no on-premise infrastructure may be required beyond the Fuuz Device Gateway for machine connectivity and store-and-forward.

The Fuuz Device Gateway is available across all three deployment models as a lightweight on-premise agent that provides machine connectivity protocol support (OPC UA, EtherNet/IP, PCCC, Modbus TCP, MQTT, Sparkplug B, SQL, HTTP, TCP, file-based, and printer interfaces), data operations, MCP (Model Context Protocol) capabilities, and store-and-forward resiliency for buffering data during network interruptions. For organizations with connectivity needs beyond the Gateway's native 19 drivers, Fuuz integrates with Inductive Automation Ignition (SCADA + HMI + unlimited drivers) and Litmus Edge (250+ device drivers, edge analytics) as complementary edge technologies.

2. Architecture & Data Flow

Definitions

• Fuuz Cloud (Hosted): A fully managed deployment where the Fuuz platform is hosted by Fuuz on public or private cloud infrastructure. Fuuz manages provisioning, scaling, upgrades, security patching, and high availability. The customer connects via browser and configures edge connectivity using the Fuuz Device Gateway and/or third-party edge platforms.
• Fuuz In-House Full Stack (Kubernetes): A self-hosted deployment where the complete Fuuz technology stack is delivered as a Kubernetes (K8S) application and deployed on the customer's own infrastructure — on-premise data center, private cloud, or hybrid environment. The customer manages infrastructure, networking, and scaling while gaining full control over data residency and network access.
• Fuuz In-House Single Instance: A lightweight, self-contained Fuuz deployment installed at a single plant, factory, or site. Designed for edge-first scenarios where the platform runs locally with direct network access to industrial assets, existing SCADA infrastructure, or a Unified Namespace (UNS).
• Fuuz Device Gateway: A proprietary on-premise software agent providing bidirectional communication between Fuuz (cloud or local) and industrial equipment. Supports 19 native protocol drivers (OPC UA, EtherNet/IP, PCCC, Modbus TCP, MQTT, Sparkplug B, SQL, HTTP, TCP, file, and printer interfaces), store-and-forward buffering during network disruptions, remote configuration from the Fuuz platform, auto-updates, and MCP capabilities. No VPN or RDP access required.
• Inductive Automation Ignition: An industrial software platform providing SCADA, HMI, alarming, historian, and edge computing capabilities. Ignition serves as the preferred edge platform when SCADA visualization and operator HMIs are required at the plant level. All Ignition machine communications are exposed via OPC UA and MQTT/Sparkplug B, which the Fuuz Gateway connects to natively.
• Litmus Edge: An industrial edge data platform offering 250+ device drivers, edge analytics, data normalization, and protocol translation. Litmus is the preferred edge platform when extensive machine connectivity is needed across diverse equipment without SCADA or HMI requirements. Litmus publishes data via OPC UA, MQTT, and Sparkplug B — all natively supported by the Fuuz Gateway.
• KEPServerEX (Kepware): An OPC connectivity platform with 160+ device drivers, published via OPC UA and MQTT IoT Gateway. Kepware can serve as a connectivity layer in any deployment model, particularly where specific legacy protocol drivers are needed. The Fuuz OPCUA driver connects directly to KEPServerEX.
• Edge-Based Resiliency: The ability for industrial operations to continue functioning during cloud or WAN connectivity interruptions. Achieved by running Fuuz locally (In-House), deploying edge platforms (Ignition, Litmus) that operate independently of cloud connectivity, or leveraging the Fuuz Gateway's store-and-forward buffering for data operations.
• Store-and-Forward: A capability of the Fuuz Device Gateway that buffers data locally when network connectivity to the Fuuz platform is interrupted, then automatically forwards buffered data when connectivity is restored. Ensures no data loss during network outages.
• Unified Namespace (UNS): An architecture pattern (typically implemented via MQTT/Sparkplug B) that provides a single, hierarchical data namespace for all operational and business data across an enterprise. Fuuz connects to UNS implementations through its native MQTT and Sparkplug B gateway drivers.
• CIM (Common Information Model): Fuuz's data contextualization framework that provides standardized industrial data models, relationships, and hierarchies. CIM ensures consistent data structure regardless of the source system, enabling cross-site analytics and enterprise reporting.

Deployment Models

The three deployment methodologies share identical Fuuz platform capabilities but differ in infrastructure ownership, network topology, and edge resiliency characteristics:

Edge Technology Decision Framework

Choosing the right edge technology depends on the specific requirements at each facility. The decision is not mutually exclusive — organizations can deploy different edge configurations at different sites while maintaining a single Fuuz platform instance.

Data Flow Architecture per Deployment Model

Fuuz Cloud + Ignition at Edge (SCADA):

Plant Floor Equipment (PLCs, CNCs, Robots, Sensors)
    │
    ▼
┌──────────────────────────────────────────────────────────┐
│  EDGE (On-Premise)                                       │
│                                                          │
│  Ignition Gateway ─── SCADA / HMI / Alarming / Historian │
│    ├── Direct machine communication (all protocols)      │
│    ├── Operator HMIs on touchscreens                     │
│    └── Publishes via OPC UA / MQTT / Sparkplug B         │
│                         │                                │
│  Fuuz Device Gateway ◄──┘                                │
│    ├── Consumes Ignition data via OPC UA / MQTT          │
│    ├── Store-and-forward buffering                       │
│    ├── Edge data operations & MCP                        │
│    └── Pushes to Fuuz Cloud  ────────────────────┐       │
└──────────────────────────────────────────────────┼───────┘
                                                   │
                                                   ▼
┌──────────────────────────────────────────────────────────┐
│  FUUZ CLOUD (Hosted by Fuuz)                             │
│                                                          │
│  ├── Data Flows (transformations, aggregations, ETL)     │
│  ├── CIM (Common Information Model)                      │
│  ├── Industrial Apps (MES, WMS, CMMS, QC, OEE)           │
│  ├── Enterprise Integrations (ERP, CRM, BI)              │
│  ├── Data Modeling & GraphQL API                         │
│  └── Screens, Dashboards, Reports                        │
└──────────────────────────────────────────────────────────┘

Fuuz Cloud + Litmus at Edge (Connectivity-First):

Plant Floor Equipment (PLCs, CNCs, Robots, Sensors)
    │
    ▼
┌──────────────────────────────────────────────────────────┐
│  EDGE (On-Premise)                                       │
│                                                          │
│  Litmus Edge ─── 250+ Device Drivers / Edge Analytics    │
│    ├── Connects to any industrial device                 │
│    ├── Data normalization & contextualization            │
│    └── Publishes via OPC UA / MQTT / Sparkplug B         │
│                         │                                │
│  Fuuz Device Gateway ◄──┘                                │
│    ├── Consumes Litmus data via OPC UA / MQTT            │
│    ├── Store-and-forward & MCP                           │
│    └── Pushes to Fuuz Cloud  ────────────────────┐       │
└──────────────────────────────────────────────────┼───────┘
                                                   │
                                                   ▼
┌──────────────────────────────────────────────────────────┐
│  FUUZ CLOUD (Hosted by Fuuz)                             │
│  [Same full platform capabilities as above]              │
└──────────────────────────────────────────────────────────┘

Fuuz In-House Full Stack (Kubernetes):

Plant Floor Equipment (PLCs, CNCs, Robots, Sensors)
    │
    ▼
┌──────────────────────────────────────────────────────────┐
│  CUSTOMER NETWORK (On-Premise / Private Cloud)           │
│                                                          │
│  Fuuz Platform (Full K8S Stack)                          │
│    ├── Direct machine access (on-network)                │
│    ├── Data Flows, CIM, Industrial Apps                  │
│    ├── Enterprise Integrations                           │
│    ├── Screens, Dashboards, Reports                      │
│    └── Full platform — no cloud dependency               │
│                                                          │
│  Optional: Ignition (if SCADA/HMI needed)                │
│  Optional: Litmus (if extended driver coverage needed)   │
│  Optional: Kepware (if specific legacy drivers needed)   │
│                                                          │
│  Fuuz Device Gateway (for specific edge locations)       │
│    ├── Additional sites, remote assets                   │
│    └── Store-and-forward to Fuuz K8S instance            │
└──────────────────────────────────────────────────────────┘

Fuuz In-House Single Instance (Plant-Level):

Plant Floor Equipment (PLCs, CNCs, Robots, Sensors)
    │
    ▼
┌──────────────────────────────────────────────────────────┐
│  PLANT / FACTORY / SITE                                  │
│                                                          │
│  Fuuz Single Instance                                    │
│    ├── Direct network access to industrial assets        │
│    ├── Connects to existing SCADA (Ignition, etc.)       │
│    ├── Connects to existing UNS (MQTT/Sparkplug B)       │
│    ├── Full Fuuz apps: MES, WMS, CMMS, QC, OEE           │
│    └── Data Flows, CIM, Integrations                     │
│                                                          │
│  Optional: Ignition (SCADA + HMI + edge computing)       │
│  Optional: Litmus (extended drivers + edge analytics)    │
│                                                          │
│  Fuuz Device Gateway                                     │
│    ├── Edge data ops, MCP, store-and-forward             │
│    └── Bridge to cloud services if needed                │
└──────────────────────────────────────────────────────────┘

3. Use Cases

• Multi-Site Manufacturer with SCADA at Every Plant (Fuuz Cloud + Ignition): A discrete manufacturer with 12 plants across North America and Europe deploys Ignition at each facility for SCADA, alarming, and operator HMIs on production lines. Each Ignition instance communicates locally with Allen-Bradley and Siemens PLCs. The Fuuz Device Gateway at each site consumes Ignition data via OPC UA and Sparkplug B, then forwards to Fuuz Cloud for MES, OEE, CIM, and enterprise ERP integration with SAP. Operators see local HMIs on Ignition; managers see cross-site dashboards in Fuuz.
• High-Mix Automotive Tier 1 Supplier (Fuuz Cloud + Litmus): A Tier 1 automotive supplier runs 200+ machines from 15 different vendors including Fanuc, KUKA, Mazak, DMG MORI, and legacy Mitsubishi PLCs. SCADA is not required — they need data collection for OEE and quality tracking. Litmus Edge connects to all 200+ machines using its extensive driver library. Fuuz Gateway consumes the unified Litmus data stream via MQTT Sparkplug B and pushes to Fuuz Cloud for MES, quality control, and production analytics. No SCADA overhead, no HMI development — just connectivity and operational intelligence.
• Greenfield Smart Factory (Fuuz In-House Full Stack K8S): A new semiconductor fab deploys the complete Fuuz platform on an on-premise Kubernetes cluster within their secure network. All cleanroom equipment connects directly to Fuuz via OPC UA and EtherNet/IP since the platform sits on the same network. No data leaves the facility. For equipment requiring PROFINET (a protocol Fuuz does not natively support), they deploy Ignition to bridge PROFINET devices to OPC UA, which Fuuz consumes. The K8S deployment auto-scales during production ramp-up and provides complete data residency control for regulatory compliance.
• Defense Contractor with Air-Gapped Network (Fuuz In-House Full Stack K8S): A defense manufacturer requires zero cloud connectivity and complete data isolation. The Fuuz K8S stack is deployed entirely within their classified network perimeter. All machine connectivity is direct since the platform is on the same network as the equipment. Ignition provides SCADA for weapons assembly lines where real-time operator visualization is critical. No Fuuz Gateway is needed — the platform communicates directly with all equipment.
• Single Plant Startup Manufacturer (Fuuz In-House Single Instance): A startup medical device manufacturer deploys a single Fuuz instance on a server in their one facility. Fuuz connects directly to their Rockwell ControlLogix PLCs via EtherNet/IP and to their environmental monitoring system via Modbus TCP using the built-in gateway drivers. As they grow, they can federate this instance with a Fuuz Cloud instance for corporate visibility without rebuilding their local implementation.
• ERP-Driven MES with No Machine Connectivity (Fuuz Cloud Only): A contract packager needs MES for work order tracking, inventory management, and shipping — all driven by NetSuite ERP integration. Workers use tablets running Fuuz web screens. No direct machine connectivity is needed; production data is entered by operators. Fuuz Cloud connects to NetSuite via REST APIs using cloud connectors. No on-premise infrastructure is deployed — not even a Fuuz Gateway.
• Process Manufacturer with Existing Ignition Infrastructure (Fuuz Cloud + Ignition): A food and beverage manufacturer already runs Ignition at 8 plants for batch control, SCADA, and alarming. Rather than replacing Ignition, they add Fuuz Cloud for MES, WMS, quality management, and enterprise SAP integration. The Fuuz Gateway at each plant connects to each Ignition installation via OPC UA and MQTT, forwarding contextualized production data to Fuuz for cross-plant analytics, CIM, and compliance reporting. Ignition continues to handle all process control and operator HMIs — Fuuz handles everything above the SCADA layer.
• Remote Oil & Gas Operations (Fuuz Cloud + Gateway Store-and-Forward): A pipeline operator has remote compressor stations with intermittent satellite connectivity. Fuuz Device Gateways at each station connect locally to RTUs and PLCs via Modbus TCP, collecting pressure, flow, and temperature data. When satellite links drop, the Gateway's store-and-forward buffer retains all data. When connectivity restores, data automatically syncs to Fuuz Cloud for historian, alarming, compliance, and dispatch operations. No Ignition or Litmus needed — just the Gateway's native Modbus driver and store-and-forward.
• Brownfield Factory Modernization with Litmus (Fuuz Cloud + Litmus): A metal stamping operation has a fleet of legacy equipment spanning 30+ years — old Fanuc controllers, serial-connected CMMs, analog sensors, and a mix of proprietary protocols. Litmus Edge bridges all legacy equipment through its 250+ driver library, normalizing data into a consistent MQTT Sparkplug B stream. The Fuuz Gateway consumes this stream and pushes to Fuuz Cloud for OEE dashboards, predictive maintenance triggers, and integration with Plex ERP. As the Fuuz Litmus module releases in 2026, the integration shifts to point-and-click configuration.
• Distributed Utility with Edge Resiliency (Fuuz In-House Single Instance + Gateway): A water utility deploys Fuuz Single Instance at each treatment plant for local SCADA integration, work order management, and regulatory compliance logging. Ignition at each site handles SCADA and alarming for process control. Fuuz Gateways at remote pump stations handle store-and-forward data collection for sites without full Fuuz instances. A central Fuuz Cloud instance aggregates data from all locations for enterprise reporting, regulatory submissions, and capital planning.

4. Deployment Details

Each deployment methodology has specific implementation characteristics, prerequisites, and configuration workflows. The following sections detail what is involved in each approach.

Deployment Model 1: Fuuz Cloud (Hosted by Fuuz)

Infrastructure: Fuuz manages all cloud infrastructure on public cloud (AWS, Azure, GCP) or private cloud deployments. The customer does not provision, manage, or maintain any Fuuz platform infrastructure. Automatic scaling, backups, security patching, and high availability are included.

Edge Configuration Options:

Deployment Model 2: Fuuz In-House — Full Stack (Kubernetes)

Infrastructure: Fuuz delivers the complete technology stack as a Kubernetes application. The customer deploys it on their own K8S cluster — whether on-premise bare metal, VMware, OpenShift, Rancher, AWS EKS, Azure AKS, or Google GKE. Fuuz provides release packages, Helm charts, and deployment documentation. The customer manages provisioning, networking, scaling, backups, and upgrades.

Machine Connectivity: Since the platform resides inside the customer's network, it can communicate directly with machines, equipment, and industrial systems without a gateway — provided the equipment is on an accessible network segment. The Fuuz Gateway is still available for connecting to isolated network zones, remote sites, or assets behind firewalls.

Edge Technology Options:

• Direct Access: If the K8S cluster has network access to PLCs, sensors, and equipment, Fuuz connects directly via its native protocol support. No additional edge software required.
• Ignition: Deploy Ignition if SCADA visualization, operator HMIs, and alarming are required. Ignition handles process control at the edge; Fuuz K8S handles operational applications.
• Litmus: Deploy Litmus if the equipment mix requires more device drivers than Fuuz natively supports and SCADA is not needed.
• KEPServerEX: Deploy Kepware for specific legacy driver requirements where Ignition or Litmus are not justified.

Deployment Model 3: Fuuz In-House — Single Instance

Infrastructure: Fuuz is deployed as a single instance on a server or VM at the plant, factory, or site. This is the lightest-weight self-hosted option — no Kubernetes orchestration required. The instance has direct network access to local industrial assets, SCADA systems, databases, and file shares.

Integration Points:

• Existing SCADA: Tie directly to Ignition, VTScada, FactoryTalk, or any other SCADA system via OPC UA, MQTT, or Sparkplug B
• Unified Namespace (UNS): Connect to existing MQTT/Sparkplug B UNS implementations using the Fuuz MQTT and Sparkplug B drivers
• Ignition: Add Ignition alongside for SCADA, HMI, edge computing, and industrial controls integration capabilities beyond what Fuuz provides
• Litmus: Add Litmus for additional device driver coverage and edge analytics when the equipment mix exceeds Fuuz's native gateway drivers
• Fuuz Gateway: Deploy the Gateway for edge data operations, store-and-forward to a cloud Fuuz instance, or MCP capabilities at sub-site locations

5. Technical Details

Fuuz Device Gateway — Native Protocol Drivers

The Fuuz Device Gateway includes 19 native drivers that cover the majority of industrial connectivity scenarios without requiring third-party edge software:

Edge Integration Protocols — Ignition & Litmus Connectivity

Both Ignition and Litmus expose data through protocols natively supported by the Fuuz Gateway. The primary integration paths are:

Platform Capabilities Available Across All Deployment Models

Regardless of the deployment method selected, every Fuuz instance delivers the identical set of platform capabilities:

• Data Flows: Visual workflow designer for backend automation, transformations, aggregations, ETL, event-driven processing, and gateway-level logic
• Enterprise Integrations: 44+ cloud connectors for ERP (SAP, NetSuite, Dynamics 365, Epicor, Plex), CRM (Salesforce, HubSpot), BI, and cloud services
• CIM (Common Information Model): Standardized industrial data models for cross-site consistency and contextual analytics
• Industrial Applications: MES, WMS, CMMS, Quality Control, OEE, Production Scheduling, and more — pre-built or custom-developed
• Data Modeling: Schema designer with full GraphQL API generation for custom application data models
• Screen Designer: Visual UI builder for dashboards, tables, forms, HMIs, mobile screens, and reports
• Device Gateway: On-premise agent with 19 native drivers, store-and-forward, remote configuration, and auto-updates
• Multi-Tenancy: Application isolation with dedicated databases, users, roles, and access controls per application
• Package System: Distributable .fuuz packages for application deployment, marketplace distribution, and version management

Upcoming: Fuuz Modules for Ignition & Litmus (2026)

Fuuz is releasing dedicated integration modules for both Inductive Automation Ignition and Litmus Edge in 2026. These modules will provide:

• Point-and-click configuration for Ignition and Litmus connections from within the Fuuz platform
• Automated tag/device discovery from Ignition OPC UA namespaces and Litmus device catalogs
• Bidirectional data mapping between Fuuz data models and Ignition/Litmus data structures
• Health monitoring dashboards for edge connectivity status and data quality metrics
• Pre-built data flow templates for common integration patterns (telemetry ingestion, alarm forwarding, setpoint writing)

6. Resources

Fuuz Platform Resources

• Fuuz Platform: fuuz.com
• Fuuz Knowledge Base: support.fuuz.com
• Fuuz Device Gateway Documentation: KB Article — Device Gateway Configuration & Drivers
• Fuuz Cloud Connectors Reference: KB Article — Cloud Connectors: Complete Integration Reference
• Fuuz Edge Connections Reference: KB Article — Edge Connections: Complete Industrial Integration Reference
• Fuuz Data Flows Documentation: KB Article — Data Flow Designer

Edge Platform Resources

• Inductive Automation Ignition: inductiveautomation.com — SCADA, HMI, alarming, historian, edge computing
• Litmus Edge: litmus.io — 250+ device drivers, edge analytics, data normalization
• KEPServerEX (Kepware / PTC): kepware.com — 160+ device drivers, OPC UA server
• Cirrus Link Solutions: cirrus-link.com — Sparkplug B specification authors, Ignition MQTT modules

Protocol Standards

• OPC UA: opcfoundation.org — OPC Unified Architecture specification
• Eclipse Sparkplug: sparkplug.eclipse.org — Sparkplug B specification for industrial MQTT
• MQTT: mqtt.org — MQTT messaging protocol specification
• EtherNet/IP: odva.org — CIP and EtherNet/IP specifications

7. Troubleshooting

Common Issues

Best Practices

• Start with the simplest deployment that meets your needs. If Fuuz Cloud with a Gateway covers your requirements, there is no need to deploy Ignition or Litmus.
• Assess offline requirements honestly. Many operations can run entirely from the cloud. Only deploy on-premise infrastructure when there is a genuine need for offline capability, sub-second control, or data residency compliance.
• Deploy the Fuuz Gateway at every site with machine connectivity needs — even alongside Ignition or Litmus — to gain store-and-forward, MCP, and edge data operations capabilities.
• Use Ignition when SCADA is required. If operators need HMIs, alarming, or real-time process visualization at the plant floor, Ignition is the clear choice. Let Ignition handle process control; let Fuuz handle operations and enterprise integration.
• Use Litmus when you need broad connectivity without SCADA. If the primary challenge is connecting diverse equipment from many vendors, Litmus's 250+ driver library solves the connectivity problem while Fuuz handles everything above the data layer.
• Prefer Sparkplug B for MQTT integrations. When connecting to Ignition, Litmus, or any UNS implementation, use the Sparkplug B protocol driver rather than raw MQTT for standardized payload structure, birth/death session management, and automatic metric discovery.
• Plan for the 2026 Ignition and Litmus modules. Current protocol-based integrations will migrate seamlessly to the new point-and-click modules when released. Design your architecture with these modules in mind.
• Network segmentation matters for In-House deployments. Ensure the K8S cluster or Single Instance server has appropriate network access to both the OT network (for machine connectivity) and the IT network (for enterprise integrations, user access).
• Test store-and-forward before production. Simulate network outages during deployment validation to confirm data buffering and recovery work as expected for your specific data volumes and outage scenarios.
• Consider federated architectures for multi-site. Deploy Fuuz Single Instance at each site for local operations, then aggregate into Fuuz Cloud for enterprise-level visibility, analytics, and reporting.
• Document the edge technology stack at each site. Different sites may use different combinations of Fuuz Gateway, Ignition, Litmus, and Kepware. Maintain a deployment registry for support and upgrade planning.
• Separate concerns between edge and cloud. Edge platforms (Ignition, Litmus) own real-time machine communication and process control. Fuuz owns operational applications, data contextualization, enterprise integration, and analytics. Avoid duplicating responsibilities.
• Size K8S clusters for growth. When deploying the Full Stack K8S option, plan node capacity for anticipated growth in applications, users, data flows, and connected devices over a 3-5 year horizon.
• Leverage Fuuz Data Flows for edge-to-cloud transformations. Even with Ignition or Litmus at the edge, Fuuz Data Flows handle the heavy lifting of data transformation, contextualization (CIM), aggregation, and enterprise system integration. This keeps edge platforms focused on what they do best — connectivity and control.

8. Revision History