Pre-alpha · Phase 4 in progress

The open-source SCADA & HMI platform.

Web-first runtime, cross-platform desktop designer, plant-floor connectivity. Built on Rust, TypeScript, and modern Python for in-platform AI/ML — not Java, not .NET, not Jython 2.7.

MIT-licensed · single static binary · no JVM · no per-server fees

Why another platform?

Industrial automation has been locked behind closed source tooling and expensive gateway licensing for decades. Tools like Inductive Automation Ignition and Rockwell FactoryTalk Optix are excellent, but there is no equivalent open-source platform a small or mid-size plant could actually run. OpenWebHMI's goal is to change that.

AI-assisted development makes the timeline plausible in a way it wasn't five years ago.

v1.0 scope

Concrete bounds. If anything in the project implies bigger numbers, it's wrong and gets fixed.

Stack at a glance

Layer Ignition Optix OpenWebHMI
Gateway Java (JVM) C# / .NET Rust (single static binary)
Designer Java + Swing Visual Studio (Win-only) Tauri + React/TS (Win + Mac)
Web HMI Perspective (React/TS over Java) Optix WebPresentation React + TypeScript
Scripting Jython 2.7 (frozen 2010) C# / JS CPython 3.11+ in worker subprocesses
Open source? MIT

The CPython 3.11+ scripting layer is the headline differentiator: numpy, pandas, scikit-learn, torch, and LLM SDKs all run natively in scripts. In-platform predictive maintenance and AI-assisted authoring become normal features, not external integration projects.

Full reasoning: docs/stack-rationale.md ↗

Where we are

  1. ✓ Phase 0 Foundations — gateway boots, simulated tags flow to a browser.
  2. ✓ Phase 1 Vertical slice — Rockwell driver wired end-to-end, validated against a simulator. Released as v0.1.0.
  3. ✓ Phase 2 Designer MVP — form-based authoring, 6 essential components, hot reload.
  4. ✓ Phase 3 Core SCADA — historian, alarms, auth, trends, Python scripting host, Monaco script editor.
  5. In progress Phase 4 — five drivers (Rockwell, OPC UA, Modbus, MQTT/Sparkplug B, Beckhoff ADS), plugin SDK, real-hardware validation gate before 1.0.

Detailed roadmap ↗

What we explicitly don't try to be

Want to follow along?

The repo is the source of truth — every architectural decision, task brief, code review, and validation run is in markdown alongside the code.