# Edge Gateway System Requirements & Deployment Best Practices

> Gateway Applies to Versions: 2025.12+ Overview The Edge Gateway acts as a secure door between your facility and Fuuz Cloud. It is not a full-stack…

Source: https://www.fuuz.com/help/gateway-system-requirements
Last updated: 2026-06-15

Build Apps · Gateways & Connections


Last updated June 15, 2026, 9:02 PM UTC

## Overview

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

![Edge Gateway deployment overview](https://www.fuuz.com/assets/help/e470e97676ce.webp)

## 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 | Fuuz Documentation Team | Initial Release |

## See Also

- Edge Gateway Installation Step-by-Step
- [Gateway Deployment & Architecture](https://www.fuuz.com/help/gateway-deployment-architecture)
- [Edge to Cloud Infrastructure](https://www.fuuz.com/help/edge-to-cloud-infrastructure)

### Need more help?

Ask the Fuuz community, or open a ticket with Fuuz support.

[Ask the community](https://www.fuuz.com/community) [Open a ticket](https://support.fuuz.com/portal/en/newticket)

On this page

[Overview](#overview)

[Optimal Deployment Strategies](#optimal-deployment-strategies)

[Hardware Profiles](#hardware-profiles)

[Deployment Best Practices](#deployment-best-practices)

[Security & Governance](#security-governance)

[Revision History](#revision-history)

[See Also](#see-also)