Skip to content

Gateway System Requirements

Fuuz Wiki Import edited this page Jun 5, 2026 · 4 revisions

Fuuz Gateway System Requirements & Deployment Best Practices

Article Type: Concept / How-To Audience: Solution Architects, OT/IT Engineers, Administrators Module: Fuuz Edge Gateway Applies to Versions: 2025.12+

Overview

The Fuuz Gateway acts as a secure door between your facility and Fuuz Cloud. It is not a full-stack platform but a lightweight edge component designed for secure connectivity, data flows, and optional local HMIs. Proper sizing and deployment are critical for performance, reliability, and security.

Critical: If using Edge Flows and Edge Screens (HMI, Local MES, PLC control), deploy one gateway per PLC or workstation for optimal load balancing and security.

Fuuz Gateway deployment overview

Optimal Deployment Strategies

  • Edge Workloads: For HMIs, Local MES, and PLC control, use dedicated gateways per PLC/workstation.
  • Monitoring Only: For centralized data monitoring, a single gateway on a VM can suffice.
  • Small Deployments: For fewer than 100 devices, running as a Windows service on a VM may be acceptable.
  • Best Practice: Always start with Docker-based deployments, ideally managed via Portainer.io templates for scalability and lifecycle consistency.

Hardware Profiles

Single PLC with HMI Screen

  • 64-bit Processor
  • 64-bit Windows Operating System
  • 2–4 GB RAM

Standard PLC / Data Collection

  • 64-bit Dual-Core Processor
  • 64-bit Windows Operating System
  • 4–8 GB RAM

Adding Store-and-Forward

  • 4 CPU Cores
  • Additional 2–4 GB RAM
  • 20 GB free storage for the database
  • Requirements for MySQL (included in the Gateway installation bundle)
  • If exceeding 500 tags with Store-and-Forward, use separate gateways for tag collection and the database.

Deployment Best Practices

  1. Use Docker for containerized gateway services.
  2. Manage deployments with Portainer templates for Build, QA, and Production environments.
  3. Align the gateway lifecycle with cloud environment promotion and validation steps.
  4. Configure secure networking (firewalls, VLANs, certificates for MQTT/WebSocket).
  5. Enable observability: logs, metrics, and dashboards for gateway health.

Tip: For edge-based UI workloads, do not consolidate everything into one gateway — use dedicated or virtual machines for Fuuz Edge.

Security & Governance

  • Role-based access and tenant isolation apply at both edge and cloud.
  • Harden OS and network configurations.
  • Follow compliance standards (SOC 2, ITAR, CFR) for data governance.

Revision History

Version Date Editor Description
1.0 2025-12-23 Craig Scott Initial Release

See Also


Source: support.fuuz.com

🏠 Home

Getting Started (14)
Training Guides (52)

Applications

Access & Users

Data Models & Schema

Screens

Weather Lookup Series — guided 3-part build

Data Flows & Integrations

Data, Reporting & Monitoring

Enterprise & Organizations

Platform Concepts & Architecture (10)
Screens & Application Design (17)
Data Models & Schema (8)
Data Flows & Scripting (51)

Designing Flows

Data Flow Nodes

JSONata Reference

Scripting

Integrations & Connectors (30)

General & iPaaS

Plex

EDI

IIoT & Edge Gateway (18)

Physical Device Connectors

Edge Data Connectors

Reporting, Documents & Dashboards (8)
Administration & Access Control (27)
Data Management (8)
Accelerators, Templates & Packages (8)
Design Standards (1)
How-To Guides (8)
FAQ & Troubleshooting (1)
Release Notes (117)

2026

2025

2024

2023

2022

2021

2020

Policies & Company (6)

Clone this wiki locally