IronFlock vs AVEVA (Wonderware)
AVEVA (formerly Wonderware, now part of Schneider Electric) offers one of the most established industrial software ecosystems in the world. Its suite spans HMI (InTouch), supervisory control (System Platform), process historians (Historian / PI System), batch management, MES, and cloud connectivity (AVEVA Connect). It is deeply entrenched in process industries — oil & gas, pharma, food & beverage, water treatment — where decades of deployment have built institutional knowledge and regulatory validation.
IronFlock represents a fundamentally different architecture: a distributed system where autonomous edge devices run containerized apps, while central services (FleetDB, AI orchestration, dashboarding) provide fleet-wide data and intelligence — all connected through a real-time WAMP message broker.
This page provides an honest comparison to help teams choose the right system.
At a Glance
| Dimension | IronFlock | AVEVA |
|---|---|---|
| Look & feel | Modern web UI — clean, responsive, browser-native | Windows desktop IDEs (WindowMaker, ArchestrA IDE) — powerful but visually dated |
| Usability | Self-service: sign up, flash a device, deploy apps in minutes | Requires specialized ArchestrA engineers; weeks to months for initial deployment |
| Collaboration | Multi-user with roles, API keys, device sharing, project-level access control | Galaxy-based collaboration — complex, requires Windows infrastructure and domain knowledge |
| How modern | Cloud-native, containerized, AI-first, designed 2020s | Legacy Windows architecture from 1990s, incrementally modernized (AVEVA Connect) |
| Community | Growing — open app marketplace, developer docs | Large established industrial community — decades of integrator expertise, especially in process industries |
| 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 | Vendor-built — AVEVA develops and sells all functionality as in-house products; third-party involvement limited to system integrators and OPC connectivity |
| Tradition | Founded for IoT fleet management and edge computing | Wonderware founded 1987 — one of the original SCADA/HMI pioneers, now part of Schneider Electric |
Architecture
AVEVA: Server-Centric Ecosystem
AVEVA’s architecture is built around Windows servers running interconnected components. A typical deployment looks like this:
- System Platform (ArchestrA): The supervisory backbone — object-oriented modeling of plant assets, with Galaxy and AppEngine servers managing runtime.
- InTouch HMI: The visualization layer — screens built in the WindowMaker IDE (Windows desktop tool), served to InTouch WindowViewer or AVEVA Web Clients.
- Historian: Time-series data storage. On-premises server collecting tags from System Platform, PLCs, or direct DA/HDA connections. The separate AVEVA PI System (acquired from OSIsoft) offers a more scalable historian with its own licensing.
- Batch Management: ISA-88 compliant recipe execution for pharma and food production.
- MES / Operations Management: Production tracking, downtime analysis, OEE — via AVEVA’s MES modules or Schneider Electric’s broader Ecostruxure suite.
- Communication Drivers: Proprietary drivers for Modbus, OPC DA/UA, Siemens, Allen-Bradley, and others.
- AVEVA Connect: Cloud offering for data visualization and remote monitoring — a separate product with separate pricing and its own deployment.
- AVEVA Edge (formerly InTouch Edge HMI): A lighter runtime for embedded panels and edge gateways — still Windows-based, limited scripting.
Each component is a separately licensed product. A full deployment requires Windows Server infrastructure, SQL Server databases, dedicated engineering workstations, and significant integration engineering to connect the pieces.
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 | AVEVA |
|---|---|---|
| Add a new site | Connect devices — they join the project and start sending data to FleetDB | Provision Windows servers, install System Platform, configure ArchestrA objects, deploy InTouch screens |
| Add a capability | Install an app (often free) | Purchase a new module, install on server, integrate with System Platform |
| Update 50 field devices | One-click bulk OTA across the fleet | Manual per-device update or SCCM deployment |
| Run custom AI model | Deploy as a containerized app on each device | Not supported natively — requires external integration |
| Access device remotely | Click “Open Tunnel” in the browser | VPN to plant network or set up AVEVA Connect subscription |
| Add a new protocol | Install a protocol app (OPC UA, Modbus, MQTT, Kafka) | Purchase and install communication driver |
| Scale devices, data, and projects | Devices are self-contained; services scale independently; TimescaleDB for data; swarm-based project isolation | Add servers, configure Galaxy hierarchy; Historian for data volumes; separate projects share infrastructure |
| Update the platform itself | Zero-downtime rolling updates for most central services | Planned maintenance window with system downtime |
Feature Comparison
Data & Connectivity
| Feature | IronFlock | AVEVA |
|---|---|---|
| PLC connectivity | Via OPC UA / Modbus apps | ✅ Proprietary drivers (Modbus, OPC DA/UA, Siemens, AB, BACnet) |
| OPC UA support | ✅ Via apps | ✅ Built-in OPC DA and UA |
| MQTT support | ✅ Via apps | ⚠️ Via AVEVA Edge or third-party |
| Kafka connectivity | ✅ Via apps | ❌ Not available natively |
| REST API data integration | ✅ Built-in | ⚠️ Limited — AVEVA Connect APIs |
| Time-series database | ✅ Auto-provisioned per-project TimescaleDB | ⚠️ Historian (per-server license) or PI System (separate product, separate license) |
| Automated data provisioning | ✅ Tables created automatically per app | ❌ Manual tag configuration required |
| Data isolation between projects | ✅ Physical database separation + cryptographic isolation | ❌ Manual server/namespace separation |
| Edge data processing | ✅ Full compute on device | ⚠️ AVEVA Edge — limited scripting, Windows only |
| Cloud database scaling | ✅ Managed, auto-scaling | ⚠️ AVEVA Connect (separate subscription) |
| LoRaWAN sensor integration | ✅ ChirpStack on virtual device — unified data pipeline | ❌ Not available |
Visualization & Dashboards
| Feature | IronFlock | AVEVA |
|---|---|---|
| Dashboard builder | ✅ No-code YAML widget system | InTouch WindowMaker (Windows IDE) |
| Widget library | ✅ Charts, gauges, maps, tables, forms, actions | ✅ Rich industrial symbol library (P&ID, pumps, valves, tanks) |
| Multi-page dashboards | ✅ | ✅ |
| Form widgets with data storage | ✅ Built-in | ❌ Must build custom via scripting |
| Action widgets (machine control) | ✅ Built-in | ✅ Via QuickScript .NET |
| Real-time updates | ✅ Sub-second via WAMP | ✅ Sub-second via OPC subscriptions |
| Dashboard-only user roles | ✅ Built-in | ⚠️ Requires manual role configuration |
| Embeddable dashboards | ✅ | ⚠️ AVEVA Web Client (limited) |
| Design tool | Browser-based (no install) | Windows desktop IDE (WindowMaker / ArchestrA IDE) |
| Industrial HMI graphics (P&ID) | ✅ Full SCADA symbol library | ✅ Extensive symbol libraries — pumps, valves, tanks, piping, conveyors |
Remote Access & Security
| Feature | IronFlock | AVEVA |
|---|---|---|
| Built-in tunneling service | ✅ TCP, HTTP(S), UDP, SSH, VNC, VPN | ❌ Not available — VPN required |
| Remote HMI access | ✅ One-click from browser | ⚠️ AVEVA Web Client or AVEVA Connect (separate subscription) |
| Remote desktop access | ✅ VNC tunneling | ❌ VPN or third-party (TeamViewer, RDP) |
| SSH access to devices | ✅ Browser-based | ❌ |
| Authentication | ✅ OIDC with TOTP 2FA | ⚠️ Windows Active Directory / OS-level auth |
| API key management | ✅ | ❌ |
| Zero open ports on devices | ✅ Agent calls out | ❌ Servers listen on configured ports |
| Per-tenant message isolation | ✅ Cryptographic realm isolation | ❌ Shared infrastructure |
| Audit logging | ✅ Full device and user audit trail | ⚠️ Historian audit trail (limited scope) |
App Development
| Feature | IronFlock | AVEVA |
|---|---|---|
| Development languages | ✅ Any (Docker containers) | ❌ QuickScript .NET, VBScript, ArchestrA scripting only |
| Built-in cloud IDE | ✅ | ❌ |
| Git integration | ✅ GitHub, GitLab | ❌ Proprietary Galaxy versioning |
| CI/CD release pipeline | ✅ Built-in build and release | ❌ Manual deployment via ArchestrA IDE |
| App marketplace | ✅ With monetization | ❌ |
| Third-party module ecosystem | Growing app ecosystem | ⚠️ Schneider Electric partner solutions |
| Scripting language | Any (Python, Go, Rust, JS, etc.) | QuickScript .NET / VBScript |
AI & Analytics
| Feature | IronFlock | AVEVA |
|---|---|---|
| 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 | ❌ |
| Advanced analytics | ✅ Via containerized apps | ⚠️ AVEVA Insight (separate cloud product) |
| Predictive maintenance | ✅ Via AI agents + edge apps | ⚠️ AVEVA Predictive Analytics (separate module) |
Device & Fleet Management
| Feature | IronFlock | AVEVA |
|---|---|---|
| Bulk OTA updates (OS, agent, app) | ✅ | ❌ Manual per-server updates (SCCM, RDP) |
| Device grouping and management | ✅ | ❌ |
| Live logs from all apps | ✅ Streaming in browser | ❌ Windows Event Viewer / log files |
| Location management and map view | ✅ | ❌ |
| Device sharing with privileges | ✅ | ❌ |
| OEM device pre-registration | ✅ Plug & play | ❌ |
| Connect any Linux device | ✅ ARM, x86, NVIDIA Jetson | ❌ Windows only |
| Virtual devices (cloud compute) | ✅ Run Grafana, Node-RED, Jupyter alongside physical fleet | ❌ |
| Multi-site management | ✅ Single control plane for all sites | ⚠️ Separate System Platform per site, or AVEVA Connect |
Alarms & Notifications
| Feature | IronFlock | AVEVA |
|---|---|---|
| Configurable alarm rules | ✅ On any telemetry stream | ✅ Alarm system integrated with System Platform |
| Email notifications | ✅ | ✅ Via alarm notification pipeline |
| SMS notifications | ✅ | ⚠️ Via third-party integration |
| Voice call notifications | ❌ | ⚠️ Via third-party integration |
| Severity levels | ✅ Critical, Major, Minor | ✅ Configurable priorities |
| Auto-resolve | ✅ | ✅ |
| Manual assessment & annotation | ✅ | ✅ Alarm shelving and acknowledgment |
| ISA-18.2 compliance | ⚠️ Flexible but not pre-certified | ✅ Mature alarm management with ISA-18.2 support |
MES & Batch
| Feature | IronFlock | AVEVA |
|---|---|---|
| Batch management (ISA-88) | ⚠️ Via containerized apps | ✅ AVEVA Batch Management (recipe execution, audit trails) |
| OEE tracking | ⚠️ Via apps | ✅ AVEVA MES Performance |
| Production tracking | ⚠️ Via apps | ✅ AVEVA MES Operations |
| Quality management | ⚠️ Via apps | ✅ AVEVA MES Quality |
| Regulatory compliance (FDA 21 CFR Part 11) | ⚠️ Audit trail available, not pre-validated | ✅ Pre-validated workflows |
Pricing Comparison
AVEVA: Per-Component Licensing
AVEVA uses a per-component licensing model where each product in the ecosystem is separately purchased. A typical deployment requires:
- System Platform: Licensed per-server, with per-client access licenses
- InTouch HMI: Per-station or per-client licensing
- Historian: Per-server, with tag count tiers (500, 2,000, 10,000, unlimited)
- Communication Drivers: Per-driver, per-server
- MES Modules: Per-module licensing (Performance, Quality, Operations — each separate)
- Batch Management: Separate module license
- AVEVA Connect: Separate cloud subscription (per-user, per-data-volume)
- PI System (if used instead of Historian): Enterprise licensing from OSIsoft/AVEVA
Additional costs include Windows Server licenses, SQL Server licenses, annual maintenance fees (typically 15–20% of license cost), and professional services for integration and commissioning. Each new site requires a new set of server licenses. Enterprise agreements are negotiated directly with AVEVA/Schneider Electric sales.
IronFlock: Free Cloud + Subscription for On-Premises
IronFlock’s cloud version is free — all core 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 AVEVA
AVEVA may be the better choice if:
- You have existing System Platform deployments with custom InTouch applications and trained ArchestrA engineers.
- You need ISA-88 batch management with pre-validated recipe execution for regulated pharma or food production.
- You require FDA 21 CFR Part 11 compliance with pre-validated electronic signatures and audit trails — AVEVA has decades of validation documentation.
- You need highly specialized custom P&ID graphics — InTouch ships with 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 are a Schneider Electric shop and want tight integration with Modicon PLCs, Ecostruxure, and the broader Schneider ecosystem.
- You need the PI System for enterprise-scale historian deployments across hundreds of thousands of tags with complex asset framework modeling.
- Your organization has a signed Schneider Electric / AVEVA enterprise agreement covering the full software portfolio.
When to Choose IronFlock
IronFlock is the stronger choice when:
- You are building a new deployment and want to avoid legacy Windows-server architecture.
- You need app deployment in any language — not proprietary QuickScript .NET or VBScript.
- 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 system.
- You manage a fleet of devices across multiple sites and need centralized OTA updates, monitoring, and management from a single control plane.
- You need multi-tenant isolation with automatic per-project data separation.
- You want to run on Linux — any distro, any hardware (ARM, x86, NVIDIA Jetson) — without Windows Server infrastructure.
- Cost matters — AVEVA’s per-server, per-client, per-module, plus AVEVA Connect and Historian licensing significantly exceeds IronFlock’s subscription model for comparable capabilities.
- You want to build and monetize industrial apps on a marketplace.
- You want automatic time-series storage without provisioning and maintaining dedicated Historian or PI System servers.
Migration Path
IronFlock can run alongside an existing AVEVA deployment. Teams commonly start by deploying IronFlock edge devices alongside existing System Platform infrastructure, using OPC UA apps to connect to the same PLCs and data sources. IronFlock handles fleet management, remote access, and AI-powered analytics while AVEVA continues serving existing InTouch screens and batch processes. Over time, dashboards and data storage can migrate to IronFlock, reducing dependence on Windows server infrastructure and per-component licensing.