Fuuz Deployment Methodologies

Fuuz Deployment Methodologies

Article Type: Concept 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 Edge Gateway for machine connectivity and store-and-forward.

The Edge 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 Edge 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.

Note — Coming in 2026: Fuuz is releasing full integration modules for both Inductive Automation Ignition and Litmus Edge, enabling point-and-click configuration for edge-to-cloud connectivity. Until then, integration is accomplished through standard protocol connections (OPC UA, MQTT, Sparkplug B) via the Edge Gateway or Fuuz cloud connectors. All Fuuz platform capabilities — data flows, enterprise integrations, CIM, industrial applications, and data modeling — are available regardless of which deployment method or edge technology is selected.

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 Edge 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).
• Edge 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 Edge 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 Edge 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 OPC UA 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 Edge Gateway's store-and-forward buffering for data operations.
• Store-and-Forward: A capability of the Edge 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:

Capability	Fuuz Cloud (Hosted)	In-House Full Stack (K8S)	In-House Single Instance
Infrastructure	Managed by Fuuz (public or private cloud)	Customer-managed Kubernetes cluster	Customer-managed single server/VM at plant
Scaling	Automatic vertical & horizontal	Customer-managed K8S scaling	Fixed capacity (single instance)
Data Residency	Cloud region (configurable)	Full customer control	Full customer control (on-site)
Offline Capability	Via edge platforms + Edge Gateway store-and-forward	Full — runs inside customer network	Full — runs at plant level
Machine Connectivity	Edge Gateway + Ignition / Litmus / Kepware	Direct (on-network) + Edge Gateway + Ignition / Litmus	Direct (on-network) + Edge Gateway + Ignition / Litmus
Upgrades & Patching	Managed by Fuuz	Customer-managed (Fuuz provides releases)	Customer-managed
Multi-Site Support	Native — single platform, multiple applications	Native — full platform within customer network	Per-site — federated via cloud or API
Fuuz Platform Features	All features	All features	All features

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.

Requirement	Recommended Edge Technology	Why
SCADA with HMIs at the edge	Inductive Automation Ignition	Ignition provides full SCADA visualization, alarming, historian, and operator HMI capabilities. Fuuz handles operational applications (MES, WMS, CMMS, QC), data movement, transformations, contextualizations, CIM, and enterprise integrations. This is the gold standard for sites requiring both real-time process visualization and cloud-connected operational intelligence.
Extensive machine connectivity (no SCADA)	Litmus Edge	Litmus provides 250+ device drivers covering virtually every PLC, CNC, robot, and industrial controller. If you don't need SCADA/HMI but have diverse equipment that exceeds the Edge Gateway's native driver set, Litmus is the most efficient connectivity layer. Fuuz consumes Litmus data via OPC UA, MQTT, or Sparkplug B and delivers all operational applications from the cloud.
Additional drivers beyond Edge Gateway	Ignition, Litmus, or KEPServerEX	When the specific equipment requires proprietary protocol drivers (S7, MC Protocol, BACnet, PROFINET, etc.) not natively available on the Edge Gateway. All three options expose data via OPC UA and/or MQTT for Edge Gateway consumption.
Standard connectivity (OPC UA, EtherNet/IP, Modbus, MQTT)	Edge Gateway only	If all equipment supports protocols the Edge Gateway natively handles — OPC UA, EtherNet/IP (Allen-Bradley), PCCC, Modbus TCP, MQTT, Sparkplug B, SQL, HTTP, TCP — no additional edge software is needed. The Edge Gateway includes store-and-forward and data operations out of the box.
Store-and-forward / data ops at edge	Edge Gateway	The Edge Gateway provides native store-and-forward buffering, MCP capabilities, and edge data operations across all deployment models. Deploy it at any edge location alongside Ignition, Litmus, or standalone.
No on-premise needs — everything cloud-capable	None (Fuuz Cloud only)	If all data sources are cloud-accessible (APIs, cloud databases, SaaS integrations), no on-premise infrastructure is required. Fuuz Cloud connects directly via cloud connectors. This is common for MES implementations driven by ERP integration rather than direct machine connectivity.

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         │
│                         │                                │
│  Edge 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         │
│                         │                                │
│  Edge 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)   │
│                                                          │
│  Edge 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)    │
│                                                          │
│  Edge 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 Edge 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. The Edge 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 Edge 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 an Edge 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 Edge 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 + Edge Gateway Store-and-Forward): A pipeline operator has remote compressor stations with intermittent satellite connectivity. Edge Gateways at each station connect locally to RTUs and PLCs via Modbus TCP, collecting pressure, flow, and temperature data. When satellite links drop, the Edge 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 Edge 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 Edge 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 + Edge 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. Edge 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)

