Flexible Architecture.
From a single server to entire networks.

Ideal for small to medium-sized solutions, where the entire system runs on a single server. This is the most commonly used architecture, consisting of one central Ignition server connected to an SQL database and production equipment (PLCs), to which users connect.

Use cases:
monitoring of a production line or hall (SCADA)
visualization of OEE or energy consumption (EMS)
deployment at a single physical location

Benefits: Simplicity, low costs, fast implementation.

Suitable for systems that need to scale. The system is split into separate components (backend servers – communication with PLCs, databases, and enterprise systems vs. front-end servers – user interfaces and reporting). This enables better load distribution across servers and easier infrastructure scaling.

Use cases:
expected or planned growth in data volume and number of users
need to separate visualization from data collection
multiple independent applications/projects within a single infrastructure
large systems that are not divided by individual plants or locations

Benefit: Higher performance, parallel development capabilities, and readiness for enterprise-scale deployment.

Solution for large enterprises and multi-site operations. Each plant has its own local Ignition server (a so-called “spoke”) that collects and processes data locally. The central headquarters (“hub”) has access to all information without the need for a direct connection to every individual device.

Use cases:
centralized overview across multiple plants
data synchronization across sites
advanced enterprise solutions (e.g. BI, predictive analytics, SSOT)

Benefit: High resilience to outages, scalability across locations, ideal for decentralized organizations.

Designed for large industrial groups that need to manage multiple plants, divisions, and data layers. This architecture combines the advantages of decentralized data collection (local “Edge” servers) with a centrally managed platform (central server/cluster).

Use cases:
manufacturing groups with multiple plants and regional IT teams
centralized reports, BI, predictive analytics, SSOT
scenarios requiring high availability and redundancy

Benefit: Hierarchical overview, data consolidation, resilience to outages, and simplified maintenance.

Modern, scalable architecture based on the publish/subscribe principle. Devices (or edge servers) publish data to a central MQTT broker. Ignition, acting as a “subscriber,” consumes the data quickly, securely, and efficiently.

Use cases: remote sites where permanent online connectivity is not available thousands of sensors with low data throughput separation of data collection and data processing

Benefit: Minimal network load, high reliability, and extreme scalability.

Combination of local servers (on-prem) with cloud solutions. Ignition allows you to design the architecture according to your needs. Part of the system runs locally in production, while another part runs in the cloud (e.g. visualization, BI, APIs).

Use cases: consolidation of data from multiple locations ensuring operation even during internet outages combination of local infrastructure with the cloud

Benefit: Flexibility, lower maintenance costs, and the ability to deploy only what you currently need.