In my project, I had to connect multiple plants with Ignition Cloud Edition. I was sending messages through a gateway device using the MQTT protocol, and Ignition Cloud Edition was consuming it. For example, there is one plant located in France and another plant located in Italy. In each plant, a PLC is connected with a gateway device, and the gateway device is able to share MQTT messages. Ignition Cloud Edition is able to subscribe to it. In the middle of that, there has to be one MQTT broker. The gateway device sends an MQTT message to a broker, and the broker sends it to Ignition Cloud Edition. In Ignition Cloud Edition, I configured a database. The particular database I used was MySQL Community Edition, and the database is used for historian purposes. There was also Perspective module usage as well.
Senior expert SCADA and MES at a computer software company with 11-50 employees
Real User
Top 10
Sep 7, 2026
My main use case for Ignition Cloud Edition is regarding the customer deployment of these Ignition Cloud Edition projects when they do not want to install on the on-premises servers. My main use case for Ignition Cloud Edition is for customers that do not want to use on-premises-based services, and they want to use the pre-bundled module set, which comes with pre-loaded core high-level modules including Perspective, SQL Bridge, Tag Historian, Enterprise Administration Module, reporting, alarm notification, and Mongo DB integration. Rather than purchasing a traditional perpetual license, Ignition Cloud Edition is deployed directly via cloud marketplaces like AWS and Azure using a pay-as-you-go or user-based model and also has native MQTT and cloud connectivity, featuring native MQTT engine, transmission, and distributor modules by Cirrus Link to easily stream IoT data from local edge devices like Ignition Edge directly into the cloud. Its elasticity and enterprise analytics allow taking advantage of cloud infrastructure to scale and store dynamically for massive data historian and connect operational data directly to cloud-native tools like machine learning, AI, and big data pipelines.
My main use case for Ignition Cloud Edition was to view Tyson food plants' beef slaughter lines where they took care of the cattle. I use Ignition Cloud Edition to show the lines and all the systems and send alerts and statuses to the database. A specific example of how I used it in that context is if there was an issue with the way a part of a cow was sliced or skinned, it would alert my phone for the admin.
Control Automation Engineer at a manufacturing company with 501-1,000 employees
Real User
Top 5
Sep 4, 2026
When I first consider Ignition Cloud Edition, the first word that comes to my mind is flexibility. I developed an entire SCADA platform to monitor my site, focusing on maintenance of PLCs and DCS hardware. This allows us to collect maintenance data from the controllers in the field. We have many controllers in the field, including Siemens controllers, Rockwell controllers, and DeltaV controllers. All these controllers have diagnostics from the card, from the point in the card, such as digital input, output inputs, analog outputs, and analog inputs. Every point of the controller and every IO has a diagnostic, and I used Ignition Cloud Edition to send this data to the cloud.
Senior Control Engineer at a construction company with 11-50 employees
Real User
Top 5
Jun 9, 2026
My main use case for Ignition Cloud Edition involves agriculture projects for farms. In an agriculture project, we are using the Cirrus Link modules in Ignition for publishing and subscribing to the Ignition server from the different farms, which is the main point of using MQTT. I then push the data to the cloud using Snowflake, a Snowflake solution from a strategic partner with Ignition for cloud systems and data management. I have another project for wind turbines using the MQTT solution from Ignition and pushing it to the cloud using Snowflake.
Ignition Cloud Edition is a scalable software solution designed to enhance operational efficiency through cloud-based data integration and real-time insights, providing businesses with powerful tools for better decision-making.This fully-featured platform streamlines industrial processes and enables seamless deployment of applications across diverse environments. Its cloud infrastructure supports robust data management, helping users achieve greater scalability and flexibility. With Ignition...
In my project, I had to connect multiple plants with Ignition Cloud Edition. I was sending messages through a gateway device using the MQTT protocol, and Ignition Cloud Edition was consuming it. For example, there is one plant located in France and another plant located in Italy. In each plant, a PLC is connected with a gateway device, and the gateway device is able to share MQTT messages. Ignition Cloud Edition is able to subscribe to it. In the middle of that, there has to be one MQTT broker. The gateway device sends an MQTT message to a broker, and the broker sends it to Ignition Cloud Edition. In Ignition Cloud Edition, I configured a database. The particular database I used was MySQL Community Edition, and the database is used for historian purposes. There was also Perspective module usage as well.
My main use case for Ignition Cloud Edition is regarding the customer deployment of these Ignition Cloud Edition projects when they do not want to install on the on-premises servers. My main use case for Ignition Cloud Edition is for customers that do not want to use on-premises-based services, and they want to use the pre-bundled module set, which comes with pre-loaded core high-level modules including Perspective, SQL Bridge, Tag Historian, Enterprise Administration Module, reporting, alarm notification, and Mongo DB integration. Rather than purchasing a traditional perpetual license, Ignition Cloud Edition is deployed directly via cloud marketplaces like AWS and Azure using a pay-as-you-go or user-based model and also has native MQTT and cloud connectivity, featuring native MQTT engine, transmission, and distributor modules by Cirrus Link to easily stream IoT data from local edge devices like Ignition Edge directly into the cloud. Its elasticity and enterprise analytics allow taking advantage of cloud infrastructure to scale and store dynamically for massive data historian and connect operational data directly to cloud-native tools like machine learning, AI, and big data pipelines.
My main use case for Ignition Cloud Edition was to view Tyson food plants' beef slaughter lines where they took care of the cattle. I use Ignition Cloud Edition to show the lines and all the systems and send alerts and statuses to the database. A specific example of how I used it in that context is if there was an issue with the way a part of a cow was sliced or skinned, it would alert my phone for the admin.
When I first consider Ignition Cloud Edition, the first word that comes to my mind is flexibility. I developed an entire SCADA platform to monitor my site, focusing on maintenance of PLCs and DCS hardware. This allows us to collect maintenance data from the controllers in the field. We have many controllers in the field, including Siemens controllers, Rockwell controllers, and DeltaV controllers. All these controllers have diagnostics from the card, from the point in the card, such as digital input, output inputs, analog outputs, and analog inputs. Every point of the controller and every IO has a diagnostic, and I used Ignition Cloud Edition to send this data to the cloud.
I spin up an instance of Ignition Cloud Edition and simulate a bunch of tags and record them in a separate database.
My main use case for Ignition Cloud Edition involves agriculture projects for farms. In an agriculture project, we are using the Cirrus Link modules in Ignition for publishing and subscribing to the Ignition server from the different farms, which is the main point of using MQTT. I then push the data to the cloud using Snowflake, a Snowflake solution from a strategic partner with Ignition for cloud systems and data management. I have another project for wind turbines using the MQTT solution from Ignition and pushing it to the cloud using Snowflake.
I am using Ignition for systems, making systems, monitoring, and ticketing systems.