Best For: Organizations that want to minimize infrastructure management, scale across multiple sites, and leverage Fuuz-managed hosting. The fastest time-to-value deployment option.

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:

Configuration	On-Premise Components	When to Use
Cloud Only	None	No machine connectivity needed. ERP-driven MES, API-only integrations, cloud data sources.
Cloud + Edge Gateway	Edge Gateway	Machine connectivity via Edge Gateway–supported protocols (OPC UA, EtherNet/IP, Modbus, MQTT, Sparkplug B, SQL, HTTP, TCP). Store-and-forward for intermittent connectivity. Local databases, file interfaces, printers.
Cloud + Ignition + Edge Gateway	Ignition Gateway, Edge Gateway	SCADA/HMI required at edge. Ignition handles all direct machine communications, operator visualization, alarming, and historian. Edge Gateway consumes Ignition data via OPC UA / Sparkplug B. Fuuz Cloud delivers MES, WMS, CMMS, QC, OEE, CIM, and enterprise integrations.
Cloud + Litmus + Edge Gateway	Litmus Edge, Edge Gateway	No SCADA needed, but extensive machine connectivity requirements across diverse equipment. Litmus provides 250+ drivers. Edge Gateway consumes normalized data via OPC UA / MQTT / Sparkplug B. Fuuz Cloud delivers all operational applications.
Cloud + Kepware + Edge Gateway	KEPServerEX, Edge Gateway	Specific legacy driver requirements (160+ Kepware drivers) without need for SCADA or extensive edge analytics. The Fuuz OPC UA driver connects directly to KEPServerEX.

Important — Offline Considerations for Cloud-Hosted Deployments: Customers running Fuuz hosted by Fuuz should carefully assess how much offline capability is actually required. If all operational workflows can execute from the cloud with reliable internet connectivity, nothing is needed on-premise. The Edge Gateway is only required when you need machine connectivity, local database access, file system interfaces, local printers, or store-and-forward data buffering. Ignition or Litmus are only required when you need SCADA/HMI or extended device driver coverage beyond the Edge Gateway's native capabilities.

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

Best For: Organizations requiring full data residency control, air-gapped deployments, regulatory compliance constraints, or that prefer to manage their own infrastructure. Delivers the complete Fuuz platform within the customer's network perimeter.

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 Edge 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

Best For: Single-site operations, edge-first deployments, plants with limited IT infrastructure, or facilities that need the full Fuuz platform locally without Kubernetes complexity. Also suitable as a plant-level node in a federated multi-site architecture.

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
• Edge Gateway: Deploy the Edge Gateway for edge data operations, store-and-forward to a cloud Fuuz instance, or MCP capabilities at sub-site locations

5. Technical Details

Edge Gateway — Native Protocol Drivers

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

