IronFlock vs Ignition by Inductive Automation
Ignition by Inductive Automation is one of the most widely deployed SCADA platforms in the world. It earned that position by disrupting the legacy SCADA market with unlimited licensing and a modern Java-based architecture — a genuine leap forward when it launched.
IronFlock represents the next architectural shift: from gateway-centric to distributed edge-plus-cloud, from monolithic modules to containerized apps, and from visualization-first to AI-first.
This page provides an honest comparison to help teams choose the right platform.
At a Glance
| Dimension | IronFlock | Ignition |
|---|---|---|
| Look & feel | Modern web UI — clean, responsive, browser-native | Functional but dated — Java desktop Designer, web Perspective is improving |
| Usability | Self-service: sign up, flash a device, deploy apps in minutes | Requires trained integrator for Gateway setup, tag configuration, and Designer projects |
| Collaboration | Multi-user with roles, API keys, device sharing, project-level access control | Single-user Designer; limited multi-user support via Perspective sessions |
| How modern | Cloud-native, containerized, AI-first, designed 2020s | Java-based architecture from 2010; modernizing (Perspective) but legacy core |
| Community | Growing — open app marketplace, developer docs | Large established community — Inductive Automation forum, annual ICC conference, integrator network |
| Strategy | Open ecosystem — IronFlock builds the core system (data historian, alarms, dashboards, device management) and extends via an open third-party app marketplace for domain-specific functionality | First-party modules — Inductive Automation develops and sells all functionality as purchasable modules; third-party contributions via Ignition Exchange are growing but limited in scope |
| Tradition | Founded for IoT fleet management and edge computing | Founded 2003 — disrupted legacy SCADA with unlimited licensing and Java architecture |
Architecture
Ignition: Gateway-Centric
Ignition runs as a Java server (the Gateway) that acts as the central hub for your entire system. The Gateway collects tags from PLCs, stores history in a SQL database, serves Perspective/Vision screens, runs scripts, and manages alarms. Every client connects to the Gateway. Scaling means adding Gateways and connecting them via the Gateway Network.
- Server: Java application running on Windows, Linux, or macOS
- Clients: Web browser (Perspective) or Java desktop app (Vision)
- Edge: Ignition Edge is a limited version for field devices — no database connectivity, 35-day history limit, one project at a time
- Logic: Python/Jython scripting, SFC module for sequential logic
- Deployment: Install Gateway, configure tags and screens via the Designer (Java desktop application)
IronFlock: Distributed Edge + Central Services
IronFlock is a distributed system with two complementary layers. Autonomous edge devices run a lightweight agent and Docker-containerized apps at the point of operation. Central services — FleetDB (TimescaleDB), the FleetDB Service, AI orchestration, and the web UI — provide fleet-wide data storage, dashboarding, and intelligence. A WAMP message broker connects everything with real-time pub/sub and RPC.
You can also provision virtual devices — cloud-hosted compute nodes that join your project alongside physical devices, running fleet-wide services like Grafana, Node-RED, Jupyter, or custom data pipelines.
- Edge devices: Any Linux-capable hardware — Raspberry Pi, industrial PCs, NVIDIA Jetson, gateways — running apps autonomously
- Apps: Docker containers in any programming language, deployed to edge or virtual devices
- Data: Edge apps publish telemetry through the message broker to FleetDB, which automatically provisions per-project TimescaleDB tables
- Central services: FleetDB Service processes data streams, evaluates alarms, and serves dashboards; the AI Service orchestrates multi-agent conversations with direct device access
- Deployment: Flash a device, connect it to the broker, install apps from the store or your own repo
What This Means in Practice
| Scenario | IronFlock | Ignition |
|---|---|---|
| Add a new site | Connect devices — they join the project and start sending data to FleetDB | Install and license a new Gateway |
| Add a capability | Install an app (often free) | Buy and install a module |
| Update 100 devices | One-click bulk OTA across the fleet | Update each Gateway individually |
| Run custom AI model | Deploy as a containerized app on each device | Not supported natively |
| Access device remotely | Click “Open Tunnel” in the browser | Set up VPN |
| Scale devices, data, and projects | Devices are self-contained; services scale independently; TimescaleDB for data; swarm-based project isolation | Add Gateways; Historian for data; separate projects per Gateway |
| Update the platform itself | Zero-downtime rolling updates for most central services | Gateway restart required per instance |
Feature Comparison
Data & Connectivity
| Feature | IronFlock | Ignition |
|---|---|---|
| PLC connectivity | Via OPC UA / Modbus apps | ✅ Extensive native drivers (Allen-Bradley, Siemens, Omron, Modbus, BACnet, DNP3) |
| OPC UA support | ✅ Via apps | ✅ Built-in server and client |
| MQTT support | ✅ Via apps | ⚠️ Requires Cirrus Link modules (paid add-on) |
| Kafka connectivity | ✅ Via apps | ⚠️ Paid module |
| REST API data integration | ✅ Built-in | ⚠️ Via scripting |
| Automated time-series storage | ✅ Per-project TimescaleDB | ❌ Requires external SQL database setup |
| Data isolation between projects | ✅ Physical database separation + cryptographic isolation | ❌ Manual database/tag separation |
| Edge data processing | ✅ Full compute on device | ⚠️ Edge edition — limited, no database connectivity |
| Cloud database scaling | ✅ Managed, auto-scaling | ❌ Self-managed SQL |
| LoRaWAN sensor integration | ✅ ChirpStack on virtual device — unified data pipeline | ⚠️ Via third-party modules |
Visualization & Dashboards
| Feature | IronFlock | Ignition |
|---|---|---|
| Dashboard builder | ✅ No-code YAML widget system | Designer tool (drag-and-drop, more complex) |
| Widget library | ✅ Charts, gauges, maps, tables, forms, actions | ✅ Rich component library (Perspective) |
| Multi-page dashboards | ✅ | ✅ |
| Form widgets with data storage | ✅ Built-in | ❌ Must build custom |
| Action widgets (machine control) | ✅ Built-in | ✅ Via scripting |
| Real-time updates | ✅ Sub-second via WAMP | ✅ Sub-second via polling/subscriptions |
| Dashboard-only user roles | ✅ Built-in | ⚠️ Requires manual role configuration |
| Embeddable dashboards | ✅ | ⚠️ Limited |
| Design tool | Browser-based (no install) | Java desktop Designer application |
Remote Access & Security
| Feature | IronFlock | Ignition |
|---|---|---|
| Built-in tunneling service | ✅ TCP, HTTP(S), UDP, SSH, VNC, VPN | ❌ Not available — VPN required |
| Remote HMI access | ✅ One-click from browser | ❌ Requires network configuration |
| Remote desktop access | ✅ VNC tunneling | ❌ VPN or third-party |
| SSH access to devices | ✅ Browser-based | ❌ |
| Authentication | ✅ OIDC with TOTP 2FA | ⚠️ Basic user/role system |
| API key management | ✅ | ❌ |
| Zero open ports on devices | ✅ Agent calls out | ❌ Gateway listens on configured ports |
| Per-tenant message isolation | ✅ Cryptographic realm isolation | ❌ Shared Gateway |
| Audit logging | ✅ Full device and user audit trail | ⚠️ Alarm journal only |
App Development
| Feature | IronFlock | Ignition |
|---|---|---|
| Development languages | ✅ Any (Docker containers) | ❌ Java and Jython only |
| Built-in cloud IDE | ✅ | ❌ |
| Git integration | ✅ GitHub, GitLab | ❌ |
| CI/CD release pipeline | ✅ Built-in build and release | ❌ |
| App marketplace | ✅ With monetization | ⚠️ Ignition Exchange (community, free) |
| Third-party module ecosystem | Growing app ecosystem | ✅ Established module showcase |
| Scripting language | Any (Python, Go, Rust, JS, etc.) | Python/Jython |
AI & Analytics
| Feature | IronFlock | Ignition |
|---|---|---|
| Multi-agent AI orchestration | ✅ Built-in | ❌ Not available |
| Natural language queries over device data | ✅ | ❌ |
| Physical AI (execute functions on devices) | ✅ | ❌ |
| App-defined custom AI agents | ✅ YAML-based agent templates | ❌ |
| AI-generated real-time charts | ✅ In-conversation | ❌ |
| Voice-based interaction | ✅ | ❌ |
| Edge ML/analytics | ✅ Deploy any ML framework via containerized apps | ❌ |
| Custom data descriptors for AI | ✅ | ❌ |
Device & Fleet Management
| Feature | IronFlock | Ignition |
|---|---|---|
| Bulk OTA updates (OS, agent, app) | ✅ | ❌ Manual per-gateway updates |
| Device grouping and management | ✅ | ❌ |
| Live logs from all apps | ✅ Streaming in browser | ❌ Gateway logs only |
| Location management and map view | ✅ | ❌ |
| Device sharing with privileges | ✅ | ❌ |
| OEM device pre-registration | ✅ Plug & play | ❌ |
| Connect any Linux device | ✅ ARM, x86, NVIDIA Jetson | ❌ Server-class hardware expected |
| Virtual devices (cloud compute) | ✅ Run Grafana, Node-RED, Jupyter alongside physical fleet | ❌ |
Alarms & Notifications
| Feature | IronFlock | Ignition |
|---|---|---|
| Configurable alarm rules | ✅ On any telemetry stream | ✅ Tag alarm system |
| Email notifications | ✅ | ✅ (Alarm Notification module — paid add-on) |
| SMS notifications | ✅ | ✅ (SMS module — paid add-on) |
| Voice call notifications | ❌ | ✅ (Voice module — paid add-on) |
| Severity levels | ✅ Critical, Major, Minor | ✅ Configurable priorities |
| Auto-resolve | ✅ | ✅ |
| Manual assessment & annotation | ✅ | ✅ Alarm shelving |
Pricing Comparison
Ignition: Module-Based Perpetual Licensing
Ignition uses a perpetual license model where each capability is a separately purchased module. A typical deployment requires the platform license plus modules for visualization, database connectivity, alarm notification, reporting, and MQTT — each priced individually. Add annual support & maintenance fees, Ignition Edge licenses for field devices, and third-party MES modules from Sepasoft. Each new site needs its own Gateway license.
See Ignition’s pricing page for current module pricing.
IronFlock: Free Cloud + Subscription for On-Premises
IronFlock’s cloud version is free — all core platform features (device management, dashboards, OTA updates, alarms, app deployment) are included at no cost. IronFlock charges based on resource usage: storage, remote access sessions, virtual devices, and AI usage.
Additional capabilities can be added by purchasing apps from the marketplace — for example, specialized protocol connectors, analytics tools, or industry-specific solutions built by IronFlock or third-party developers.
For on-premises deployments (air-gapped or private infrastructure), IronFlock offers a subscription-based license.
When to Choose Ignition
Ignition may be the better choice if:
- You need traditional SCADA process visualization with highly specialized custom P&ID graphics — Ignition’s Perspective and Vision modules include a dedicated HMI graphics editor with advanced drawing tools for complex custom process screens. (Note: IronFlock now includes a full SCADA symbol library covering pumps, valves, tanks, pipes, and more.)
- You need deep native PLC integration with proprietary protocols (Allen-Bradley DF1, Siemens S7 with absolute addressing) and don’t want to use OPC UA.
- You have an existing Ignition ecosystem with trained integrators and established projects.
- You need Sequential Function Charts for visual sequential logic programming.
- You operate in a highly regulated environment that specifically requires Ignition’s validated workflow documentation.
- Your use case is a single-site SCADA system with a fixed set of well-known PLCs and no need for fleet management or AI.
When to Choose IronFlock
IronFlock is the stronger choice when:
- You manage a fleet of devices across multiple sites and need centralized OTA updates, monitoring, and management.
- You want to deploy custom apps in any language — not just Java/Jython.
- You need built-in AI — natural language queries, multi-agent orchestration, physical AI execution on devices.
- You want remote access without VPN — tunneling for HTTP, SSH, VNC, TCP, and UDP built into the platform.
- You need multi-tenant isolation with automatic per-project data separation.
- Cost matters — IronFlock delivers SCADA, MES, AI, remote access, and fleet management without buying modules one at a time.
- You want to build and monetize industrial apps on a marketplace.
- You are building a modern digital operations stack and want to avoid vendor lock-in to Java-based tooling.
Migration Path
IronFlock can run alongside Ignition. Teams commonly start by connecting IronFlock to their existing OPC UA infrastructure (Ignition can act as the OPC UA server), then gradually shift visualization, remote access, and fleet management to IronFlock while Ignition continues handling direct PLC communication. Over time, containerized OPC UA apps on IronFlock can replace the Ignition layer entirely.