Driver	Protocol	Typical Use
OPC UA Client	OPC UA	Universal industrial connectivity — PLCs, SCADA, historians, gateways
EtherNet/IP PLC	EtherNet/IP (CIP)	Allen-Bradley / Rockwell Automation direct PLC tag read/write
PCCC PLC	DF1/PCCC	Legacy Allen-Bradley SLC 500 and MicroLogix controllers
Modbus TCP	Modbus TCP	Sensors, meters, VFDs, RTUs, Schneider PLCs — the universal field protocol
MQTT Client	MQTT 3.1.1 / 5.0	Subscribe/publish to MQTT brokers — standard IIoT messaging
MQTT Broker	MQTT	Publish data to an MQTT broker endpoint
MQTT Sparkplug B	Sparkplug B	Standardized industrial IoT payload format — UNS, Ignition, Cirrus Link
SAP RFC	SAP RFC	Direct SAP Remote Function Call — invoke BAPIs without middleware
Microsoft SQL	TDS	SQL Server direct connectivity — historians, MES, ERP databases
MySQL	MySQL Protocol	MySQL / MariaDB direct connectivity
Oracle DB	Oracle Net	Oracle Database — requires Oracle Instant Client
IBM DB2	DRDA	IBM DB2 including AS/400 (IBM i) systems
HTTP Client	HTTP/HTTPS	Calls external REST/HTTP APIs from the gateway
HTTP Server	HTTP/HTTPS	Receives HTTP POST requests — acts as a local webhook receiver
TCP Socket	TCP	Raw TCP socket for custom protocols
TCP Server	TCP	Subscribes to a TCP port for incoming connections
Local File	File System	Reads/writes CSV, XML, JSON, flat files on the local machine
Native Printer	System Spooler	Sends to printers via OS print spooler
TCP Printer	TCP (9100)	Direct TCP to label printers (Zebra, SATO, etc.)

Edge Integration Protocols — Ignition & Litmus Connectivity

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

Edge Platform	Primary Protocol	Edge Gateway Driver	Notes
Ignition	OPC UA	OPC UA Client	Ignition's built-in OPC UA server — most common integration path
Ignition	MQTT / Sparkplug B	MQTT Sparkplug B	Ignition is the Sparkplug B reference implementation (via Cirrus Link modules)
Ignition	SQL	MS SQL / MySQL	Query Ignition's historian database directly
Litmus Edge	MQTT / Sparkplug B	MQTT Sparkplug B	Litmus publishes normalized device data via Sparkplug B — recommended path
Litmus Edge	OPC UA	OPC UA Client	Litmus includes an OPC UA server interface
Litmus Edge	REST	HTTP Client	Litmus REST API for configuration and data access
KEPServerEX	OPC UA	OPC UA Client	Kepware's OPC UA server — 160+ device drivers exposed via OPC UA
KEPServerEX	MQTT	MQTT Client	Via Kepware's IoT Gateway plug-in

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
• Edge 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)

Note: Until the dedicated modules release, all Ignition and Litmus integrations are accomplished through the Edge Gateway's native OPC UA, MQTT, and Sparkplug B drivers. This approach is fully production-ready and is how current customers connect to these platforms today.

6. Resources

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

Issue	Cause	Resolution
Edge Gateway cannot connect to Ignition OPC UA server	Ignition OPC UA server security policy mismatch or endpoint URL misconfigured	Verify the Ignition OPC UA endpoint URL (typically opc.tcp://[hostname]:62541/discovery). Ensure Ignition's OPC UA security policies allow the connection (check Security → OPC UA in Ignition Gateway). Accept the Edge Gateway's certificate in Ignition's trust store.
Data gaps after network outage (cloud deployment)	Edge Gateway store-and-forward buffer exceeded during extended outage, or gateway was not deployed	Verify the Edge Gateway is deployed at the edge with store-and-forward enabled. Check buffer storage capacity relative to expected outage durations. For extended outages, consider deploying Fuuz In-House to eliminate cloud dependency for critical data.
Litmus data not appearing in Fuuz	Litmus MQTT/Sparkplug B topic structure does not match Edge Gateway subscription configuration	Verify Litmus is publishing to the expected MQTT topics. Check the Edge Gateway Sparkplug B driver's group ID and edge node ID match the Litmus configuration. Validate MQTT broker connectivity from both Litmus and the Edge Gateway.
Cannot connect to PLC directly from Fuuz K8S deployment	Kubernetes pod network isolation preventing access to the OT network segment	Verify K8S networking allows egress to the OT network VLAN. Check firewall rules between the K8S cluster and the industrial network. Consider deploying an Edge Gateway on a host with OT network access if direct K8S-to-OT routing is not feasible.
Unsupported PLC protocol (S7, MC Protocol, PROFINET)	Edge Gateway does not natively support proprietary PLC protocols	Deploy Ignition, Litmus, or Kepware to bridge the unsupported protocol to OPC UA or MQTT. The Edge Gateway then connects to the bridge platform. This is the standard pattern for any protocol not natively supported.
High latency in cloud-based machine data	WAN latency between edge location and cloud, or Edge Gateway polling interval too large	Adjust Edge Gateway driver polling intervals. For sub-second requirements, consider Fuuz In-House deployment for local processing. Use edge platforms (Ignition, Litmus) for real-time control while Fuuz Cloud handles analytics and operational apps with acceptable latency.
Edge Gateway not auto-updating	Outbound internet access blocked by corporate firewall for Edge Gateway update endpoints	Whitelist the Edge Gateway update endpoints in the corporate firewall. For In-House deployments with no internet access, contact Fuuz support for offline update packages.
Deciding between Ignition and Litmus	Unclear requirements for SCADA vs. connectivity-only	If you need SCADA visualization, operator HMIs at the edge, alarming, or historian — choose Ignition. If you need broad device connectivity (250+ drivers) without SCADA — choose Litmus. If your equipment supports OPC UA, EtherNet/IP, Modbus, or MQTT — the Edge Gateway alone may be sufficient.
Sparkplug B birth/death certificates not registering	MQTT broker does not have Sparkplug-aware session management configured	Verify the MQTT broker supports Sparkplug B session awareness (HiveMQ, EMQX, or Mosquitto with appropriate configuration). Ensure clean session settings match between the publishing edge node and the subscribing Edge Gateway.
Single Instance performance degradation	Server resources insufficient for the number of concurrent users, data flows, and device connections	Review server CPU, memory, and disk I/O metrics. The Single Instance deployment has fixed capacity — if resource constraints are reached, consider upgrading server hardware or migrating to the K8S Full Stack deployment for horizontal scaling.
KEPServerEX OPC UA connection dropping intermittently	Kepware OPC UA session timeout or subscription keepalive mismatch	Increase the session timeout and publishing interval in the Edge Gateway OPC UA driver configuration. Verify Kepware's OPC UA settings match (Administration → Settings → OPC UA). Check for network devices (firewalls, NAT) that may be terminating idle TCP connections.
In-House K8S deployment not receiving platform updates	Self-hosted deployments require manual update application — not automatic like cloud-hosted	Subscribe to Fuuz release notifications. Apply K8S Helm chart updates per the Fuuz deployment guide. Schedule regular maintenance windows for platform updates. For air-gapped environments, request offline release packages from Fuuz support.

Best Practices

• Start with the simplest deployment that meets your needs. If Fuuz Cloud with an Edge 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 Edge 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 Edge 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

Version	Date	Author	Changes
1.0	February 2026	Fuuz Documentation Team	Initial release — three deployment methodologies, edge technology decision framework, Ignition/Litmus/Kepware integration guidance, Edge Gateway native driver reference, and 2026 module roadmap

See Also

• How-To-Managing-Green-Blue-Deployments-with-Fuuz-Package-Management-Zero-Downtime
• Switching-between-Fuuz-Environments-Build-QA-Production
• Fuuz-Standard-Packages
• Setting-up-In-House-Fuuz
• Application-Designer-Guide

---

Source: support.fuuz.com